>>OTOH, just like any other statistics, this program is best at measuring what it measures and staying ignorant at what it doesn't.
>>
>>It would never measure me, for instance, because I use Toad instead. SSMS is so limited it's sometimes near useless. The code it generates frequently needs editing before it can run. Its error messages are sometimes misleading, sometimes just plain wrong. Today I had a case when a change of a field from decimal(14,1) to decimal(14,2) was refused, as it would require rebuilding the table. However, "alter table blabla alter column dcolxx decimal(14,2) null" passes without any messages from SQL. Ah, and, BTW, for those changes which really do require rebuilding the table, Toad generates the whole script which builds the temp table, inserts from the original table into it, drops the original table, renames temp to original, which SSMS never offered (that I remember - maybe recent versions can do that).
>
>Yes, I do understand a lot of persons prefer to use other tools.
>
>BTW, to avoid the message when you were not able to change the field type from the designer, there is a switch for that in the Tools menu.

The message says "Saving changes is not permitted.The changes you have made require the following tables to be dropped and re-created. You have either made the changesto a table that' can't be re-created or enabled the option Prevent saving changes that require the table to be re-created".

All of which is wrong. Saving changes is generally permitted, not "not permitted" in general - a qualifier is missing. "Changes... require the table to be dropped" - wrong, changing from decimal(14,1) to decimal(14,2) does not. "You have made changes to a table that can't be re-created" - I've never seen such a table. _Every_ table can be re-created, just run the create script again. "...Or you have enabled the option..." - wrong, I never touched it, it's the default of a setting I never even knew existed.

Permission to re-blog?