i agree with thomas

well in our concern we have faced a serious issue on this one that's why i posted it here, in our concern we usually deploy the empty backup to the customer and there we run a default procedure to populate the mandatory table detail, the same procedure also used for year end updation it deletes all the existing records and reset all the identity to 1, all goes well until that day

one of our client ask us to prepare the script for the database and ask to deploy it in his server, Every thing goes well, what make us stumped was this DBCC CHECKIDENT, when the user wants the default data, we run that procedure ,we usually start identity with 1, but there it start's with 0 and the night mare begins, then i do a little Google search but no help, well then i decide to read detail in msdn finally i found it and know why it happen, then we change the entire procedure with some little tweaks and also update the clients system (Tedious but a fatal error is gone)

Every rule in a world of bits and bytes, can be bend or eventually be broken
MyBlog About Common dialog control
A Visualizer for viewing SqlCommand object script [/url]