Thursday, March 16, 2006

sql server 2000 dts copy object pain

task is simple enough, copy a table (and its contents) from one database server to another.
So i create a dts copy object, uncheck "copy all", uncheck "copy related objects" select the specific table and bobs your uncle, or not. for some reason the dts is trying to copy a user over as well. so i get a "user xxx does not exist in the database" error. ok, thats fine, if i'd even selected that i wanted to copy the user. What a pain in the arse.

Luckily i have an application that updates a replica of this table, and with a quick connection string change i started updating the table (altho this will take 10 times as long as the dts would have).

I'm not saying the dts copy object is shite, obviously i'm dong somethign a bit stupid, but surely if you are allowed to select the specific database objects to copy the dts should only copy those specific database objects?

No comments: