"Jay" <nospam@nospam.org> wrote in message
news:eFRaUJX9HHA.5160@TK2MSFTNGP05.phx.gbl...
> When I try to alter a table with:
>
> DECLARE @Beg datetime
> DECLARE @End datetime
>
> SET @Beg = getdate()
> ALTER TABLE __TABLE__
> ALTER COLUMN _COLUMN_ VARCHAR(250)
> SET @End = getdate()
>
> PRINT DATEDIFF(second, @Beg, @End)
>
> I get the message:
>
> Warning: The table '__TABLE__' has been created but its maximum row size
> (15334) exceeds the maximum number of bytes per row (8060). INSERT or
> UPDATE of a row in this table will fail if the resulting row length
> exceeds 8060 bytes.
> Server: Msg 4928, Level 16, State 1, Line 5
> Cannot alter column '__COLUMN__' because it is 'REPLICATED'.
>
> Now I would understand this on production, but the table isn't replicated
> on the dev system, where I ran this. I do know that the databases were
> created from production backups.
>
>

"Jay" <nospam@nospam.org> wrote in message
news:eFRaUJX9HHA.5160@TK2MSFTNGP05.phx.gbl...
> When I try to alter a table with:
>
> DECLARE @Beg datetime
> DECLARE @End datetime
>
> SET @Beg = getdate()
> ALTER TABLE __TABLE__
> ALTER COLUMN _COLUMN_ VARCHAR(250)
> SET @End = getdate()
>
> PRINT DATEDIFF(second, @Beg, @End)
>
> I get the message:
>
> Warning: The table '__TABLE__' has been created but its maximum row size
> (15334) exceeds the maximum number of bytes per row (8060). INSERT or
> UPDATE of a row in this table will fail if the resulting row length
> exceeds 8060 bytes.
> Server: Msg 4928, Level 16, State 1, Line 5
> Cannot alter column '__COLUMN__' because it is 'REPLICATED'.
>
> Now I would understand this on production, but the table isn't replicated
> on the dev system, where I ran this. I do know that the databases were
> created from production backups.
>
>