question on warnings recieved after running sp_repladdcolumn and sp_repldropcolumn

copy/past of sample error:
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'mytestdb' because schema replication is performed.
Warning: The table 'GeneralInventory' has been created but its maximum row
size (9929) 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.
Warning: The table 'conflict_mytestdb_GeneralInventory' has been created but
its maximum row size (11924) 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.
this was after a sp_repldropcolumn? and I recieved similar messages after
performing an sp_repladdcolumn? What are they talking about? what problems
could this cause? what do I need to do?
any info is appreciated... thanks.
ignore these warnings. The first one is the only meaningful one.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"djc" <noone@.nowhere.com> wrote in message
news:%23$oVUw3XEHA.2448@.TK2MSFTNGP09.phx.gbl...
> copy/past of sample error:
> --
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'mytestdb' because schema replication is performed.
> Warning: The table 'GeneralInventory' has been created but its maximum row
> size (9929) 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.
> Warning: The table 'conflict_mytestdb_GeneralInventory' has been created
but
> its maximum row size (11924) 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.
> --
> this was after a sp_repldropcolumn? and I recieved similar messages after
> performing an sp_repladdcolumn? What are they talking about? what problems
> could this cause? what do I need to do?
> any info is appreciated... thanks.
>
|||This is a general SQL Server warning and isn't particular to replication eg
you can 2 varchar (8000) cols as you want to a table and the second time
there'll be this warning (if you do it in QA), as potentially you might
exceed the 8060ish max row size.
Regards,
Paul Ibison
|||good. Thank you!
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:Op8xu83XEHA.3664@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> ignore these warnings. The first one is the only meaningful one.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "djc" <noone@.nowhere.com> wrote in message
> news:%23$oVUw3XEHA.2448@.TK2MSFTNGP09.phx.gbl...
row[vbcol=seagreen]
or[vbcol=seagreen]
> exceeds
> but
resulting[vbcol=seagreen]
after[vbcol=seagreen]
problems
>
|||thanks Paul.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:evHKNn4XEHA.3016@.tk2msftngp13.phx.gbl...
> This is a general SQL Server warning and isn't particular to replication
eg
> you can 2 varchar (8000) cols as you want to a table and the second time
> there'll be this warning (if you do it in QA), as potentially you might
> exceed the 8060ish max row size.
> Regards,
> Paul Ibison
>
sql