November 10, 2002 at 6:48 am
HI..
My installation was in the following sequence.
WIn2k advanced server
WIn2k Service pack
Win2k Clustering service
MSSQL 7
MSSQL Service pack
MSSQL Failover Cluster.
After the above installtion one of our application had a memory leak. alomost 512kb per second on a normal load. We suspected the application and a complete code review was done. But there were no loose ends.
Finally we decided to reapply the WIN2k SP.
The leak issue was solved after applying the win2k service pack but the SQL Agent on the cluster had someproblems. Agent was unable to create tasks...
We now decided to run the service pack for SQL. MSSQL service pack 3 was run and the agent problem was solved but the replication was not working...The log reader was reporing error (sqlserver not available)..
It was high time spending time debugginng and we decided a complete reinstall.
The sequence is as follows
Win2k Advanced server
Win2k Clustering
MSSQL server
Win2k Service pack 2
SQL service pack 3
SQL Clustering.
Now the problem is the Memory leak again...and applying win2k sp3 again will solve this but SQL agent might conk. I cant afford to reinstall my machine again...is there any solution specifically for this problem...or am I missing the sequence.
levi
Jesus My Saviour
November 10, 2002 at 6:58 am
Usually what I do is
Win2k adv
Win2k sp's
win2k clustering setup
mssql 7
mssql cluster
mssql sp's
I haven't had a problem with that order yet. I like to go ahead and setup the sql7 cluster then apply the sp's to it seems to handle that better.
You may want to search microsoft's technet and see if they have had any issues with mem leaks and sql7 clustering.
Cheers,
Wes
November 10, 2002 at 5:08 pm
FIrst back up to your application. Can you give a little on what it does. Did you ever figure out in the first place what was casuing the memory leak. I have a C++ app GUI that I have been building with a server for the past year and have run across leaks that seemed to go away with the Service Pack that I ultimately found out were do to me NEWing a variable and not destroying it in proper sequence, the Service Pack masked the issue so I assumed was OS. Now as for SP3, tey instaed SP4 for SQL, if your issues is known they will pop you for a ticket charge on it. If you can again duplicate it they may determine the issue without charge, however I would do everything else without your app being added until done. Could still be the app in some way adn if your app is thye issue they will charge you.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply