Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ramdas
Posting Yak Master
181 Posts |
 Posted - 2003-02-24 : 21:31:42
|
| Hi,I have some tables in my database which have columns defined as Identity and are Primary keys. Is it a good choice to have identity columns as PK's since when the table(s) has to be moved from Dev to Prod, maintaing the Identity Sequence could pose a problem. also if these columns are Foreign Keyed with other tables, it could complicate the issue.I have run into these issues especially in one situation the the table was moved from Dev to Prod, the data was transferred. There was a bug the dat had to be deleted from Tables in Prod. When the time came to moving data again, the identity sequence was lost in Production.Any ideas/suggestions as to how to avoid such pit falls.Ramdas NarayananSQL Server DBA |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-02-24 : 21:38:04
|
| I guess you are talking about static data otherwise there is no problem as the tables would be empty.In which case populate the tables via scripts. Run the scripts as part of the promotion so that the identities are preserved.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Identity Cols and Primary Keys