Lỗi the automatically saved settings file visual studio
I moved my documents from d drive back to c and this is what I got in both Visual Studio 2012 and Microsoft SQL Server Management Studio Show --- Microsoft Visual Studio --- The automatically saved settings file 'visual studio 2012\settings\CurrentSettings.vssettings' cannot be found. You can change this file on the 'Import and Export Settings' Tools Options page. The IDE will use your most recent settings for this session. --- OK --- ------ Microsoft SQL Server Management Studio --- The automatically saved settings file 'sql server management studio\Settings\SQL Server Management Studio\CurrentSettings-2013-06-06.vssettings' cannot be found. You can change this file on the 'Import and Export Settings' Tools Options page. The IDE will use your most recent settings for this session. --- OK --- To fix it1. Go to Tools/Options 2. Go to Environment/Import and Export Settings and change the path to existing one. I've used the path to my documents Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Saving changes is not permitted error message in SSMS
In this articleThis article helps you work around the problem in which you receive an error message when you try to save a table in SQL Server Management Studio (SSMS). Original product version: SQL Server Original KB number: 956176 SymptomsWhen you try to save a table after making changes to the table using Designer in SQL Server management Studio, you may receive the following error message: Saving changes is not permitted. The changes that 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. This problem occurs when you make one or more of the following changes to the table:
CauseThis problem occurs because the Prevent saving changes that require the table re-creation option is enabled by default in SQL Server Management Studio. When you change a table so that you alter the metadata structure of the table, and then you save the table, the table must be re-created based on these changes. This may result in the loss of metadata and in a direct loss of data during the re-creation of the table. If you enable the Prevent saving changes that require the table re-creation option in the Designer section of the SQL Server Management Studio (SSMS) Options window, you receive the error message that is mentioned in the 'Symptoms' section. WorkaroundTo work around this problem, use For example, to change MyDate column of type datetime in at table called MyTable to accept NULL values you can use:
Important We strongly recommend that you do not work around this problem by turning off the Prevent saving changes that require table re-creation option. For more information about the risks of turning off this option, see the 'More information' section. More informationTo change the Prevent saving changes that require the table re-creation option, follow these steps:
Note If you disable this option, you are not warned when you save the table that the changes that you made have changed the metadata structure of the table. In this case, data loss may occur when you save the table. Risk of turning off the "Prevent saving changes that require table re-creation" optionAlthough turning off this option can help you avoid re-creating a table, it can also lead to changes being lost. For example, suppose that you enable the Change Tracking feature in SQL Server to track changes to the table. When you perform an operation that causes the table to be re-created, you receive the error message that is mentioned in the section. However, if you turn off this option, the existing change tracking information is deleted when the table is re-created. Therefore, we recommend that you do not work around this problem by turning off the option. To determine whether the Change Tracking feature is enabled for a table, follow these steps:
When the |