Thank you for submitting this cool story – Trackback from SharePoint Sidekick…

First of all, I am not sure why SQL server is starting some tables with identity column 0 and some tables with 1 after using reseed.

Actually I wrote a procedure and it will start by checking whether the table in the database is having any identity column set or not.

If the table has an identity column then it will try to truncate the table data and set the reseed to 1. If you don’t use truncate then table identity column is starting from 0.

But you can’t use truncate for all the tables, some tables may throw an exception (you can use delete statement for these tables) so I wrapped the above statement with TRY block.

If it throws an error then I can catch that and use delete statement and reseed to 0.

Hope this explanation is helpful.

May not be logical but works fine for me. Have you tried and tested my solution?

Cheers,
Scriptstar

Could you explain in a few words how it works?