StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAltering candidate key in SQL Server 2005
primarykey
Id
7855337
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-21T21:14:08.217
FavoriteCount
0
LastActivityDate
2011-10-21T21:34:32.013
LastEditDate
2011-10-21T21:34:32.013
LastEditorUserId
58375
OwnerUserId
58375
ParentId
0
PostTypeId
1
Score
1
ViewCount
468
LastEditorDisplayName
text
Body
I have a rather interesting task ahead of me and I want to make sure I am thinking it out correct - I have a table <code>Part</code> that has its <code>part_id</code> being used as part of the candidate keys of several other tables (<code>A</code>, <code>B</code>, <code>C</code>). I need to drop <code>Part</code> and use <code>Product</code> instead. <code>A</code>, <code>B</code>, <code>C</code> need to have their <code>part_id</code> column (which is of type <code>bigint</code>) replaced with a new column of <code>product_id</code> (which is of datatype <code>int</code>). I need to use the <code>part_id</code> column of the tables to determine what <code>product_id</code> I need to use for each row. Here is what I am thinking is what I need to do (thoughts?): <ol> <li>create the <code>product_id</code> column in each of the tables (<code>A</code>, <code>B</code>, <code>C</code>) </li> <li>set the <code>product_id</code> of each row for each table to the appropriate value </li> <li>drop any constraints/fk/pk I have for the <code>part_id</code> column in <code>A</code>, <code>B</code>, <code>C</code></li> <li>drop the <code>part_id</code> from those tables completely</li> <li>recreate the constraints/fk/pk I dropped earlier, only have <code>product_id</code> be part of them instead</li> <li>drop the <code>Part</code> table completely</li> </ol> Can anyone see any potential issues that I may be neglecting? Thanks! Additional Info: Tables A, B, and C each have LOTS of data, so if there is more performant way, I am all ears.
Tags
<sql-server-2005><tsql><foreign-keys><database-schema><alter-table>
Title
Altering candidate key in SQL Server 2005
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDan Appleyard
UserOwnerUserId
1. USDan Appleyard
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POAltering candidate key in SQL Server 2005
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.