Post reply

Prevent option for saving changes

  • December 8, 2011 at 9:21 am

    #249384

    When connected to the Management Studio on a SQL Server 2008 R2 server, I modified an existing table using 'Design' [also tried 'Add column'] ... after the two columns were added I tried to save the changes and received the message below. I have not purposely turned on any "protection" and have not been able to locate where to turn it off. I can successfully use 'alter table tabname add colname ...' but that does not place the column where we need it [because of how some of the ERP procedures are written].

    "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."

    Can someone enlighten me please?

    Thank you.

  • December 8, 2011 at 9:39 am

    #1418779

    Ellen-477471 (12/8/2011)

    When connected to the Management Studio on a SQL Server 2008 R2 server, I modified an existing table using 'Design' [also tried 'Add column'] ... after the two columns were added I tried to save the changes and received the message below. I have not purposely turned on any "protection" and have not been able to locate where to turn it off. I can successfully use 'alter table tabname add colname ...' but that does not place the column where we need it [because of how some of the ERP procedures are written].

    "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."

    Can someone enlighten me please?

    Thank you.

    [/URL]

    It's on by default I think.

    Forever trying to learn
    My blog - http://www.cadavre.co.uk/
    For better, quicker answers on T-SQL questions, click on the following...http://www.sqlservercentral.com/articles/Best+Practices/61537/
    For better, quicker answers on SQL Server performance related questions, click on the following...http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • December 8, 2011 at 9:55 am

    #1418797

    Thank you so much. That was exactly the problem. Such simple things can waste so much time!

    You would think that searching BOL, using keywords from the error message, something would have pointed me to the solution.

    Thank goodness for this forum.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply