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

Question on using SQLBulkCopy

I need to copy large amounts of data between SQL databases, and between SQL and Access. I've been reading a lot of good explanations of SQLBulkCopy, but the only good examples I've found are written in C# and I work in VB. I'm very new to ASP.NET 2.0 (about a month) and came from Classic ASP, not .NET 1.1. I'm still getting my feet wet and I'm afraid it doesn't take much to confuse me. Can someone point me to a good article or tutorial that includes a clear example written in VB?

Diane

The MSDN Library has a decent example in all languages:

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlbulkcopy.aspx

Question on SQL job step invoking .cmd

I have a simple SQL job that is scheduled to invoke a .cmd to perform a
file copy task.
How can I get SQL job to report to correct status when the copy task
fails, such as due to connectivity issue, or file not found, and etc?
thanks.One option is to capture the return code and do a raiserror
if the return code <> 0. Along the lines of:
DECLARE @.ret int
EXEC @.ret = master..xp_cmdshell 'copy ...etc' , NO_OUTPUT
IF @.ret <> 0 RAISERROR('File copy error',16, 1)
-Sue
On 28 Jul 2006 08:23:49 -0700, "Rose" <rose.say@.gmail.com>
wrote:

>I have a simple SQL job that is scheduled to invoke a .cmd to perform a
>file copy task.
>How can I get SQL job to report to correct status when the copy task
>fails, such as due to connectivity issue, or file not found, and etc?
>thanks.

Question on SQL job step invoking .cmd

I have a simple SQL job that is scheduled to invoke a .cmd to perform a
file copy task.
How can I get SQL job to report to correct status when the copy task
fails, such as due to connectivity issue, or file not found, and etc?
thanks.One option is to capture the return code and do a raiserror
if the return code <> 0. Along the lines of:
DECLARE @.ret int
EXEC @.ret = master..xp_cmdshell 'copy ...etc' , NO_OUTPUT
IF @.ret <> 0 RAISERROR('File copy error',16, 1)
-Sue
On 28 Jul 2006 08:23:49 -0700, "Rose" <rose.say@.gmail.com>
wrote:
>I have a simple SQL job that is scheduled to invoke a .cmd to perform a
>file copy task.
>How can I get SQL job to report to correct status when the copy task
>fails, such as due to connectivity issue, or file not found, and etc?
>thanks.sql