"Text column data incomplete" error during replication

I'm doing a transactional replication for the first time between 2
servers.
After 14 minutes of running (according to the logs), the replicaton
crashes. This is what I find in the log file generated by the
distribution agent. It starts bulk copying data from many tables until
it finally crashes on the first copy.
Any ideas why?
What does it mean 'Text column data incomplete'.
Table Parcel has 2 text columns that can be NULL.
Also, at the time the replication was taking place, it is possible
other transactions might have been being added/deleted from
Parcel......could this produce this type of error?
Here goes the erro log:
Bulk copying data into table 'Parcel'
:
Bulk copying data into table 'Item Specific Cost Factor'
:
Bulk copying data into table 'Item Appraisal Details'
:
:
Agent message code 20037. The process could not bulk copy into table
'"Parcel"'.
[6/16/2004 10:37:08 AM]SERVER.distribution: {call
sp_MSadd_distribution_history(4, 6, ?, ?, 0, 0, 0.00, 0x01, 1, ?,
414, 0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts: ErrorId = 9,
Transaction Seqno = 0004158900000066000100000001, Command ID = 414
Message: Replication-Replication Distribution Subsystem: agent
SERVER-Acadia_Final_Assessor-Acadia_Final_Assessor-68.216.171.51-4
failed.
The process could not bulk copy into table '"Parcel"'.[6/16/2004
10:37:08 AM]SERVER.distribution: {call sp_MSadd_repl_alert(3, 4, 9,
14151, ?, 414, N'SERVER', N'Acadia_Final_Assessor', N'68.216.171.51',
N'TestDB', ?)}
ErrorId = 9, SourceTypeId = 1
ErrorCode = ''
ErrorText = 'select * from "Parcel Item" where 1 = 2
'
[6/16/2004 10:37:08 AM]SERVER.distribution: {call
sp_MSadd_repl_error(9, 0, 1, ?, N'', ?)}
Category:COMMAND
Source: Failed Command
Number:
Message: select * from "Parcel Item" where 1 = 2
ErrorId = 9, SourceTypeId = 4
ErrorCode = 'S1000'
ErrorText = 'Text column data incomplete'
[6/16/2004 10:37:09 AM]SERVER.distribution: {call
sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
Category:ODBC
Source: 68.216.171.51
Number: S1000
Message: Text column data incomplete
ErrorId = 9, SourceTypeId = 4
ErrorCode = 'S1000'
ErrorText = 'Text column data incomplete'
[6/16/2004 10:37:09 AM]SERVER.distribution: {call
sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: S1000
Message: Text column data incomplete
ErrorId = 9, SourceTypeId = 4
ErrorCode = 'S1000'
ErrorText = 'Text column data incomplete'
[6/16/2004 10:37:09 AM]SERVER.distribution: {call
sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: S1000
Message: Text column data incomplete
ErrorId = 9, SourceTypeId = 4
ErrorCode = 'S1000'
ErrorText = 'Text column data incomplete'
[6/16/2004 10:37:09 AM]SERVER.distribution: {call
sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: S1000
Message: Text column data incomplete
ErrorId = 9, SourceTypeId = 4
ErrorCode = 'S1000'
ErrorText = 'Text column data incomplete'
[6/16/2004 10:37:09 AM]SERVER.distribution: {call
sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: S1000
Message: Text column data incomplete
[6/16/2004 10:37:09 AM]68.216.171.51.TestDB: exec
dbo.sp_MSupdatelastsyncinfo N'SERVER',N'Acadia_Final_Assessor',
N'Acadia_Final_Assessor', 0, 6, N'The process could not bulk copy into
table ''"Parcel"''.'
Disconnecting from Subscriber '......'
Disconnecting from Distributor 'SERVER'
Disconnecting from Distributor History 'SERVER'
is the database collations on the subscriber and publisher the same?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Rocio" <rocio.katsanis@.softwareservices.net> wrote in message
news:7b914006.0406161119.2936cea7@.posting.google.c om...
> I'm doing a transactional replication for the first time between 2
> servers.
> After 14 minutes of running (according to the logs), the replicaton
> crashes. This is what I find in the log file generated by the
> distribution agent. It starts bulk copying data from many tables until
> it finally crashes on the first copy.
> Any ideas why?
> What does it mean 'Text column data incomplete'.
> Table Parcel has 2 text columns that can be NULL.
> Also, at the time the replication was taking place, it is possible
> other transactions might have been being added/deleted from
> Parcel......could this produce this type of error?
> Here goes the erro log:
> Bulk copying data into table 'Parcel'
> :
> Bulk copying data into table 'Item Specific Cost Factor'
> :
> Bulk copying data into table 'Item Appraisal Details'
> :
> :
> Agent message code 20037. The process could not bulk copy into table
> '"Parcel"'.
> [6/16/2004 10:37:08 AM]SERVER.distribution: {call
> sp_MSadd_distribution_history(4, 6, ?, ?, 0, 0, 0.00, 0x01, 1, ?,
> 414, 0x01, 0x01)}
> Adding alert to msdb..sysreplicationalerts: ErrorId = 9,
> Transaction Seqno = 0004158900000066000100000001, Command ID = 414
> Message: Replication-Replication Distribution Subsystem: agent
> SERVER-Acadia_Final_Assessor-Acadia_Final_Assessor-68.216.171.51-4
> failed.
> The process could not bulk copy into table '"Parcel"'.[6/16/2004
> 10:37:08 AM]SERVER.distribution: {call sp_MSadd_repl_alert(3, 4, 9,
> 14151, ?, 414, N'SERVER', N'Acadia_Final_Assessor', N'68.216.171.51',
> N'TestDB', ?)}
> ErrorId = 9, SourceTypeId = 1
> ErrorCode = ''
> ErrorText = 'select * from "Parcel Item" where 1 = 2
> '
> [6/16/2004 10:37:08 AM]SERVER.distribution: {call
> sp_MSadd_repl_error(9, 0, 1, ?, N'', ?)}
> Category:COMMAND
> Source: Failed Command
> Number:
> Message: select * from "Parcel Item" where 1 = 2
> ErrorId = 9, SourceTypeId = 4
> ErrorCode = 'S1000'
> ErrorText = 'Text column data incomplete'
> [6/16/2004 10:37:09 AM]SERVER.distribution: {call
> sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
> Category:ODBC
> Source: 68.216.171.51
> Number: S1000
> Message: Text column data incomplete
> ErrorId = 9, SourceTypeId = 4
> ErrorCode = 'S1000'
> ErrorText = 'Text column data incomplete'
> [6/16/2004 10:37:09 AM]SERVER.distribution: {call
> sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
> Category:ODBC
> Source: ODBC SQL Server Driver
> Number: S1000
> Message: Text column data incomplete
> ErrorId = 9, SourceTypeId = 4
> ErrorCode = 'S1000'
> ErrorText = 'Text column data incomplete'
> [6/16/2004 10:37:09 AM]SERVER.distribution: {call
> sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
> Category:ODBC
> Source: ODBC SQL Server Driver
> Number: S1000
> Message: Text column data incomplete
> ErrorId = 9, SourceTypeId = 4
> ErrorCode = 'S1000'
> ErrorText = 'Text column data incomplete'
> [6/16/2004 10:37:09 AM]SERVER.distribution: {call
> sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
> Category:ODBC
> Source: ODBC SQL Server Driver
> Number: S1000
> Message: Text column data incomplete
> ErrorId = 9, SourceTypeId = 4
> ErrorCode = 'S1000'
> ErrorText = 'Text column data incomplete'
> [6/16/2004 10:37:09 AM]SERVER.distribution: {call
> sp_MSadd_repl_error(9, 0, 4, ?, N'S1000', ?)}
> Category:ODBC
> Source: ODBC SQL Server Driver
> Number: S1000
> Message: Text column data incomplete
> [6/16/2004 10:37:09 AM]68.216.171.51.TestDB: exec
> dbo.sp_MSupdatelastsyncinfo N'SERVER',N'Acadia_Final_Assessor',
> N'Acadia_Final_Assessor', 0, 6, N'The process could not bulk copy into
> table ''"Parcel"''.'
> Disconnecting from Subscriber '......'
> Disconnecting from Distributor 'SERVER'
> Disconnecting from Distributor History 'SERVER'
|||Hi Hillary,
I treid the same replication 3 more times, and the erro I got on those 3
times was different than the one I published here. Now the error is:
Category:SQLSERVER
Source: <IP of subscriber...>
Number: 2812
Message: Could not find stored procedure 'sp_MSupd_Entity Address'.
[6/16/2004 8:24:39 PM]68.216.171.51.TestDB: exec
dbo.sp_MSupdatelastsyncinfo N'SERVER',N'Acadia_Final_Assessor',
N'Acadia_Final_Assessor', 0, 6, N'Error at parameter 199 during
datastream processing of parameterized command.'
Disconnecting from Subscriber '<IP of subscriber...>'
Disconnecting from Distributor 'SERVER'
Disconnecting from Distributor History 'SERVER'
If I looked carefully at this log file, and it seems to me that such
stored procedure is somehow created:
[6/16/2004 8:01:12 PM]<IP of subscriber...>.TestDB: create procedure
"[sp_MSupd_Entity Address]"
@.c1 int,@.c2 int,@.c3 int,@.c4 int,@.c5 int,@.c6 char(4),@.c7 int,@.c8 bit,@.c9
int,@.c10 varchar(500),@.pkc1 int
,@.bitmap binary(2)
as
if substring(@.bitmap,1,1) & 1 = 1
begin
update "Entity Address" set
"Address ID" = case substring(@.bitmap,1,1) & 1 when 1 then @.c1 else
"Address ID" end
,"Entity ID" = case substring(@.bitmap,1,1) & 2 when 2 then @.c2 else
"Entity ID" end
,"City ID" = case substring(@.bitmap,1,1) & 4 when 4 then @.c3 else "City
ID" end
,"State ID" = case substring(@.bitmap,1,1) & 8 when 8 then @.c4 else
"State ID" end
,"Postal Code ID" = case substring(@.bitmap,1,1) & 16 when 16 then @.c5
else "Postal Code ID" end
,"Zip Last 4" = case substring(@.bitmap,1,1) & 32 when 32 then @.c6 else
"Zip Last 4" end
,"Country ID" = case substring(@.bitmap,1,1) & 64 when 64 then @.c7 else
"Country ID" end
,"Primary Address" = case substring(@.bitmap,1,1) & 128 when 128 then @.c8
else "Primary Address" end
,"Address Type ID" = case substring(@.bitmap,2,1) & 1 when 1 then @.c9
else "Address Type ID" end
,"Address Lines" = case substring(@.bitmap,2,1) & 2 when 2 then @.c10 else
"Address Lines" end
where "Address ID" = @.pkc1
if @.@.rowcount = 0
if @.@.microsoftversion>0x07320000
exec sp_MSreplraiserror 20598
end
else
begin
update "Entity Address" set
"Entity ID" = case substring(@.bitmap,1,1) & 2 when 2 then @.c2 else
"Entity ID" end
,"City ID" = case substring(@.bitmap,1,1) & 4 when 4 then @.c3 else "City
ID" end
,"State ID" = case substring(@.bitmap,1,1) & 8 when 8 then @.c4 else
"State ID" end
,"Postal Code ID" = case substring(@.bitmap,1,1) & 16 when 16 then @.c5
else "Postal Code ID" end
,"Zip Last 4" = case substring(@.bitmap,1,1) & 32 when 32 then @.c6 else
"Zip Last 4" end
,"Country ID" = case substring(@.bitmap,1,1) & 64 when 64 then @.c7 else
"Country ID" end
,"Primary Address" = case substring(@.bitmap,1,1) & 128 when 128 then @.c8
else "Primary Address" end
,"Address Type ID" = case substring(@.bitmap,2,1) & 1 when 1 then @.c9
else "Address Type ID" end
,"Address Lines" = case substring(@.bitmap,2,1) & 2 when 2 then @.c10 else
"Address Lines" end
where "Address ID" = @.pkc1
if @.@.rowcount = 0
if @.@.microsoftversion>0x07320000
exec sp_MSreplraiserror 20598
end
however, if I look at TestDB in my subscriber, I can find
[sp_MSupd_Entity Address] but not sp_MSupd_Entity Address, note one is
with brackets, the other not.
why 2 sp's anyway (with & without brackets)?
how can I control the creation of this procedure? I looked at the
properties tab of this publictaion at the Publisher, under Article
Entity Address, and make sure all the options are selected (e.g. Replace
INSERT commands with this stored procedure, etc).
The only option I could not access is the one at the very bottom that
causes replication to use the columns name. It was just enabled.
Any ideas?
btw: your book about Transactional & Snapshot replication looks good, I
haven't found a good book on replication yet! Is it out already?
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
|||on your publisher do this
sp_scriptpublicationcustomprocs 'publicationName'
then in your results pan, copy the results and then paste them into another ISQLW window which you open into your subsciption database. then execute this script there.
Restart your distribution agent.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Rocio Katsanis" wrote:

> Hi Hillary,
> I treid the same replication 3 more times, and the erro I got on those 3
> times was different than the one I published here. Now the error is:
> Category:SQLSERVER
> Source: <IP of subscriber...>
> Number: 2812
> Message: Could not find stored procedure 'sp_MSupd_Entity Address'.
> [6/16/2004 8:24:39 PM]68.216.171.51.TestDB: exec
> dbo.sp_MSupdatelastsyncinfo N'SERVER',N'Acadia_Final_Assessor',
> N'Acadia_Final_Assessor', 0, 6, N'Error at parameter 199 during
> datastream processing of parameterized command.'
> Disconnecting from Subscriber '<IP of subscriber...>'
> Disconnecting from Distributor 'SERVER'
> Disconnecting from Distributor History 'SERVER'
> If I looked carefully at this log file, and it seems to me that such
> stored procedure is somehow created:
> [6/16/2004 8:01:12 PM]<IP of subscriber...>.TestDB: create procedure
> "[sp_MSupd_Entity Address]"
> @.c1 int,@.c2 int,@.c3 int,@.c4 int,@.c5 int,@.c6 char(4),@.c7 int,@.c8 bit,@.c9
> int,@.c10 varchar(500),@.pkc1 int
> ,@.bitmap binary(2)
> as
> if substring(@.bitmap,1,1) & 1 = 1
> begin
> update "Entity Address" set
> "Address ID" = case substring(@.bitmap,1,1) & 1 when 1 then @.c1 else
> "Address ID" end
> ,"Entity ID" = case substring(@.bitmap,1,1) & 2 when 2 then @.c2 else
> "Entity ID" end
> ,"City ID" = case substring(@.bitmap,1,1) & 4 when 4 then @.c3 else "City
> ID" end
> ,"State ID" = case substring(@.bitmap,1,1) & 8 when 8 then @.c4 else
> "State ID" end
> ,"Postal Code ID" = case substring(@.bitmap,1,1) & 16 when 16 then @.c5
> else "Postal Code ID" end
> ,"Zip Last 4" = case substring(@.bitmap,1,1) & 32 when 32 then @.c6 else
> "Zip Last 4" end
> ,"Country ID" = case substring(@.bitmap,1,1) & 64 when 64 then @.c7 else
> "Country ID" end
> ,"Primary Address" = case substring(@.bitmap,1,1) & 128 when 128 then @.c8
> else "Primary Address" end
> ,"Address Type ID" = case substring(@.bitmap,2,1) & 1 when 1 then @.c9
> else "Address Type ID" end
> ,"Address Lines" = case substring(@.bitmap,2,1) & 2 when 2 then @.c10 else
> "Address Lines" end
> where "Address ID" = @.pkc1
> if @.@.rowcount = 0
> if @.@.microsoftversion>0x07320000
> exec sp_MSreplraiserror 20598
> end
> else
> begin
> update "Entity Address" set
> "Entity ID" = case substring(@.bitmap,1,1) & 2 when 2 then @.c2 else
> "Entity ID" end
> ,"City ID" = case substring(@.bitmap,1,1) & 4 when 4 then @.c3 else "City
> ID" end
> ,"State ID" = case substring(@.bitmap,1,1) & 8 when 8 then @.c4 else
> "State ID" end
> ,"Postal Code ID" = case substring(@.bitmap,1,1) & 16 when 16 then @.c5
> else "Postal Code ID" end
> ,"Zip Last 4" = case substring(@.bitmap,1,1) & 32 when 32 then @.c6 else
> "Zip Last 4" end
> ,"Country ID" = case substring(@.bitmap,1,1) & 64 when 64 then @.c7 else
> "Country ID" end
> ,"Primary Address" = case substring(@.bitmap,1,1) & 128 when 128 then @.c8
> else "Primary Address" end
> ,"Address Type ID" = case substring(@.bitmap,2,1) & 1 when 1 then @.c9
> else "Address Type ID" end
> ,"Address Lines" = case substring(@.bitmap,2,1) & 2 when 2 then @.c10 else
> "Address Lines" end
> where "Address ID" = @.pkc1
> if @.@.rowcount = 0
> if @.@.microsoftversion>0x07320000
> exec sp_MSreplraiserror 20598
> end
> however, if I look at TestDB in my subscriber, I can find
> [sp_MSupd_Entity Address] but not sp_MSupd_Entity Address, note one is
> with brackets, the other not.
> why 2 sp's anyway (with & without brackets)?
> how can I control the creation of this procedure? I looked at the
> properties tab of this publictaion at the Publisher, under Article
> Entity Address, and make sure all the options are selected (e.g. Replace
> INSERT commands with this stored procedure, etc).
> The only option I could not access is the one at the very bottom that
> causes replication to use the columns name. It was just enabled.
> Any ideas?
> btw: your book about Transactional & Snapshot replication looks good, I
> haven't found a good book on replication yet! Is it out already?
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
>

"Select *" in Replication Tables

Hi,
I used "select * from replicate_table_name" in my stored procedures and my
application.Now i want to replicate that tables.
Will it affect my application and Replication.
Please Advice me.
Regds
Soura
It has zero effect on replication, since replication is not going to look at
your code.
It will have no effect on your application as long as you are using
transactional replication. If you are using any other method of
replication, an additional column will be added to your tables which can
then be picked up by that select * and returned to your application which
might not be expecting it, thereby causing it to blow up.
It is VERY STRONGLY recommended that you do NOT use select * in any code
that you ever write in an application. It is bad programming practice and
can lead to some very nasty errors after your application is deployed.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:56C4D4EC-2E19-4648-81E0-621E8EF821E7@.microsoft.com...
> Hi,
> I used "select * from replicate_table_name" in my stored procedures and my
> application.Now i want to replicate that tables.
> Will it affect my application and Replication.
>
> Please Advice me.
> Regds
> Soura
>
>
>
|||It depends . The table schema is modified if you have updatable
subscribers or merge replication - an extra column is added. However, in the
case of merge if you already have a guid column with the rowguid attribute
there won't be another column added.
So, in those cases which cause a schema modification, will the extra column
cause an issue? This depends on your code. In TSQL, if you use:
Insert into x
select * from Y
and Y has an extra column added, it'll fail.
If your code simply does
select * from Y
then it depends on how the recordset/dataset is used in the client app.
There may be some code that iterates through the columns collection which'll
fail if it encounters a new column. Actually this is unlikely as most
columns are referenced directly by name, and the new column will simply
exist but never be referred to.
Anyway - hopefully this gives you some ideas of what to look for to see if
these things will be an issue in your code...
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

"On demand" push subscription

Hi everyone,

Here is my problem: I need to implement an "on demand" push subscription. I am currently using a transactional replication with subscription agents running continiously. The connection between the publisher and the subscribers is pretty flaky, plus having the agents run continiously utilizes an ennormous amount of network bandwidth. At the same time the data need to be pushed to the subscribers as soon as they get into the publisher, so scheduling would not work either.

The only choice I have is to implement a solution where the distribution agents would be generally disconnected (i.e. disabled) from the subscribers, and would be enabled only when a data change is processd by the publisher.

Where do I start? Should I use triggers, DTS, or anything else? If yes, how? I am open to any suggestions.

Thank you very, very, very much!For the consistency between database why don't you use LOG SHIPPING which works in similar fashion of replication.|||Thank you for your input, Satya! I've investigated log shipping as a possible alternative, but found that it requires to be scheduled at a cerain time. I need a solution that allows an immediate update of the records.

Thank you, any additional ideas are greatly appreciated!

Originally posted by Satya
For the consistency between database why don't you use LOG SHIPPING which works in similar fashion of replication.|||True, its debatable topic between replication and log shipping.

What I mean is if you log shipping and enable Log transfer every 15 minutes between Primary and secondary server which will have easy effect of backup of live database. LS proved and saved a lot of time of mine than replication.

If you're insist to use immediate updations then better to opt for replication and make sure to suffice all the terms before using.

Refer books online for more information on REPLICATION topic.|||To Satya:

Woohoo! I resolved the problem! I have implemented the "on demand" programmatically using C#. The user decides when to actually replicate by simply pressing a button. The command initializes, runs, and terminates all of the necessary distribution agents. This way the agents are deactivated most of the time, and are activated only when the user actually puts in a batch of records and gives a command to replicate. Since the records are put in only once or twice daily, but need to be available everywhere immediately, it is a perfect solution for us. Of course, if the data were put in more often, it would make more sense to leave the agents run continuously or to use a frequently scheduled log shipping.

P.S. I used a Microsoft Distribution Control 8.0 (SQLDISTXLib)

"Not enough server storage is available to process this command"

Hi,
We have several customers using replication on similar databases - all with the same schema, published using essentially the same script. One of them has been getting the "Not enough server storage" message when they try to access any network shares on th
e server with the published database on it. This starts happening between 24-36 hours after they first run the snapshot agent.
The application log contains an entry saying "The process could not create file \\[SERVER]\REPLDATA\unc",
and the system log has one saying "The server was unable to allocate from the system paged pool because the pool was empty".
When they turn off the replication everything is fine.
I suggested increasing the IRPStackSize value in the registry, as this was mentioned in the closest article I could find on MSDN/KB (something about Norton AntiVirus), but this didn't make any difference.
This is SQL Server 2000 running on Windows 2000 Server, all with up-to-date service packs.
Any ideas or suggestions would be appreciated.
Mark
from your earlier post i understand that the snapshot creation part gives
out this message.
If the error occurs while the snapshot is being generated, check the
following"
1. Check if the sql server service account has appropriate NTFS and share
level permissions to write to the repldata directory.
2. Check if there is enough storage space on the disk for creating files
in repldata directory.
3. Check if you can run xp_cmdshell "dir
\\distributorname\c$\mssql\repldata"
and dir \\distributor\c$\mssql\repldata from command prompt.
If the error occurs after the snapshot has been completely generated, Refer
-
* KB : 285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Pls do let me know of the SQL server version (build number). and the event
id's of the event log messages.
Does this message stop replication? are the subscribers and publisher in
sync? - Just to confirm if this message is obstructing replication from
being in sync.

"max text repl size" safety

I just increased the max size of text replication to 524288 bytes with below
Sql statements. The system allows me to do that but I'm wondering if there
is any issue/drawback that I should know about pumping the max size up by so
much. Thank you in advance for your advice.
EXEC sp_configure 'max text repl size', '524288'
go
RECONFIGURE WITH OVERRIDE
go
Basically it means that SQL can replicate data where a row contains more
than 524288 bytes. This will cause performance degradation on your system as
rows this size are going through.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Zeng" <Zeng5000@.hotmail.com> wrote in message
news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
>I just increased the max size of text replication to 524288 bytes with
>below
> Sql statements. The system allows me to do that but I'm wondering if
> there
> is any issue/drawback that I should know about pumping the max size up by
> so
> much. Thank you in advance for your advice.
> EXEC sp_configure 'max text repl size', '524288'
> go
> RECONFIGURE WITH OVERRIDE
> go
>
|||If you have a separate distributor server where does this setting need to be
issued. At the distributor or the publisher?
If the system is moving large files (2- 10 MB) what kind of impact will it
have? What impact will it have on both servers?
Thanks
"Hilary Cotter" wrote:

> Basically it means that SQL can replicate data where a row contains more
> than 524288 bytes. This will cause performance degradation on your system as
> rows this size are going through.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Zeng" <Zeng5000@.hotmail.com> wrote in message
> news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
>
>
|||I believe its on the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:2DB417F1-5573-48EA-B1AC-C10B8760D75E@.microsoft.com...[vbcol=seagreen]
> If you have a separate distributor server where does this setting need to
> be
> issued. At the distributor or the publisher?
> If the system is moving large files (2- 10 MB) what kind of impact will it
> have? What impact will it have on both servers?
> Thanks
> "Hilary Cotter" wrote:

"max text repl size" safety

I just increased the max size of text replication to 524288 bytes with below
Sql statements. The system allows me to do that but I'm wondering if there
is any issue/drawback that I should know about pumping the max size up by so
much. Thank you in advance for your advice.
EXEC sp_configure 'max text repl size', '524288'
go
RECONFIGURE WITH OVERRIDE
goBasically it means that SQL can replicate data where a row contains more
than 524288 bytes. This will cause performance degradation on your system as
rows this size are going through.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Zeng" <Zeng5000@.hotmail.com> wrote in message
news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
>I just increased the max size of text replication to 524288 bytes with
>below
> Sql statements. The system allows me to do that but I'm wondering if
> there
> is any issue/drawback that I should know about pumping the max size up by
> so
> much. Thank you in advance for your advice.
> EXEC sp_configure 'max text repl size', '524288'
> go
> RECONFIGURE WITH OVERRIDE
> go
>|||If you have a separate distributor server where does this setting need to be
issued. At the distributor or the publisher?
If the system is moving large files (2- 10 MB) what kind of impact will it
have? What impact will it have on both servers?
Thanks
"Hilary Cotter" wrote:

> Basically it means that SQL can replicate data where a row contains more
> than 524288 bytes. This will cause performance degradation on your system
as
> rows this size are going through.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Zeng" <Zeng5000@.hotmail.com> wrote in message
> news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
>
>|||I believe its on the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:2DB417F1-5573-48EA-B1AC-C10B8760D75E@.microsoft.com...[vbcol=seagreen]
> If you have a separate distributor server where does this setting need to
> be
> issued. At the distributor or the publisher?
> If the system is moving large files (2- 10 MB) what kind of impact will it
> have? What impact will it have on both servers?
> Thanks
> "Hilary Cotter" wrote:
>

"max text repl size" safety

I just increased the max size of text replication to 524288 bytes with below
Sql statements. The system allows me to do that but I'm wondering if there
is any issue/drawback that I should know about pumping the max size up by so
much. Thank you in advance for your advice.
EXEC sp_configure 'max text repl size', '524288'
go
RECONFIGURE WITH OVERRIDE
go
Basically it means that SQL can replicate data where a row contains more
than 524288 bytes. This will cause performance degradation on your system as
rows this size are going through.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Zeng" <Zeng5000@.hotmail.com> wrote in message
news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
>I just increased the max size of text replication to 524288 bytes with
>below
> Sql statements. The system allows me to do that but I'm wondering if
> there
> is any issue/drawback that I should know about pumping the max size up by
> so
> much. Thank you in advance for your advice.
> EXEC sp_configure 'max text repl size', '524288'
> go
> RECONFIGURE WITH OVERRIDE
> go
>
|||If you have a separate distributor server where does this setting need to be
issued. At the distributor or the publisher?
If the system is moving large files (2- 10 MB) what kind of impact will it
have? What impact will it have on both servers?
Thanks
"Hilary Cotter" wrote:

> Basically it means that SQL can replicate data where a row contains more
> than 524288 bytes. This will cause performance degradation on your system as
> rows this size are going through.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Zeng" <Zeng5000@.hotmail.com> wrote in message
> news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
>
>
|||I believe its on the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:2DB417F1-5573-48EA-B1AC-C10B8760D75E@.microsoft.com...[vbcol=seagreen]
> If you have a separate distributor server where does this setting need to
> be
> issued. At the distributor or the publisher?
> If the system is moving large files (2- 10 MB) what kind of impact will it
> have? What impact will it have on both servers?
> Thanks
> "Hilary Cotter" wrote:

"max text repl size" safety

I just increased the max size of text replication to 524288 bytes with below
Sql statements. The system allows me to do that but I'm wondering if there
is any issue/drawback that I should know about pumping the max size up by so
much. Thank you in advance for your advice.
EXEC sp_configure 'max text repl size', '524288'
go
RECONFIGURE WITH OVERRIDE
goBasically it means that SQL can replicate data where a row contains more
than 524288 bytes. This will cause performance degradation on your system as
rows this size are going through.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Zeng" <Zeng5000@.hotmail.com> wrote in message
news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
>I just increased the max size of text replication to 524288 bytes with
>below
> Sql statements. The system allows me to do that but I'm wondering if
> there
> is any issue/drawback that I should know about pumping the max size up by
> so
> much. Thank you in advance for your advice.
> EXEC sp_configure 'max text repl size', '524288'
> go
> RECONFIGURE WITH OVERRIDE
> go
>|||If you have a separate distributor server where does this setting need to be
issued. At the distributor or the publisher?
If the system is moving large files (2- 10 MB) what kind of impact will it
have? What impact will it have on both servers?
Thanks
"Hilary Cotter" wrote:
> Basically it means that SQL can replicate data where a row contains more
> than 524288 bytes. This will cause performance degradation on your system as
> rows this size are going through.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Zeng" <Zeng5000@.hotmail.com> wrote in message
> news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
> >I just increased the max size of text replication to 524288 bytes with
> >below
> > Sql statements. The system allows me to do that but I'm wondering if
> > there
> > is any issue/drawback that I should know about pumping the max size up by
> > so
> > much. Thank you in advance for your advice.
> >
> > EXEC sp_configure 'max text repl size', '524288'
> > go
> > RECONFIGURE WITH OVERRIDE
> > go
> >
> >
>
>|||I believe its on the publisher.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:2DB417F1-5573-48EA-B1AC-C10B8760D75E@.microsoft.com...
> If you have a separate distributor server where does this setting need to
> be
> issued. At the distributor or the publisher?
> If the system is moving large files (2- 10 MB) what kind of impact will it
> have? What impact will it have on both servers?
> Thanks
> "Hilary Cotter" wrote:
>> Basically it means that SQL can replicate data where a row contains more
>> than 524288 bytes. This will cause performance degradation on your system
>> as
>> rows this size are going through.
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>> "Zeng" <Zeng5000@.hotmail.com> wrote in message
>> news:e3DD325%23FHA.3992@.TK2MSFTNGP15.phx.gbl...
>> >I just increased the max size of text replication to 524288 bytes with
>> >below
>> > Sql statements. The system allows me to do that but I'm wondering if
>> > there
>> > is any issue/drawback that I should know about pumping the max size up
>> > by
>> > so
>> > much. Thank you in advance for your advice.
>> >
>> > EXEC sp_configure 'max text repl size', '524288'
>> > go
>> > RECONFIGURE WITH OVERRIDE
>> > go
>> >
>> >
>>

"Mark for re-initialization" hangs

Hi, I have a problem with a SQL 2000 transactional replication.
It is a replication with subscriptions on several world wide located
servers.
A WAN connection has been disabled for some time and as result one
subscription has been marked inactive.
Message: "The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be dropped and
recreated."
In the past this problem could been solved by re-initializing the
subscription but in this case
the Enterprise Manager hangs, when I tried to mark the subscription
for re-initialization.
Both SQL servers (publisher and subscriber) have been re-started but
the problem remained.
There are no sessions on the subscriber database which could block the
initialization.
The subscription can not be deleted.
What more can I do?
can you issue this command in qa on the publisher in the publication
database?
sp_reinitsubscription
'publicationname','all','SubscriberName','subscrip tionDatabase'
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"hmb1963" <hmb1963@.gmx-topmail.de> wrote in message
news:1185358724.772454.145180@.k79g2000hse.googlegr oups.com...
> Hi, I have a problem with a SQL 2000 transactional replication.
> It is a replication with subscriptions on several world wide located
> servers.
> A WAN connection has been disabled for some time and as result one
> subscription has been marked inactive.
> Message: "The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be dropped and
> recreated."
> In the past this problem could been solved by re-initializing the
> subscription but in this case
> the Enterprise Manager hangs, when I tried to mark the subscription
> for re-initialization.
> Both SQL servers (publisher and subscriber) have been re-started but
> the problem remained.
> There are no sessions on the subscriber database which could block the
> initialization.
> The subscription can not be deleted.
> What more can I do?
>
|||I tried out the stored procedure but the result was a hanging qa
without any status or error message.
|||use sp_who2 to identify locks/deadlocks caused by the replication processes
and selectively kill them,
Then try again.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"hmb1963" <hmb1963@.gmx-topmail.de> wrote in message
news:1185443077.713064.265760@.r34g2000hsd.googlegr oups.com...
>I tried out the stored procedure but the result was a hanging qa
> without any status or error message.
>
|||Success!
I have killed again all sessions both on the publisher and subscriber
databases and
then the stored procedure sp_reinitsubscription worked.
Many thanks for your support.
Martin

"Know Issue" not in KB. COLID continues to rise.

I use transactional replication on several very "wide" table. One has
254 columns. After finding that was my limit for replication to work I
removed an unused columns and added a new needed column. Since the
COLID in the SYSCOLUMNS did not reset replication failed. I'm down to
renaming columns now.
This was in SQL Server 2000 and is still present in 2005. A call to
Microsoft turned up "Known Issue" statement.
Has anyone found another way around this without creating a new table
with the needed columns and moving the current data in? Keep in mind I
inherited this database and did not create a table this wide.
Thanks.
Mike.Mike,
apart from your suggestion, the only other workaround I am aware of is to
partition the table and to replicate the 2 tables separately, which is
probably more work than your method.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

"Know Issue" not in KB. COLID continues to rise.

I use transactional replication on several very "wide" table. One has
254 columns. After finding that was my limit for replication to work I
removed an unused columns and added a new needed column. Since the
COLID in the SYSCOLUMNS did not reset replication failed. I'm down to
renaming columns now.
This was in SQL Server 2000 and is still present in 2005. A call to
Microsoft turned up "Known Issue" statement.
Has anyone found another way around this without creating a new table
with the needed columns and moving the current data in? Keep in mind I
inherited this database and did not create a table this wide.
Thanks.
Mike.Mike,
apart from your suggestion, the only other workaround I am aware of is to
partition the table and to replicate the 2 tables separately, which is
probably more work than your method.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

"Invalid distribution command" in transaction replication

HI
I had a replication working nicely for long time. SQL 2k, SP3.
One day it stoped working with the error "Invalid distribution command." and
last action is: insert into "ponim" ("tz_pone.
Transaction sequence number and command ID of last execution batch are
0x0000829800000ABB000100000000 and 1.
I think maybe that day I added a new column using sp_repladdcolumn.
I want to say that the same script I run for that replication I ran for
another 3 similar replication and they all still work prefectly.
Any Ideas what I can do?
Please take in consider that I have lots of data in the publication that
couldn't be send to the subscriber becouse of the above error.
Thanks
use sp_browsereplcmds to identiy this command. Then apply this command
on the subcriber.
Then update msreplication_subscripions with the xaxct_seqno for this
command. This will cause it to skip this command.

"Invalid distribution command" in transaction replication

HI
I had a replication working nicely for long time. SQL 2k, SP3.
One day it stoped working with the error "Invalid distribution command." and
last action is: insert into "ponim" ("tz_pone.
Transaction sequence number and command ID of last execution batch are
0x0000829800000ABB000100000000 and 1.
I think maybe that day I added a new column using sp_repladdcolumn.
I want to say that the same script I run for that replication I ran for
another 3 similar replication and they all still work prefectly.
Any Ideas what I can do?
Please take in consider that I have lots of data in the publication that
couldn't be send to the subscriber becouse of the above error.
Thanksuse sp_browsereplcmds to identiy this command. Then apply this command
on the subcriber.
Then update msreplication_subscripions with the xaxct_seqno for this
command. This will cause it to skip this command.

"Invalid distribution command" in transaction replication

HI
I had a replication working nicely for long time. SQL 2k, SP3.
One day it stoped working with the error "Invalid distribution
command." and
last action is: insert into "ponim" ("tz_pone.
Transaction sequence number and command ID of last execution batch are
0x0000829800000ABB000100000000 and 1.
I think maybe that day I added a new column using sp_repladdcolumn.
I want to say that the same script I run for that replication I ran for
another 3 similar replication and they all still work prefectly.
Any Ideas what I can do?
Please take in consider that I have lots of data in the publication
that
couldn't be send to the subscriber becouse of the above error.
Thanks
Please enable logging as per this article:
http://support.microsoft.com/?id=312292 to get more details about the
failing command.
sp_browsereplcmds could also be used to find these details.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

"Invalid distribution command" in transaction replication

HI
I had a replication working nicely for long time. SQL 2k, SP3.
One day it stoped working with the error "Invalid distribution command." and
last action is: insert into "ponim" ("tz_pone.
Transaction sequence number and command ID of last execution batch are
0x0000829800000ABB000100000000 and 1.
I think maybe that day I added a new column using sp_repladdcolumn.
I want to say that the same script I run for that replication I ran for
another 3 similar replication and they all still work prefectly.
Any Ideas what I can do?
Please take in consider that I have lots of data in the publication that
couldn't be send to the subscriber becouse of the above error.
Thanks
use sp_browsereplcmds to identiy this command. Then apply this command
on the subcriber.
Then update msreplication_subscripions with the xaxct_seqno for this
command. This will cause it to skip this command.

"Invalid distribution command" in transaction replication

HI
I had a replication working nicely for long time. SQL 2k, SP3.
One day it stoped working with the error "Invalid distribution command." and
last action is: insert into "ponim" ("tz_pone.
Transaction sequence number and command ID of last execution batch are
0x0000829800000ABB000100000000 and 1.
I think maybe that day I added a new column using sp_repladdcolumn.
I want to say that the same script I run for that replication I ran for
another 3 similar replication and they all still work prefectly.
Any Ideas what I can do?
Please take in consider that I have lots of data in the publication that
couldn't be send to the subscriber becouse of the above error.
Thanksuse sp_browsereplcmds to identiy this command. Then apply this command
on the subcriber.
Then update msreplication_subscripions with the xaxct_seqno for this
command. This will cause it to skip this command.

"Hidden" Replication Stored Procedures?

In looking thru the code for the replication related stored procedure
sp_addarticle, I noticed that there were 2 stored procedures called from
sp_addarticle that I can't seem to find anywhere on my SQL Server:
sys.sp_MSrepl_getpublisherinfo & sys.sp_MSrepl_addarticle. These are stored
procedures that appear to be undocumented and I have read comments on
Microsoft sites stating things like: “Undocumented stored procedures are only
for the use of internal replication components and should not be used to
administer replication.”. I just want to know more about these stored procs
(and others like these) as far as where they live, what they do, how
sp_addarticle calls these Stored Procs without the SP blowing up....as I
have tried to call sys.sp_MSrepl_getpublisherinfo in a 10 line script I made
and all I got back was that the sys.sp_MSrepl_getpublisherinfo couldn't be
found no matter what DB I tried to execute against. I don't see anything
helpful about these SPs when I Google (and I am a Google master) or anywhere
else. If anyone has anything relevant & helpful, I would appreciate the info.
Thanks.
Chris Jones
Application Development Consultant
they are in mssqlsystemresource.mdf. Open it in a text editor to read what
this proc does.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:420DD987-9E55-46AB-8445-82FD01740996@.microsoft.com...
> In looking thru the code for the replication related stored procedure
> sp_addarticle, I noticed that there were 2 stored procedures called from
> sp_addarticle that I can't seem to find anywhere on my SQL Server:
> sys.sp_MSrepl_getpublisherinfo & sys.sp_MSrepl_addarticle. These are
> stored
> procedures that appear to be undocumented and I have read comments on
> Microsoft sites stating things like: "Undocumented stored procedures are
> only
> for the use of internal replication components and should not be used to
> administer replication.". I just want to know more about these stored
> procs
> (and others like these) as far as where they live, what they do, how
> sp_addarticle calls these Stored Procs without the SP blowing up....as I
> have tried to call sys.sp_MSrepl_getpublisherinfo in a 10 line script I
> made
> and all I got back was that the sys.sp_MSrepl_getpublisherinfo couldn't be
> found no matter what DB I tried to execute against. I don't see anything
> helpful about these SPs when I Google (and I am a Google master) or
> anywhere
> else. If anyone has anything relevant & helpful, I would appreciate the
> info.
> --
> Thanks.
> Chris Jones
> Application Development Consultant
|||Great, that was exactly what I was looking for and when opening the
aforementioned MDF file in Notepad and doing a quick search, I found the SPs
I had mentioned in my earlier post. Thanks for the good info!
I have one follow up question based on your answer:
Is there a way to have the Resource Database appear in the list of Databases
in SQL Server Management Studio for easy browsing of it's contents, or is the
only browse option to open the MDF file with a text editor such as notepad?
Thanks.
Chris Jones
Application Development Consultant
"Hilary Cotter" wrote:

> they are in mssqlsystemresource.mdf. Open it in a text editor to read what
> this proc does.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:420DD987-9E55-46AB-8445-82FD01740996@.microsoft.com...
>
>
|||Just make a copy of the database files, attach it with a different name
and... 'voila'!
:-)
Chris wrote:[vbcol=seagreen]
> Great, that was exactly what I was looking for and when opening the
> aforementioned MDF file in Notepad and doing a quick search, I found the SPs
> I had mentioned in my earlier post. Thanks for the good info!
> I have one follow up question based on your answer:
> Is there a way to have the Resource Database appear in the list of Databases
> in SQL Server Management Studio for easy browsing of it's contents, or is the
> only browse option to open the MDF file with a text editor such as notepad?
> --
> Thanks.
> Chris Jones
> Application Development Consultant
>
> "Hilary Cotter" wrote:
|||Yip...you are absolutely correct...I just discovered that and was coming
back here to post the instructions. Here's what I found...
First, giving credit where credit is due, I found the following info I am
about to post at the following location:
http://www.aspfaq.com/sql2005/show.asp?id=28
Since the engine has hooks that hide the mssqlsystemresource database from
users, you don't have direct access to it through the GUI.
However, there is a way around this:
1.)Determine where the system databse files live, and keep this path handy:
USE master
GO
SELECT REPLACE(filename, 'master.mdf', '')
FROM sys.sysfiles
WHERE fileid = 1
2.)Stop the SQL Server service;
3.)Copy the files mssqlsystemresource.*df -> resource_copy.*df.
NOTE: do *not* rename or remove the mssqlsystemresource files!
4.)Start the SQL Server service;
5.)Run the following code in a new query window:
EXEC sp_attach_db
'Resource_Copy',
'<path from above>resource_copy.mdf',
'<path from above>resource_copy.ldf'
6.)Now, the system will no longer identify this database as a "special"
database
7.)You can easily scan through the names of system objects that might
otherwise be unknown (and browse any code associated with these objects) from
a GUI (like SQL Server Management Studio).
Thanks.
Chris Jones
Application Development Consultant
"zerg2k@.yahoo.com" wrote:

> Just make a copy of the database files, attach it with a different name
> and... 'voila'!
> :-)
> Chris wrote:
>
|||i just read ur post and i liked it beacuse i didn't even knew that SQL Server
uses such databases other then the known ones. but i didn't find the
mssqlsystemresource.mdf file can i please specify the address.
"Hilary Cotter" wrote:

> they are in mssqlsystemresource.mdf. Open it in a text editor to read what
> this proc does.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:420DD987-9E55-46AB-8445-82FD01740996@.microsoft.com...
>
>

"General network error. Check your network documentation."

I try to make a replication on my SQL Server2000 SP3 on Windows2000. I want to replicate 8 tables from Server1 to Server2. I found that 6 tables is work fine, however only 2 table that have an error that show below. How can I correct it?

The process could not deliver the snapshot to the Subscriber.

The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----------------------------------
The process could not bulk copy into table '"dbo"."Table1"'.
(Source: Server2 (Agent); Error number: 20037)
----------------------------------
General network error. Check your network documentation.
(Source: Server2 (Data source); Error number: 11)
----------------------------------Ok for the latest time I post my problem is only happen on Table1 but on Table2 is has something difference.

On Table1:
The process could not deliver the snapshot to the Subscriber.

The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----------------------------------
The process could not bulk copy into table '"dbo"."Table1"'.
(Source: Server2 (Agent); Error number: 20037)
----------------------------------
General network error. Check your network documentation.
(Source: Server2 (Data source); Error number: 11)
----------------------------------

On Table2:
The process could not query row metadata at the 'Subscriber'.

The process could not query row metadata at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200996)
----------------------------------
Genetal network error. Check your network documentation.
(Source: Server2 (Data source); Error number: 11)
----------------------------------
The process was successfully stopped.
(Source: Merge Replication Provider (Agent); Error number: -2147199469)

"DB" was not found in TransPublication collection

I had to restore one of the dbs which has replication setup with another SQL,
my problem is that after restoring db I have lot of red "X"s on Publisher
server, and I cannot get ride of those, what am trying to do is to clean this
up and recreat replication but get following errors (one in the subject)
-SQL could not retrieve info about publication
I was even thinking about dropping this db and create again then restore but
get another error msg: cannot delete it's being use for replication.
under replication I see <no items> all errors are in Replication Monitor and
db itself has "hand" indicating it's being use for replication...
need some help?
Thanks
Thanks for responding, but it does not work... I did restore old db and then
was able to clean this up... thanks again
RW
"Paul Ibison" wrote:

> If this database is no longer involved in replication in
> any way, try running sp_removedbreplication.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

"Could not continue scan with NOLOCK due to data" error during Replication Synchronization

I am receiving this message "Agent message code 601. Could not
continue scan with NOLOCK due to data" during the initial
synchronization after setting up a subscriber.
It is a straightforward tarnsactional replication of maybe twenty
tables.
I have never seen that message in the context of replication.
I think the 601 error looks to be slightly misleading as the previous
message in the log looks to indcate a successful snapshot
synchronization:
Delivered snapshot from the 'unc\serverX\20070208105750\' sub-folder
in 519625 milliseconds.
I have tried setting up the subscriber and publisher mulitple times
from scratch but always run into this message. Also all of the
replicated tables have multiple indexes and this is on a SQL Server
2005 SP1 Mirrored database. I have ran checkdb on database with no
problems found. This is halting the database from being replicated -
anyone know a way around this?
On Feb 8, 5:14 pm, "Calculated" <sarahjco...@.gmail.com> wrote:
> I am receiving this message "Agent message code 601.Could notcontinue scan with NOLOCK due to data"duringthe initialsynchronizationafter setting up a subscriber.
> It is a straightforward tarnsactionalreplicationof maybe twenty
> tables.
> I have never seen that message in the context ofreplication.
> I think the 601errorlooks to be slightly misleading as the previous
> message in the log looks to indcate a successful snapshotsynchronization:
> Delivered snapshot from the 'unc\serverX\20070208105750\' sub-folder
> in 519625 milliseconds.
> I have tried setting up the subscriber and publisher mulitple times
> from scratch but always run into this message. Also all of the
> replicated tables have multiple indexes and this is on a SQL Server
> 2005 SP1 Mirrored database. I have ran checkdb on database with no
> problems found. This is halting the database from being replicated -
> anyone know a way around this?
Resolved this - if anyone else has this problem try adding a table at
a time to the publication article and re-initializing the subscription
until you identify the problem table. Then either filter the table to
break down into smaller chunks (largest table in db was causing
problem in my case) or play around with the copy clustered index and
copy nonclustered index options on the specific table.