Importing Data w/ Enterprise Manager

This post is more than 2 years old.

So, I've noticed that when I import data using Enterprise Manager, it always seems to miss the primary keys and other constraints. Turns out I wasn't using the right option to import my data. I would chose:

Copy table(s) and view(s) from the source database.

However, what I needed to do was:

Copy objects and data between SQL Server databases.

Another thing to watch out for - when given a chance to "Use default options", turn this off and in the Options page, deselect the security options. I'm not sure why this causes problems, but it did with my test. (Kudos to my boss, David An, for this tip!)

Now for a small rant. While Enterprise Manager is a great tool for SQL Server, the interface does some things really stupid. For example - everytime you right click on a remote DB, the tool sends out a ping/request/whatever. However, if you move your mouse while the tool is waiting, you lose the right menu when it finally appears. This is even more of a pain when you are just trying to reconnect and have to wait for the right click menu option, Connect, to show up. Another thing thats a pain in the rear are wizards that don't allow you to look at the rest of the application. So, let's say I'm doing that import from db A to db B. Let's say I forget the name of db B. Once I'm in the wizard, I can't click and scroll down in the rest of Enterprise Manager to get to my db and examine it.

Raymond Camden's Picture

About Raymond Camden

Raymond is a senior developer evangelist for Adobe. He focuses on document services, JavaScript, and enterprise cat demos. If you like this article, please consider visiting my Amazon Wishlist or donating via PayPal to show your support. You can even buy me a coffee!

Lafayette, LA https://www.raymondcamden.com

Archived Comments

Comment 1 by Dimo Michailov posted on 3/12/2003 at 9:31 PM

Kudos to you for posting this! :) I am one of those who have to recreate primary keys, indexes, etc. when copying database objects.

Comment 2 by Tjarko posted on 3/26/2003 at 5:04 PM

I found this out myself a couple of months ago.. you need to deselect the security check because else the logged in account will be copied to the server your exporting or importing to.. and that account may not exist on that server.

SQL server is great.. but also a pain.. especially with these kind of little nifty things you can''t find in the documentation.. well you can.. after a couple of hours...

Comment 3 by Bill posted on 4/9/2003 at 11:33 PM

The "easiest" way to do this fast is simply to move the mdb ... renaming as required under the new database name you''ve created (as the new database created will automatically create a db and lock). I''ve never found a reliable way to migrate a db with the dts and retain the column cardinality attributes.

Comment 4 by Raymond Camden posted on 4/12/2003 at 3:32 PM

Bill, MDB files are for MS Access. I''m talking about SQL Server dbs here. :)