Exporting From 2005, importing into 2000
-
Can you post BCP format file?
MohammedU
Microsoft SQL Server MVP -
I think I found the source of my confusion, and it does seem to be working now. I was expecting the actual format of the bcp format file to change, not just the version number. I used the "V -80" switch on all my BCP commands (generating the format files and importing and exporting the *.dat files), and everything now seems to work on both SQL2000 and SQL2005, even though all the format and data files are generated from a SQL2005 server. The key was to include the -V 80 option on every single invokation of BCP.
Thanks for your patience with my question.
-
Good to know it is working
MohammedU
Microsoft SQL Server MVP -
Well, I THOUGHT it was working. Now it's not working again. I swear I had it working briefly.
The problem is that when I do the:
BCP database.dbo.tablename format nul -f "tablename.fmt" -N -V 80 -S serverName -u user -p password
command, it's outputting a file with a 9.0 at the top, instead of the 8.0, and so SQL Server 2000's BCP utility throws up its hands and stops when it sees it. This is very frustrating. I SWEAR I had it working this weekend...
I absolutely need to do this. Can ANYONE tell me what is going wrong? I *have* to produce format files and data files from a SQL Server 2005 that is readable on SQL Server 2000.
-
Open your format file and change it to 80 and try it.
MohammedU
Microsoft SQL Server MVP -
I can and will try that... but there are 760 format files, and one upgrade package is supposed to run against either SQL Server 2000 or 2005.
It would be nice if BCP on 2005 would simply honor the -V 80 switch I'm sending it, and create a version 8.0 compatable format file!
Viewing 6 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply