sql server replication: The process could not bulk copy into table '"table

You're in the

sql server replication

group:

The process could not bulk copy into table '"table_name"'

8/31/2007 12:00:00 AM

sql server replication:
I've recently come accross this replication issue i've not had before,
the replication is running in the following environment....

Machine A - Server 2000, SQL Server 2000 SP4, The Publisher
Machine B - Server 2003, SQL Server 2005 SP2, The Subscriber, Pull
Subscription

The snapshot is processed correctly on Machine A, all seems to be
transfered properly. The subscription then runs and halts at a table
with the "The process could not bulk copy into table '"table_name"' "
error message.

The replication should simply transfer all tables from Machine A to
Machine B, it is set to keep the existing table structure. No keys are
setup on Machine B.

This is the part that I don't understand! The snapshot created the
table structure but the only work around I've found for this issue so
far is to manually drop the table troublesome table from Machine B,
copy the schema script generated by the snapshot agent on Machine A
and execute it on Machine B, if i then run the subscriber it trundles
along fine until it hits the same problem with another table?!

I've checked the MDAC versions, Machine A is MDAC 2.8 sp1, Machine B
is MDAC 2.8 sp2 - i'm under the impression that there isn't an sp2
available for server 2000!

Any suggestions are more than welcome!

Re: The process could not bulk copy into table '"table_name"'

Hilary Cotter
9/2/2007 7:19:22 AM

Are the database collations the same on both sides?

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

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
[quoted text, click to view]

Re: The process could not bulk copy into table '"table_name"'

9/3/2007 12:00:00 AM

[quoted text, click to view]

Yes the collations are the same, i've tried the 2005 server in 2000
compat mode too to no avail.

[quoted text, click to view]

The machine running SP2 is actually SQL Server 2005 so putting 2000
SP4 won't make any difference will it? I have some logs but am unable
to get access to them at this moment in time. I can confirm that there
are errors with BCP, i ran the BCP command manually which reported an
error with the keys. I dropped the table troublesome table and
reinitialized - still the same problem..... now here is the
interesting bit.

I dropped the table again, copied the content of the schema file from
the snapshot, manually ran that on the 2005 box (subscriber) this
created the table with no issues. I then ran the subscription again
and everything worked so where is it going wrong during the
reinitialization? Is it an issue of replicating from 2000 to 2005?

Re: The process could not bulk copy into table '"table_name"'

9/3/2007 12:00:00 AM

[quoted text, click to view]

Nope, It's just transactional. I appear to have it working now, i've
had to drop all of the tables on the subscriber and then reinitialize
which has allowed it to start working.

The mystry is that if I now modify one table on the publisher (2000)
and reinitialise, the table is created on the 2005 instance but
nothing can be bulk copied into it due to key errors. If i drop the
table on the subscriber and manually execute the schema generated for
the table from the snapshot the table is created and will populate
fine?

Are there known issues with reinitialization between 2000 and 2005?

RE: The process could not bulk copy into table '"table_name"'

Paul Ibison
9/3/2007 2:20:00 AM

If at all possible, see if adding sp4 onto the subscriber fixes the issue. If
not, then do some logging to see if we can get some more specific info:
http://support.microsoft.com/?id=312292
HTH,
Paul Ibison

Re: The process could not bulk copy into table '"table_name"'

Paul Ibison
9/3/2007 7:04:01 AM

Apologies - missed the SQL 2005 bit. This also makes me wonder if this is a
merge publication. If it is, then this setup isn't supported and it might
account for the error you're seeing....
Cheers,
Paul Ibison

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server replication group.

View Other Months
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007

home · blog · groups

Questions? Comments? Contact the dn