SQLServerCentral.com / Replication / SQL Server 7,2000 / The process could not bulk copy into table / Latest PostsInstantForum.NET v99.99.99SQLServerCentral.comhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 09 Dec 2016 20:54:15 GMT20RE: The process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspxthank you - the developer add columns in the publishing database to the end of the tablebut put them in the middle in the subscriber dbSat, 26 May 2012 09:39:46 GMTdavidsatzRE: The process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspxThe process could not bulk copy into table '"xxxx"'i m also facing this problem, kindly guide me which agent profile is better and how can i do?i set Transactional replication..Thu, 18 Dec 2008 03:35:45 GMTmrizabidRE: The process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspx<P>Are you merge replicating a table that is being bulk copied into, such as a DTS for example?</P><P>If so the following link may help..</P><P><A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;275680">http://support.microsoft.com/default.aspx?scid=kb;en-us;275680</A></P>Thu, 06 Jan 2005 13:04:00 GMTamichalsRE: The process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspx<P>This error is a fairly common error in replication and can be caused by a no. of issues. Usually, it is because the schema in the publisher does not match that of the subscriber.</P><P>To determine the exact cause, you need to increase the verbose history level of the output and create an output file when the snapshot or distribution agent runs.</P><P>Analysing this error file will then give more of an indication as to the exact cuase of the problem.</P>Wed, 05 Jan 2005 08:21:00 GMTPaul WilliamsRE: The process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspx<P>How large is your DB. What kind of connection lies between the two servers ?</P><P>With larger tables over slower connections very often the reason for this message is a timeout. You can avoid this error by changing the snapshot agent profile settings.</P><P>M</P>Tue, 04 Jan 2005 08:21:00 GMTMarkusBRE: The process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspxCheck to see that the Subscriber has enough disk space to perform the snapshot.Mon, 03 Jan 2005 16:36:00 GMTTriggerMeRE: The process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspx<P>I'm using snapshot replications and It happens when the transactions are been replicated to the suscriber</P><P> </P><P>Thank </P>Thu, 30 Dec 2004 18:54:00 GMTer sqlRE: The process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspxWhat Replication model are you using? Does this error occur when the initial Snapshot takes place or when the transactions are been replicated to the Subscriber?Wed, 29 Dec 2004 15:58:00 GMTTriggerMeThe process could not bulk copy into tablehttp://www.sqlservercentral.com/Forums/Topic152689-7-1.aspx<P>Hi, I'm working with replication and I publishing some databases from server A to server B, in replication monitor from mi server A i saw a message in two publications:</P><P>The process could not bulk copy into table XXXXX.</P><P>How can I fix the error?.</P><P> </P><P>Thanks a lot</P><P>Sincerely</P><P>ER_SQL</P><P> </P><P> </P>Tue, 28 Dec 2004 09:55:00 GMTer sql