I have just upgraded to SQL Server 2005 from 2000 and went to export some objects to another server and found i no longer can - well at least the easy way.
Can anyone tell me what has happened to Copy Objects in the Import / Export Wizard Where can i find it now
Regards,
John
What's Happened to Copy Objects in Import/Export Wizard?
Flores
MINATCHY
Is there another thread on this issue This is a huge problem; I can't believe its just being dropped.
Not to mention that the Export Data is broken in many ways: SP1 fixed one of the Identity Insert bug (if you had "Optimize for many tables" checked, it would not do the Identity Insert), but if you export to another database, the tables are created at the destination, but without indexes (not surprizing) but also without other field-level settings, like identity.
-w
RetroFire
Launch the copy database wizard (All Tasks|Copy Database).
On the 3rd screen after the source and dest connections screens there is a screen with 2 radio buttons and a check box, select the 2nd radio button marked SQL Management Objects.
SMO is the API that is used to actually perform the transfer.
tsennyuen
Compared to SQL 2000 this is a major step back. So far I have upgraded only one server, and I will not upgrade any more because of this issue.
Gert
Mehmet Atlihan
You theoretically can for tables and views, you have to select a table and use the context menu there.
Howewer: on my PC I always get an ODBC error (see my post http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=344363&SiteID=1) (didnt get an answer yet) and a nice article
http://www.databasejournal.com/features/mssql/article.php/3594201
which gives some more info.
Personally i find this extremely debilitating in my work as a DB admin and hope all the nice functionalities of the Enterprise Manager for MSSQL 2000 get back in SP1 for 2005.
Michael
Novacaine
Igor Siticov
Carl Brochu MSFT
thanks but i need to copy other objects such as relations, indexes, extended properties, etc. as well.
I found an article http://community.discountasp.net/default.aspx f=16&m=8808 which has helped me somewhat. Basically, it states to generate script on all objects, run that script on the destination DB then run the export wizard to copy tables. However, there seems to be a bug in the 2005 import export wizard with identity inserts.
Anyway, this is beginning to be such a hassle. If i don't come up with a decent solution soon i will be going back to 2000 regretably.
John
jvheiner
Sorry, I don't understand what you are saying Could you please restate it
Thanks,
Wayne
HappyCow
http://connect.microsoft.com/
Allows you to file bugs, suggestions and follow their progress.
Scythen
johnson hk
dbabe13
Ah, that's why I never saw this. I've never been able to get it to work.
There are 2 major problems with the Copy Database function:
1) No backwards compatibility to Sql 2000. It REQUIRES the destination to be a Sql Server 2005 server (even if the source is a 2000 server or 8.0 database).
2) If your login user doesn't have privileges on ALL the databases on the server, not just the one you need to copy, it can't even enumerate the database list for you to select your database. "Server user 'username' is not a valid user in database 'otherdatabase'. (Microsoft Sql Server, Error 916). This is almost guaranteed to be the case if your database is hosted by a 3rd party vendor, and will also likely be the case in any large organization where the Sql Servers server distinct groups.
Problem 1) is marginally debatable, although I do think it should at least allow copying version 8.0 databases to Sql 2000 server. Not allowing down-stepping 9.0 to 8.0 I can understand (though it should still be allowed if only compatible options are used).
Problem 2) is pretty fatal. Copy Database is only usable if your user has privileges on ALL databases hosted on the server. So forget about 3rd party hosting altogether, and in an internal corporate environment, you need to have maximum privileges on ALL databases, or you're still out of luck.
Thanks,
Wayne