Friday, February 10, 2012

Constant locking issue

My SQL server has 1G Ram, and I noticed that it was using about 700MB of it
constant. Next day I looked and usage was gone up to 798 constant.
Is it possible that SQL server is not releasing the memory it is using,
thus causing slow downs, and lock finally.
My guess is that SQL server doesn't realy make use for windows page file.
MC
"MC" <webmaster@.ozoptics.com> wrote in message
news:endIdYzNGHA.2628@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have a SQL server 2000 running on Windows 2000 server, SP4 (4 CPU, and
2G
> RAM)
> We use this for Maximizer ECRM application, but lately (past 2-3month) we
> seem to get more SQL locking issues while running application.
> When I try to kill the proccess that causing the lock, it still shows the
> proccess in Enterprise manager, but this leads to more locks somehow.
> If I try to stop SQL server, at this stage, SQL server engine hangs then
> times out (doesn't properly stop)
> If I try to re-start the whole server, server itself hangs on the blue
> screen trying to shut down
> (I can re-start server, no problem, as long as these locks doesn't occur)
> No CRM application changes.
> Only changes on the server is constant windows patches, Symantec
> Anti-Virus updates.
> I don't know if any of those windows security update is the cause.
> I donwloaded latest SQL 2000 updates and installed still seem to happen.
> Nothing in the windows event log that tells me that I am having software
or
> hardware issues
> I noticed this error in SQL event log though, but I don't remember
getting
> this error on previous SQL crashes, due to locks
> Any idea appreciated
> MC
> SQL log
> SQL Server has encountered 1 occurrence(s) of IO requests taking longer
than
> 15 seconds to complete on file [E:\MaxData\AddrBks\OZCUSTOMERS_Log.ldf
] in
> database [OZCUSTOMERS] (15). The OS file handle is 0x000003C8. The
offset
> of the latest long IO is: 0x000000004a9c00
>SQL Server loves memory. It will give back to the OS only when necessary.
My workstation and laptop each have 2GB and I suggest that you give your
server more RAM.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"MC" <webmaster@.ozoptics.com> wrote in message
news:u9Rd5HLOGHA.1216@.TK2MSFTNGP14.phx.gbl...
My SQL server has 1G Ram, and I noticed that it was using about 700MB of it
constant. Next day I looked and usage was gone up to 798 constant.
Is it possible that SQL server is not releasing the memory it is using,
thus causing slow downs, and lock finally.
My guess is that SQL server doesn't realy make use for windows page file.
MC
"MC" <webmaster@.ozoptics.com> wrote in message
news:endIdYzNGHA.2628@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have a SQL server 2000 running on Windows 2000 server, SP4 (4 CPU, and
2G
> RAM)
> We use this for Maximizer ECRM application, but lately (past 2-3month) we
> seem to get more SQL locking issues while running application.
> When I try to kill the proccess that causing the lock, it still shows the
> proccess in Enterprise manager, but this leads to more locks somehow.
> If I try to stop SQL server, at this stage, SQL server engine hangs then
> times out (doesn't properly stop)
> If I try to re-start the whole server, server itself hangs on the blue
> screen trying to shut down
> (I can re-start server, no problem, as long as these locks doesn't occur)
> No CRM application changes.
> Only changes on the server is constant windows patches, Symantec
> Anti-Virus updates.
> I don't know if any of those windows security update is the cause.
> I donwloaded latest SQL 2000 updates and installed still seem to happen.
> Nothing in the windows event log that tells me that I am having software
or
> hardware issues
> I noticed this error in SQL event log though, but I don't remember
getting
> this error on previous SQL crashes, due to locks
> Any idea appreciated
> MC
> SQL log
> SQL Server has encountered 1 occurrence(s) of IO requests taking longer
than
> 15 seconds to complete on file [E:\MaxData\AddrBks\OZCUSTOMERS_Log.ldf
] in
> database [OZCUSTOMERS] (15). The OS file handle is 0x000003C8. The
offset
> of the latest long IO is: 0x000000004a9c00
>|||The problem is, this morning I went back to check the SQL server memory
usage has gone up to 850M
over all memory usage by the whole server was very close to 1G
Even though there were less users in the morning
(Yesterday peak of usage, SQL server memory usage was around 798M)
This tells me something in SQL server holding on to memory that doesn't
release
SQL server is set to Dynamically configure SQL memory, minimum memory query
is set to 1024Kb
MC
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#rTA1fOOGHA.2628@.TK2MSFTNGP15.phx.gbl...
> SQL Server loves memory. It will give back to the OS only when necessary.
> My workstation and laptop each have 2GB and I suggest that you give your
> server more RAM.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "MC" <webmaster@.ozoptics.com> wrote in message
> news:u9Rd5HLOGHA.1216@.TK2MSFTNGP14.phx.gbl...
> My SQL server has 1G Ram, and I noticed that it was using about 700MB of
it
> constant. Next day I looked and usage was gone up to 798 constant.
> Is it possible that SQL server is not releasing the memory it is using,
> thus causing slow downs, and lock finally.
> My guess is that SQL server doesn't realy make use for windows page file.
> MC
>
> "MC" <webmaster@.ozoptics.com> wrote in message
> news:endIdYzNGHA.2628@.TK2MSFTNGP15.phx.gbl...
> 2G
we[vbcol=seagreen]
the[vbcol=seagreen]
occur)[vbcol=seagreen]
> or
> getting
> than
in[vbcol=seagreen]
> offset
>

No comments:

Post a Comment