|
|
Posted by Erland Sommarskog on 05/17/07 21:52
Steve (tinker123@gmail.com) writes:
> On May 16, 6:42 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
>> Steve (tinker...@gmail.com) 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@sommarskog.se
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
Navigation:
[Reply to this message]
|