SQL Server 2008 Replication. ½,¼,¾ (fraction signs) have stopped replicating properly in a varchar field. They are now getting corrupt. (e.g. 108¾ at publisher and 108ó at subscriber)

  • Re: SQL Server 2008 Replication. ½,¼,¾ (fraction signs) have stopped replicating properly in a varchar field. They are now getting corrupt. (e.g. 108¾ at publisher and 108ó at subscriber)

    Field is defined as....

    Publisher = [V_MYFIELD] [varchar](50) COLLATE SQL_Latin1_General_CP850_BIN NULL

    Subscriber = [V_MYFIELD] [varchar](50) COLLATE SQL_Latin1_General_CP850_BIN NULL

    Data is being written to Publisher correctly.

    Problem has been occurring from 20th July 2013. Time unknown.

    I have an 2 hourly replication check. This picked up 2 tables with this same issue of the ½,¼,¾ signs not being replicated properly at the subscriber end.

    Replication reports no errors. It thinks everything has replicated fine.

    I know I have a separate issue with the distributor database. It has 144 million rows in [distribution].[dbo].[MSrepl_commands] table. I am in the process of working out the steps involved in fixing this via other forum pages. Is this why I might be getting this fraction sign issue? due the size of this database?

    Could anyone help with a list of things I can try to find out the "Root Cause"?

    I will of course to continue to investigate but it is always helpful to find out what people think. I have tried to find this topic area using Google but there is nothing 100% about this issue.

    Thanks,

    Regards,

    Richard.

    NOTE : This is a transaction replication setup.

    Posted 22nd July 2013 10:28hrs BST (GMT +1)

  • I fixed the issue but still do not know the "Root Cause".

    Stopping and ReStarting the Log Reader did NOT fix this.

    However Stopping and ReStarting SQL Services at the Subscriber end DID fix this.

  • Code page problem. Did one of the servers have a patch applied?

    The probability of survival is inversely proportional to the angle of arrival.

  • Both servers were patched a few weeks ago to same level. No issues since patch until last weekend. No other changes done to servers.

    I cannot find the triggering factor for this.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply