September 8, 2004 at 4:37 am
I have replication running from a sp3a publisher to a 818 subscriber - it seems there may be a problem with timestamp columns in their conversion to binary on the subscriber.
I know I have different patch versions - I have controlled environments so cannot blanket patch all servers at once - I've searched for this problem but can't find anything hence the post.
So - did ms03-031 make any changes with transactional replication ?
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
September 13, 2004 at 8:00 am
This was removed by the editor as SPAM
September 28, 2004 at 5:45 am
Hi,
I don't know if microsoft made changes to the transactional replication, but they made heavy changes to the merge replication (they even created some dangerous bugs in one of the stored procedures used for replication). So it's very likely that they also made changes to transactional replication. I would say, that you should never use different releases of ServicePacks in a replication environment.
Hope this helps.
Thorsten
September 28, 2004 at 6:31 am
Thanks - as I say in a strongly controlled environment you can't just roll out changes globally !!
The problem may well have been code - well it's always the database at fault - as it went away before I patched the prod environment. < grin >
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply