Reseed doesn''t change column properties?
-
I have a table with an Identity column (1,1). I find out from the business unit that they don't want the identity fields to start with 1, they want to start out with 100,000,000. Okay, so I run the DBCC command to reseed the column and it works.
Now the business unit wants a screen shot of the table properties to prove that what I did works (so they can attach it to the SDLC document trail). Only problem is, when I open the table via Modify and look at the Identity specs, it still has a Seed of 1 listed.
What the HECK????
DBCC
CheckIdent ('MyTable', RESEED, 100000000) is the command I used. So, can anyone tell me why the table properties don't show this new reseed? Even when the table is empty?
Thanks,
-
Because the DBCC CheckIdent is not modifying the metadata used to create the table, it is simply resetting the starting seed number to be used for future inserts into the table.
-
Actually, I just discovered that if you run the DBCC command with NoReseed after the original ReSeed command (if there are values in the table), it will reset on the table properties properly.
If there are no values in the table, however, you're stuck. Which means you can't "trust" the Identity Specification on the table if it's been reseeded prior to data population.
-
Interesting. Of course, I've never had to do to what you needed, so I wouldn't have even thought of the NoResees. something to keep in the back of mind (as long as i don't forget it
)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply