New answers tagged import
I know the one-click installer breaks (or used to break) with passwords that have an ampersand in them. It's part of some shell that doesn't go through. It gives errors like the ones you saw.
This won't work. Don't even try feeding mysqldump output directly into psql. You'll need to dump schema and data separately, convert the schema either by hand or with a tool, load the converted schema into PostgreSQL then load the dumped data. mysqldump's compatibility flags are moderately useful for dumping data but pretty useless for dumping schema ...
Since you are trying to avoid SSIS and BCP: If you don't have a deep-seated hatred of MS Access, you might want to take a brief look at it. It has a pretty slick flat-file import wizard. I prefer it over SSIS for small one-time (manual) jobs with flat-files. MSAccess can link directly into SQL Server (or equiv) tables and import directly into the server ...
As mentioned in the comments above, your time would be much better spent using SSIS for this task. Here's a recent video post that discusses handling multi-line record data files much like yours. Since you're okay with spinning your wheels, let's try to find an answer anyway--if you have the data in a single row, you have somewhere to start. My next step ...
Your best option (considering your limitations) is probably using OPENROWSET with a FORMAT FILE Take a look at those links: Use a Format File to Bulk Import Data You can use the BCP utility once locally to Create a Format File I prefer the XML Format Files
Take a good look at the control flow, both in your SQL Agent job, and the SSIS package it's running. I suspect there's a step in one of them that cleans out the source table after the work is finished, and this step is running regardless of whether the import succeeded or not. Or there may be an unrelated cleanup job that cleans out that import table.
Top 50 recent answers are included