Merge error 2147200925 - why does reboot the server machine could solve problem.

Have a look at this article:
http://support.microsoft.com/?id=814916
There is a link to the hotfix details there.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Thanks,
I did take a look at it and have download the hot fix.
But could you explain why restarting the server can solve the problem
temporarily?
Pikctsach
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||A total guess here, but the problem occurs 'in certain circimstances' and
relates to teh production of temporary tables, so the initial population of
the tempdb database might play a part. Restarting the server will recreate
tempdb from the model database, and so reset the starting point - makes
sense locically but I have no way of determining if this is the case.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks!
Have you ever thought of in whichscenarios, SQL Server creates the
temporary table name with a dash sign in the table name? (For Merge
Replication)
Why are temporary tables needed in Merge Replication?
Pikctsach.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!