When altering an existing table in the table designer, certain change types cannot be saved. - by Ray Dark

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 316372 Comments
Status Closed Workarounds
Type Bug Repros 7
Opened 12/8/2007 1:10:20 PM
Access Restriction Public


I receive the following error message when trying to save changes in the SSMS 2008 table designer:

"Saving changes is not permitted.  The changes you have made require the following tables to be dropped and re-created.  You have either made changes to a table that can't be re-created or enabled the option Prevent saving changes that require the table to be re-created.
DBType" (= name of table that cannot be saved)

I am logged on as a sysadmin when this happens.  The computer has nothing on it but Vista RTM and SQL 2008 November CTP using domain accounts for all services (except SQL Browser which uses NT Authority).  This is a default instance with default settings used for setup and all components installed.   I have not experienced this behavior in any SQL 2000 or SQL 2005 installation with any service pack up through SQL 2005 SP2.

This error does not occur if the same modification is made via an ALTER TABLE statement in a query window.
Sign in to post a comment.
Posted by Microsoft on 5/11/2011 at 9:19 PM
Hi ejerome,

We took a look at this bug along with several others recently. Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future. However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

Thanks for writing in to Microsoft.

Posted by MXJ on 1/20/2011 at 4:41 PM
Okay, it's been almost four years now. Any updates on this issue yet?
Posted by Ray Dark on 1/9/2008 at 6:56 AM
I understand that the warning is to prevent loss of CDC settings, but wouldn't it be possible to use an ALTER statement rather than DROP/CREATE behind the scenes, at least for simple things like changing the nullability of a column? This warning prevents so many types of changes that it makes the designer all but useless if you are using CDC anywhere in the database and therefore can't disable the warning. An alternative might be to have the warning message be explicit about the CDC settings loss and have YES and NO buttons to allow the user to decide whether to proceed with the change, rather than forcing them to clear the designer configuration option, save the table, and then reset the configuration option.
Posted by Microsoft on 12/14/2007 at 5:36 AM
Thanks for reporting the issue on SQL Server Management Studio titled "When altering an existing table in the table designer, certain change types cannot be saved.".

We are investigating the issue and we will keep you posted.

- Balaji Rathakrishnan