November 7, 2010 at 10:33 pm
when I changed the Table Data type in column, it doesn't allow to save in SSMS 2008 R2.
see the attached image or http://micro.harshana.net/day/2010/11/08
Harshana Weerasinghe
www.harshana.net
www.DevSmart.net
November 7, 2010 at 10:56 pm
Is the table replicated?
Any foreign key reference?
Try to alter the table using SQL command.
November 7, 2010 at 11:09 pm
use the syntax as:
alter table tablename
ALTER COLUMN columnname INT NOT NULL
or if you really want to modify in the UI, do the following:
Tools ->Options-> Designers -> Table and Database Designers -> uncheck the option "Prevent saving changes that require table re-creation"
so no, there is no bug....
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
November 7, 2010 at 11:16 pm
normally I'm using command, It is ok for me, but I've teched to newby, to do using SSMS, so that was a headache, coz. using commands is not much easy for them. it is working properly in SSMS 2005.
Harshana Weerasinghe
www.harshana.net
www.DevSmart.net
November 7, 2010 at 11:21 pm
thanks a lot, i unchecked the option "Prevent saving changes that require table re-creation" and it worked.
Harshana Weerasinghe
www.harshana.net
www.DevSmart.net
November 7, 2010 at 11:36 pm
Harshana-680014 (11/7/2010)
normally I'm using command, It is ok for me, but I've teched to newby, to do using SSMS, so that was a headache, coz. using commands is not much easy for them. it is working properly in SSMS 2005.
as I said....
or if you really want to modify in the UI, do the following:
Tools ->Options-> Designers -> Table and Database Designers -> uncheck the option "Prevent saving changes that require table re-creation"
so no, there is no bug....
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
November 8, 2010 at 1:25 am
Harshana-680014 (11/7/2010)
see the attached image or http://micro.harshana.net/day/2010/11/08%5B/quote%5D
Not a bug, a feature. It's to prevent (or at least warn) people from making a change that requires recreating the entire table. SSMS does those type of changes by creating a new table, copying data over, recreating constraints and indexes and then dropping the old table.
I'm sure you can see how well that would work with a few million rows in the table. Hence the 'prevent changes' feature.
but I've teched to newby, to do using SSMS, so that was a headache,
Rather teach the 'newbies' to use scripts. It will save them uncounted woes in the future if you teach them correctly from the start.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply