dbTalk Databases Forums  

SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities

comp.databases.ms-sqlserver comp.databases.ms-sqlserver


Discuss SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities in the comp.databases.ms-sqlserver forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Steve
 
Posts: n/a

Default SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities - 05-16-2007 , 11:34 AM






Hi;

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?

Thanks in advance for any information

Steve





-------------------------------------------------------------------
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600


Reply With Quote
  #2  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities - 05-16-2007 , 05:42 PM






Steve (tinker123 (AT) gmail (DOT) com) writes:
Quote:
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.

Quote:
Microsoft SQL Server Management Studio
9.00.1399.00
This is the RTM version. I recommend that you install SP2, which
has several enhancements to the tools. If you plan to use maintenance
plans, make sure to get hold a GDR that fixes two serious bugs in
SP2 with maintenance plans.




--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx


Reply With Quote
  #3  
Old   
Steve
 
Posts: n/a

Default Re: SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities - 05-17-2007 , 09:49 AM



On May 16, 6:42 pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:
Quote:
Steve (tinker... (AT) gmail (DOT) 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 )



Reply With Quote
  #4  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities - 05-17-2007 , 04:52 PM



Steve (tinker123 (AT) gmail (DOT) com) writes:
Quote:
On May 16, 6:42 pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:
Steve (tinker... (AT) gmail (DOT) 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 (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.