I had P2P Replication configured between 2 servers. The replication from Server 1 to Server 2 was working fine but the Replication from Server 2 to Server 1 was broken. I removed Replication completely and temporarily configured Log shipping between Server 1 and Server 2 as Server 2 was not yet active. After removing P2P Replication, the updatestats on the db which was part of P2P Replication started failing. On researching I found a KB Article:KB2498796 which states that this issue is fixed in SQL 2008 SP2 cu3. (The version of my server is SQL 2008 SP2). I upgrade my server to SQL 2008 SP3 cu1 and notice that the updatestats continue to fail. On further research, I found that the KB Article for SQL 2008 SP2 cu3 does not list KB2498796 in the bug fix list. I could not find any cu or SP After SP2 cu3 as well which would fix this issue. Only option so far I have identified is clone the table and drop existing table. My table sizes are really huge and also the number of tables along with the number of indexes, constraints, triggers and dependencies on each of the tables It does not seem worth to clone every table to fix this issue. Can anyone suggest any other alternative to fix this issue.??
The error that occurs when I run update stats is :
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.