import/export wizard in 2000 had lots of options.
I could copy databases without a care in the world. Including constraints, stored proc., AND the data, etc.
Now, with v2008, the wizard is dumbed down too much. It's a "stupid" copy function that fails on the first constraint it meets.
"Copy database.." is not an option here: it needs sysadmin on both source and destination server.
Re-adding the constraints manually is not an option either: the database is WAY too large.
I'm actually hoping there is a temporary bug in the import/export wizard. Each option (and you have THREE...) returns with a new error.
Googling, I found I am not alone:
This post is exactly my situation. Here's what his post says: (bolded key parts)
I'm trying to get used to sql server 2008 having been
forced to upgrade by my isp. I need to back up my key db on a weekly
remote schedule, so have been trying to use ssms to export data from my
remote db to a local copy.
Firstly I created a new empty db on
the local machine. Then I scripted the structure of the db on the
remote machine and ran the resulting query on the local machin
View Complete Post