We found ourselves in the less than ideal situation of developing against a database with a different version than the production one; we were developing against SQLServer 2005 but it was going to be deployed on SQLServer 2000.
I think this is a big no-no; the closer your development environment, the more valuable it is.
So anyways, we ended up having almost a fairly large (500+MB) SQLServer 2005 which we needed to get into SQLServer 2000 SP4. Restoring the backup didn't work, which isn't too much of a suprise. I certainly wasn't going to export each table into CSV and import it individually!
Google to the rescue. Google came up with this article which worked a treat.
I ended up creating the single SQL file which came out at 1.6GB, then compressed it down to a much more manageable 60MB, moved it across the world to the remote machine and hey bisto - it worked.
I think this is a big no-no; the closer your development environment, the more valuable it is.
So anyways, we ended up having almost a fairly large (500+MB) SQLServer 2005 which we needed to get into SQLServer 2000 SP4. Restoring the backup didn't work, which isn't too much of a suprise. I certainly wasn't going to export each table into CSV and import it individually!
Google to the rescue. Google came up with this article which worked a treat.
I ended up creating the single SQL file which came out at 1.6GB, then compressed it down to a much more manageable 60MB, moved it across the world to the remote machine and hey bisto - it worked.
No comments:
Post a Comment