Re: SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 17 May 2007 21:52:57 +0000 (UTC)
Steve (tinker123@xxxxxxxxx) writes:
On May 16, 6:42 pm, Erland Sommarskog <esq...@xxxxxxxxxxxxx> wrote:
Steve (tinker...@xxxxxxxxx) writes:
We just migrated to SqlServer 2005. When I import tables from from
SqlServer database into another the identity fields get switched off
from being identities.
How can I prevent that from happening?
Seems like the way to go is to click Edit SQL and add the IDENTITY
property manually.
Our databases have several hundred tables, is there a more practical
solution ( I will talk to my admin and boss about getting service pack
2 )
I hope not all of them are using the IDENTITY property, because that would
indicate a poor database design.
What exactly is the reason you are doing this huge transfer operation?
If you want to copy the entire database, using BACKUP/RESTORE is both
easier and more reliable.
The wizard anyway seems very unpractical. The missing IDENTITY property
is only the start of the problems. It does not copy keys and indexes,
and most certainly you don't want that.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities
- From: Steve
- Re: SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities
- From: Erland Sommarskog
- Re: SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities
- From: Steve
- SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities
- Prev by Date: Server Hardware
- Next by Date: Microsoft SQL Server DBA's required immediately
- Previous by thread: Re: SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities
- Next by thread: SqlServer 2005: How *best* to copy one database to another
- Index(es):
Relevant Pages
|