June 21, 2002 at 9:20 am
Hi again,
We are currently running SQL 7.0 in one of our environments. Replication is on and my question is, we are experiencing many memory leaks on the the server and have researched that perhaps SP3 will 'fix' this problem. The problem is, It would be difficult getting the SP loaded to our remote servers in a timely matter.
Will having disparate SP on the servers cause any problems? Especially with replication?
Christine
Aurora
June 21, 2002 at 9:39 am
I cannot speak directly to your issue, but I am wary of having servers that communicate on different Service Packs. I would plan on mirating them all to the same pack, 3 or 4. Fair number of changes in 3.
Also, MS will not give you support until they are all at SP4, so this is something to consider if you get into a bind.
Steve Jones
June 21, 2002 at 4:09 pm
If you are going to go to any SP, go to 4. You'll just have to upgrade to it again later anyway.
There are lots of fixes in SP3 & SP4 in relation to replication (in particular to merge replication). If you have a publisher/subscriber model then it would probably be ok to not upgrade the subscribers, provided your Publisher/Distributor are SP4... but you would need to upgrade them all if you are using merge replication.
There's a section in the documentation that accompanies SP4 in regards to deploying SP4 in replicated environments, probably best to read that.
June 22, 2002 at 12:30 pm
Also I am confused, you state you are experiencing many memory leaks. I have been involved in the SP betas and using SQL in bland form on a test server. There have been no memory leaks nor has any been reported. Hoa are you determining memory leaks and what processes are they related too. I do have an old Informix server I have to get data from and when done with linked server I had a memory leak but the was the Informix driver (known issue with Informix) and not SQL.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
June 24, 2002 at 7:54 am
Thanks for all the responses.
Antares686, I have seen plenty of memory leaks in SQL 7.0, when a simple DBCC shrinkdb is run. From what I've read this IS a documented problem with SQL 7.0 and supposedly SP3 addressess it?.?
Our problem is the publishers, are located at remote sites. They are behind firewalls and are standalone. They replicate to our subscriber which we can get to a little easier.
Knowing what I know, and receiving all the great advice I have from you guys, believe me I want all our servers operating on the same SP like all my SQL 2000 servers are.
However, deploying the SP's to our remote sites is proving to be the real challenge here.
Thanks again,
Christine
Aurora
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply