I have looked at the script of column size change and see that SSMS will create temp tables and then rename them. In test, in my - fairly small database - the change worked without a problem. But my customers have bigger tables. So my question, what - in relative terms - would constitute a "big" table? For example, I estimate that among my customers the biggest table where such change has to be done is about 500,000 rows. Is this "big" that could cause a problem? And if so, anything I can do in their SQL Server database to deal with this?
>If you are concern, generate script from SSMS and analyze it. Quite often SSMS will do modifications through creating a temp table instead of using ALTER TABLE. Could be a problem for big tables.
>
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
