February 1, 2013 at 4:39 am
Hello,
We recently have been using the December release of SSDT to script out a database deployment and noticed that the script generated DROP and the CREATE statements for tables, even though the table structure was not being changed.
We resolved this by dropping the clustered index on the table but I am keen to find out why this would be an issue.
Has anyone else run into this problem?
Any advice would be most appreciated.
Andrew
March 11, 2013 at 10:18 pm
I'm not quite sure why it does that but I noticed that also.
I now make it a habit to review the code before any changes and getting rid of "risky" stuff like unnecessary drops and creates. At least in the code I've seen, it always seems to create a table with a temp name with the same or new schema (I think it does this blindly), copies the data to the new table, then drops the old table, and lastly renames the new table with the old table name.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply