April 1, 2008 at 11:32 am
Btw, BCP's err files (-e) filter all rows for a failed batch, not just the offending row(s). And using too large a batch size can cause issues with the log even if the db is set for simple recovery mode.
April 1, 2008 at 11:36 am
Jeff Moden (4/1/2008)
To add to what Matt just said... if the server logs in as a domain super-user that can see all the machines and at least some "shares", using a little Dynamic SQL in conjuction with BULK INSERT will blow the doors off of any other type of import. If you have the luxury of being able to use BCP, BCP will find bad rows and store them in a "bad file" so you can repair them later without having the main import fail. It's not quite as fast as BULK INSERT but is still way faster than DTS. Rumor has it that SSIS also has a "Bulk Insert" method but I don't know if it'll check for bad rows "auto-magically".
SSIS has the ability to redirect any error rows, or just ignore them. So - you can capture the errors, and possibly do something else with them.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
April 1, 2008 at 12:29 pm
Thanks Matt. Learned something new today! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2008 at 2:50 pm
Lowell,
July 31, 2008 at 2:53 pm
Lowell,
You may want to try opening the data file in Excel and checking tab delimiter. Hope this info helps.
Now, maybe you can help me. I'm looking for the data base with the dam and reservoir information. Is it a public access data base? And if so, can you give me some guidance on how to access it?
Thanks,
Peggy
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply