[dba-SQLServer] Migrating tables to a new database

JWColby jwcolby at colbyconsulting.com
Mon Jan 22 09:57:45 CST 2007


COOL!  Thanks James. 


John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of James
Barash
Sent: Monday, January 22, 2007 10:34 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Migrating tables to a new database

John:

If you are using Enterprise Manager, you can use the Import Data Wizard and
instead of using Copy Tables, use Copy Objects and Data. Then uncheck copy
all objects and select the table you need to copy and it will create the
table with all its indexes, relationships, etc. if there are any and then
copy the data. I use this all the time and found it works very well.
Hope this helps.

James Barash

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Monday, January 22, 2007 6:41 AM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Migrating tables to a new database

Is it possible to migrate a table, complete with all indexes and any other
attributes to another database?  Whenever I do an Import Data it just kind
of does a generic "here's your data" kind of thing.
 
The business I am getting into involves taking lists of addresses along
which includes what I call survey data.  There is a TON of preprocessing
involved getting the addresses run through a set of processes to check with
the US Postal Service to ensure that the address is deliverable - CASS (does
the address conform to the USPS system), DPV (Delivery Point Validation -
the address exists), and NCOA which means essentially "have they changed
addresses".  Given all of the preprocessing, I really want to do this out in
a separate database for each list, where when I am finished a completely
processed set of records exists.
 
Having done all of that, I need to merge the data into a master database of
people, valid addresses, and people at addresses.  For technical reasons I
need to be able to track where people have lived.
 
I have processed a huge list and now have a database with information about
the people in THIS LIST.  I am considering building up my People / Address /
PeopleAtAddress tables inside of this first list database, and then later
migrating these three tables out to a separate database.  I do not wish to
do that however if I am going to lose all of the indexes I set up etc.
 
Any pointers on this matter?
 
John W. Colby
Colby Consulting
www.ColbyConsulting.com
 
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com




More information about the dba-SQLServer mailing list