Context Swiitching

Hi All
We recently upgraded one of our application rinning on .net and sql server
to New IBM Server.
This is a Quad processor(1.7Ghz), with 8 gb of ram. but when we migrated we
found that the system is much slower then the old system,
This is a Win2K3, running SQL 2K with SP3a. , hyperthreading on.
All my reporting queries are running slower. in fact the whole application
is running slower.
What i found out is, on old and new box the CPU util is just around 40%
with full load. But on old box which is a dual processor with hyperthreading
on, the contex swith/sec is 4000 but on new box it is about 9000/sec, I did
turn on the Lightweight pooling so that SQL uses Fiber instead of thread
mode, i have tried adjusting both the parallelism paramater, cost threshold
and max degree.. but do not see any difference in performance..Context
swithching is still 8k to 9k .
please help..
Definitely turn off the fiber mode either way. An 4 proc system will have
more context switching than a 2 proc in general, especially if they are HT.
You also want to make sure the MAXDOP at the server level is no more than
the # of physical processors. I would even try 2 and see how it goes. If the
new machine can process stuff faster or with more processors and your I/O
can't keep up or you have too little memory you can also get more context
switches. This is basically due to the fact it can't keep working while it
is waiting on resources and will swap out for another thread. That causes
more overhead and decreases overall throughput. But the bottom line is that
you can't directly compare two completely different hardware platforms as
apples to apples. You didn't mention what the old system was , how much ram,
speed of procs etc but it could be you need to adjust your configuration to
take advantage of the newer hardware.
Andrew J. Kelly SQL MVP
"Nik" <sqlserverkb@.yahoo.com> wrote in message
news:%23htrpLQQFHA.2584@.TK2MSFTNGP15.phx.gbl...
> Hi All
> We recently upgraded one of our application rinning on .net and sql server
> to New IBM Server.
> This is a Quad processor(1.7Ghz), with 8 gb of ram. but when we migrated
> we
> found that the system is much slower then the old system,
> This is a Win2K3, running SQL 2K with SP3a. , hyperthreading on.
> All my reporting queries are running slower. in fact the whole application
> is running slower.
> What i found out is, on old and new box the CPU util is just around 40%
> with full load. But on old box which is a dual processor with
> hyperthreading
> on, the contex swith/sec is 4000 but on new box it is about 9000/sec, I
> did
> turn on the Lightweight pooling so that SQL uses Fiber instead of thread
> mode, i have tried adjusting both the parallelism paramater, cost
> threshold
> and max degree.. but do not see any difference in performance..Context
> swithching is still 8k to 9k .
> please help..
>
>
|||Thanks Andrew,
I already made the MAXDOP to 4 . no improvement.
Old System is 2 procs(2Ghz), 2Gb ram, HT on, but it hosts SQL, IIS,
Reporting Services, Web Services
New One is 4 proc (1.7Ghz),8GB ram, HT on but just hosts SQL Server and
reports database used for reporting services.
Do you think the CPU speed is making it much slower, which i do not think
would be the case, I know the queries are badly written, and i mean bad.
but still the same query runs much much say on old system it takes 17 sec to
bring the report on new system it takes around 27 to 30 secs to bring the
report up.
Database setups are the same, we are using DVP but both the databases reside
on the same server and a dvp is created on both the datbases.
what elso do you think i should check for...
any ideas are most welcome..
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OViGjBRQFHA.164@.TK2MSFTNGP12.phx.gbl...
> Definitely turn off the fiber mode either way. An 4 proc system will have
> more context switching than a 2 proc in general, especially if they are
HT.
> You also want to make sure the MAXDOP at the server level is no more than
> the # of physical processors. I would even try 2 and see how it goes. If
the
> new machine can process stuff faster or with more processors and your I/O
> can't keep up or you have too little memory you can also get more context
> switches. This is basically due to the fact it can't keep working while it
> is waiting on resources and will swap out for another thread. That causes
> more overhead and decreases overall throughput. But the bottom line is
that
> you can't directly compare two completely different hardware platforms as
> apples to apples. You didn't mention what the old system was , how much
ram,
> speed of procs etc but it could be you need to adjust your configuration
to[vbcol=seagreen]
> take advantage of the newer hardware.
> --
> Andrew J. Kelly SQL MVP
>
> "Nik" <sqlserverkb@.yahoo.com> wrote in message
> news:%23htrpLQQFHA.2584@.TK2MSFTNGP15.phx.gbl...
server[vbcol=seagreen]
application[vbcol=seagreen]
40%
>
|||DPV's don't do a whole lot in most cases for performance if they are on the
same machine. If your query scans the whole table then partitioning it out
may help but better indexing would probably do more. When it comes to
processors faster is always better but the amount of cache may make quite a
bit of difference as well. A faster proc with more L2 or L3 cache can be a
lot faster than a slower one with less cache. If your queries are poorly
written then you are probably doing lots of scans and you may be using too
much parallelism still. Try setting the MAXDOP to 2 and see if that makes a
difference. Are the query plans the same as before? Have you run
sp_updatestats lately?
Andrew J. Kelly SQL MVP
"Nik" <sqlserverkb@.yahoo.com> wrote in message
news:%23ua%23CRRQFHA.3664@.TK2MSFTNGP15.phx.gbl...
> Thanks Andrew,
> I already made the MAXDOP to 4 . no improvement.
> Old System is 2 procs(2Ghz), 2Gb ram, HT on, but it hosts SQL, IIS,
> Reporting Services, Web Services
> New One is 4 proc (1.7Ghz),8GB ram, HT on but just hosts SQL Server and
> reports database used for reporting services.
> Do you think the CPU speed is making it much slower, which i do not think
> would be the case, I know the queries are badly written, and i mean bad.
> but still the same query runs much much say on old system it takes 17 sec
> to
> bring the report on new system it takes around 27 to 30 secs to bring the
> report up.
> Database setups are the same, we are using DVP but both the databases
> reside
> on the same server and a dvp is created on both the datbases.
> what elso do you think i should check for...
> any ideas are most welcome..
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OViGjBRQFHA.164@.TK2MSFTNGP12.phx.gbl...
> HT.
> the
> that
> ram,
> to
> server
> application
> 40%
>
|||Yes DVP perrformance is not affected as it is on the same box, and that was
the reason we had to bring on one box.
but The older box has 512k L3 on2.8 ghz and new one has 1Mb L3 on 1.5 ghz
still i do not understand the context switching.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:O1r9EXSQFHA.688@.TK2MSFTNGP10.phx.gbl...
> DPV's don't do a whole lot in most cases for performance if they are on
the
> same machine. If your query scans the whole table then partitioning it
out
> may help but better indexing would probably do more. When it comes to
> processors faster is always better but the amount of cache may make quite
a
> bit of difference as well. A faster proc with more L2 or L3 cache can be
a
> lot faster than a slower one with less cache. If your queries are poorly
> written then you are probably doing lots of scans and you may be using too
> much parallelism still. Try setting the MAXDOP to 2 and see if that makes
a[vbcol=seagreen]
> difference. Are the query plans the same as before? Have you run
> sp_updatestats lately?
> --
> Andrew J. Kelly SQL MVP
>
> "Nik" <sqlserverkb@.yahoo.com> wrote in message
> news:%23ua%23CRRQFHA.3664@.TK2MSFTNGP15.phx.gbl...
think[vbcol=seagreen]
sec[vbcol=seagreen]
the[vbcol=seagreen]
than[vbcol=seagreen]
If[vbcol=seagreen]
I/O[vbcol=seagreen]
context[vbcol=seagreen]
as[vbcol=seagreen]
configuration[vbcol=seagreen]
I[vbcol=seagreen]
performance..Context
>
|||What about disk system and where are located tempdb, data and transaction log.
AMB
"Nik" wrote:

> Thanks Andrew,
> I already made the MAXDOP to 4 . no improvement.
> Old System is 2 procs(2Ghz), 2Gb ram, HT on, but it hosts SQL, IIS,
> Reporting Services, Web Services
> New One is 4 proc (1.7Ghz),8GB ram, HT on but just hosts SQL Server and
> reports database used for reporting services.
> Do you think the CPU speed is making it much slower, which i do not think
> would be the case, I know the queries are badly written, and i mean bad.
> but still the same query runs much much say on old system it takes 17 sec to
> bring the report on new system it takes around 27 to 30 secs to bring the
> report up.
> Database setups are the same, we are using DVP but both the databases reside
> on the same server and a dvp is created on both the datbases.
> what elso do you think i should check for...
> any ideas are most welcome..
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OViGjBRQFHA.164@.TK2MSFTNGP12.phx.gbl...
> HT.
> the
> that
> ram,
> to
> server
> application
> 40%
>
>
|||But the older box was almost twice as fast processor speed wise. That is a
big difference. How could you even get a new box with just 1.5GHZ proc's?
What about the disk system? Is that the same or is that different as well.
Andrew J. Kelly SQL MVP
"Nik" <sqlserverkb@.yahoo.com> wrote in message
news:%23jvSu6SQFHA.1500@.TK2MSFTNGP09.phx.gbl...
> Yes DVP perrformance is not affected as it is on the same box, and that
> was
> the reason we had to bring on one box.
> but The older box has 512k L3 on2.8 ghz and new one has 1Mb L3 on 1.5 ghz
> still i do not understand the context switching.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:O1r9EXSQFHA.688@.TK2MSFTNGP10.phx.gbl...
> the
> out
> a
> a
> a
> think
> sec
> the
> than
> If
> I/O
> context
> as
> configuration
> I
> performance..Context
>
|||AFAIK, you can't event get Xeons/Pentium that slow anymore. Maybe IA64?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23GFEvOWQFHA.3336@.TK2MSFTNGP09.phx.gbl...
> But the older box was almost twice as fast processor speed wise. That is
> a big difference. How could you even get a new box with just 1.5GHZ
> proc's? What about the disk system? Is that the same or is that different
> as well.
> --
> Andrew J. Kelly SQL MVP
>
> "Nik" <sqlserverkb@.yahoo.com> wrote in message
> news:%23jvSu6SQFHA.1500@.TK2MSFTNGP09.phx.gbl...
>
|||i know but this was a management decision, without the geting dba's opinion.
I know they had screwed up in that part, but do you guys think that CPU
speed is contributing to the slowness of the entire system,
the I/O subsystem is faster on the new box.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OltsgBcQFHA.3544@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> AFAIK, you can't event get Xeons/Pentium that slow anymore. Maybe IA64?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23GFEvOWQFHA.3336@.TK2MSFTNGP09.phx.gbl...
is[vbcol=seagreen]
different[vbcol=seagreen]
ghz[vbcol=seagreen]
on[vbcol=seagreen]
it[vbcol=seagreen]
17[vbcol=seagreen]
bring[vbcol=seagreen]
databases[vbcol=seagreen]
will[vbcol=seagreen]
more[vbcol=seagreen]
goes.[vbcol=seagreen]
your[vbcol=seagreen]
line[vbcol=seagreen]
sql
>
|||TempDb is on a raid 10,same with data and tran logs. they all are on
different drives..with individual controller
Tempdb is scattered on 4 data files..
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> wrote in message
news:F9CE53C8-8563-41F9-8A4A-9818B9C5C0C0@.microsoft.com...
> What about disk system and where are located tempdb, data and transaction
log.[vbcol=seagreen]
>
> AMB
> "Nik" wrote:
think[vbcol=seagreen]
sec to[vbcol=seagreen]
the[vbcol=seagreen]
reside[vbcol=seagreen]
have[vbcol=seagreen]
are[vbcol=seagreen]
than[vbcol=seagreen]
If[vbcol=seagreen]
I/O[vbcol=seagreen]
context[vbcol=seagreen]
while it[vbcol=seagreen]
causes[vbcol=seagreen]
is[vbcol=seagreen]
as[vbcol=seagreen]
much[vbcol=seagreen]
configuration[vbcol=seagreen]
migrated[vbcol=seagreen]
around[vbcol=seagreen]
9000/sec, I[vbcol=seagreen]
thread[vbcol=seagreen]
performance..Context[vbcol=seagreen]

Context Swiitching

Hi All
We recently upgraded one of our application rinning on .net and sql server
to New IBM Server.
This is a Quad processor(1.7Ghz), with 8 gb of ram. but when we migrated we
found that the system is much slower then the old system,
This is a Win2K3, running SQL 2K with SP3a. , hyperthreading on.
All my reporting queries are running slower. in fact the whole application
is running slower.
What i found out is, on old and new box the CPU util is just around 40%
with full load. But on old box which is a dual processor with hyperthreading
on, the contex swith/sec is 4000 but on new box it is about 9000/sec, I did
turn on the Lightweight pooling so that SQL uses Fiber instead of thread
mode, i have tried adjusting both the parallelism paramater, cost threshold
and max degree.. but do not see any difference in performance..Context
swithching is still 8k to 9k .
please help..Definitely turn off the fiber mode either way. An 4 proc system will have
more context switching than a 2 proc in general, especially if they are HT.
You also want to make sure the MAXDOP at the server level is no more than
the # of physical processors. I would even try 2 and see how it goes. If the
new machine can process stuff faster or with more processors and your I/O
can't keep up or you have too little memory you can also get more context
switches. This is basically due to the fact it can't keep working while it
is waiting on resources and will swap out for another thread. That causes
more overhead and decreases overall throughput. But the bottom line is that
you can't directly compare two completely different hardware platforms as
apples to apples. You didn't mention what the old system was , how much ram,
speed of procs etc but it could be you need to adjust your configuration to
take advantage of the newer hardware.
Andrew J. Kelly SQL MVP
"Nik" <sqlserverkb@.yahoo.com> wrote in message
news:%23htrpLQQFHA.2584@.TK2MSFTNGP15.phx.gbl...
> Hi All
> We recently upgraded one of our application rinning on .net and sql server
> to New IBM Server.
> This is a Quad processor(1.7Ghz), with 8 gb of ram. but when we migrated
> we
> found that the system is much slower then the old system,
> This is a Win2K3, running SQL 2K with SP3a. , hyperthreading on.
> All my reporting queries are running slower. in fact the whole application
> is running slower.
> What i found out is, on old and new box the CPU util is just around 40%
> with full load. But on old box which is a dual processor with
> hyperthreading
> on, the contex swith/sec is 4000 but on new box it is about 9000/sec, I
> did
> turn on the Lightweight pooling so that SQL uses Fiber instead of thread
> mode, i have tried adjusting both the parallelism paramater, cost
> threshold
> and max degree.. but do not see any difference in performance..Context
> swithching is still 8k to 9k .
> please help..
>
>|||Thanks Andrew,
I already made the MAXDOP to 4 . no improvement.
Old System is 2 procs(2Ghz), 2Gb ram, HT on, but it hosts SQL, IIS,
Reporting Services, Web Services
New One is 4 proc (1.7Ghz),8GB ram, HT on but just hosts SQL Server and
reports database used for reporting services.
Do you think the CPU speed is making it much slower, which i do not think
would be the case, I know the queries are badly written, and i mean bad.
but still the same query runs much much say on old system it takes 17 sec to
bring the report on new system it takes around 27 to 30 secs to bring the
report up.
Database setups are the same, we are using DVP but both the databases reside
on the same server and a dvp is created on both the datbases.
what elso do you think i should check for...
any ideas are most welcome..
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OViGjBRQFHA.164@.TK2MSFTNGP12.phx.gbl...
> Definitely turn off the fiber mode either way. An 4 proc system will have
> more context switching than a 2 proc in general, especially if they are
HT.
> You also want to make sure the MAXDOP at the server level is no more than
> the # of physical processors. I would even try 2 and see how it goes. If
the
> new machine can process stuff faster or with more processors and your I/O
> can't keep up or you have too little memory you can also get more context
> switches. This is basically due to the fact it can't keep working while it
> is waiting on resources and will swap out for another thread. That causes
> more overhead and decreases overall throughput. But the bottom line is
that
> you can't directly compare two completely different hardware platforms as
> apples to apples. You didn't mention what the old system was , how much
ram,
> speed of procs etc but it could be you need to adjust your configuration
to
> take advantage of the newer hardware.
> --
> Andrew J. Kelly SQL MVP
>
> "Nik" <sqlserverkb@.yahoo.com> wrote in message
> news:%23htrpLQQFHA.2584@.TK2MSFTNGP15.phx.gbl...
server[vbcol=seagreen]
application[vbcol=seagreen]
40%[vbcol=seagreen]
>|||DPV's don't do a whole lot in most cases for performance if they are on the
same machine. If your query scans the whole table then partitioning it out
may help but better indexing would probably do more. When it comes to
processors faster is always better but the amount of cache may make quite a
bit of difference as well. A faster proc with more L2 or L3 cache can be a
lot faster than a slower one with less cache. If your queries are poorly
written then you are probably doing lots of scans and you may be using too
much parallelism still. Try setting the MAXDOP to 2 and see if that makes a
difference. Are the query plans the same as before? Have you run
sp_updatestats lately?
Andrew J. Kelly SQL MVP
"Nik" <sqlserverkb@.yahoo.com> wrote in message
news:%23ua%23CRRQFHA.3664@.TK2MSFTNGP15.phx.gbl...
> Thanks Andrew,
> I already made the MAXDOP to 4 . no improvement.
> Old System is 2 procs(2Ghz), 2Gb ram, HT on, but it hosts SQL, IIS,
> Reporting Services, Web Services
> New One is 4 proc (1.7Ghz),8GB ram, HT on but just hosts SQL Server and
> reports database used for reporting services.
> Do you think the CPU speed is making it much slower, which i do not think
> would be the case, I know the queries are badly written, and i mean bad.
> but still the same query runs much much say on old system it takes 17 sec
> to
> bring the report on new system it takes around 27 to 30 secs to bring the
> report up.
> Database setups are the same, we are using DVP but both the databases
> reside
> on the same server and a dvp is created on both the datbases.
> what elso do you think i should check for...
> any ideas are most welcome..
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OViGjBRQFHA.164@.TK2MSFTNGP12.phx.gbl...
> HT.
> the
> that
> ram,
> to
> server
> application
> 40%
>|||Yes DVP perrformance is not affected as it is on the same box, and that was
the reason we had to bring on one box.
but The older box has 512k L3 on2.8 ghz and new one has 1Mb L3 on 1.5 ghz
still i do not understand the context switching.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:O1r9EXSQFHA.688@.TK2MSFTNGP10.phx.gbl...
> DPV's don't do a whole lot in most cases for performance if they are on
the
> same machine. If your query scans the whole table then partitioning it
out
> may help but better indexing would probably do more. When it comes to
> processors faster is always better but the amount of cache may make quite
a
> bit of difference as well. A faster proc with more L2 or L3 cache can be
a
> lot faster than a slower one with less cache. If your queries are poorly
> written then you are probably doing lots of scans and you may be using too
> much parallelism still. Try setting the MAXDOP to 2 and see if that makes
a
> difference. Are the query plans the same as before? Have you run
> sp_updatestats lately?
> --
> Andrew J. Kelly SQL MVP
>
> "Nik" <sqlserverkb@.yahoo.com> wrote in message
> news:%23ua%23CRRQFHA.3664@.TK2MSFTNGP15.phx.gbl...
think[vbcol=seagreen]
sec[vbcol=seagreen]
the[vbcol=seagreen]
than[vbcol=seagreen]
If[vbcol=seagreen]
I/O[vbcol=seagreen]
context[vbcol=seagreen]
as[vbcol=seagreen]
configuration[vbcol=seagreen]
I[vbcol=seagreen]
performance..Context[vbcol=seagreen]
>|||What about disk system and where are located tempdb, data and transaction lo
g.
AMB
"Nik" wrote:

> Thanks Andrew,
> I already made the MAXDOP to 4 . no improvement.
> Old System is 2 procs(2Ghz), 2Gb ram, HT on, but it hosts SQL, IIS,
> Reporting Services, Web Services
> New One is 4 proc (1.7Ghz),8GB ram, HT on but just hosts SQL Server and
> reports database used for reporting services.
> Do you think the CPU speed is making it much slower, which i do not think
> would be the case, I know the queries are badly written, and i mean bad.
> but still the same query runs much much say on old system it takes 17 sec
to
> bring the report on new system it takes around 27 to 30 secs to bring the
> report up.
> Database setups are the same, we are using DVP but both the databases resi
de
> on the same server and a dvp is created on both the datbases.
> what elso do you think i should check for...
> any ideas are most welcome..
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OViGjBRQFHA.164@.TK2MSFTNGP12.phx.gbl...
> HT.
> the
> that
> ram,
> to
> server
> application
> 40%
>
>|||But the older box was almost twice as fast processor speed wise. That is a
big difference. How could you even get a new box with just 1.5GHZ proc's?
What about the disk system? Is that the same or is that different as well.
Andrew J. Kelly SQL MVP
"Nik" <sqlserverkb@.yahoo.com> wrote in message
news:%23jvSu6SQFHA.1500@.TK2MSFTNGP09.phx.gbl...
> Yes DVP perrformance is not affected as it is on the same box, and that
> was
> the reason we had to bring on one box.
> but The older box has 512k L3 on2.8 ghz and new one has 1Mb L3 on 1.5 ghz
> still i do not understand the context switching.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:O1r9EXSQFHA.688@.TK2MSFTNGP10.phx.gbl...
> the
> out
> a
> a
> a
> think
> sec
> the
> than
> If
> I/O
> context
> as
> configuration
> I
> performance..Context
>|||AFAIK, you can't event get Xeons/Pentium that slow anymore. Maybe IA64?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23GFEvOWQFHA.3336@.TK2MSFTNGP09.phx.gbl...
> But the older box was almost twice as fast processor speed wise. That is
> a big difference. How could you even get a new box with just 1.5GHZ
> proc's? What about the disk system? Is that the same or is that different
> as well.
> --
> Andrew J. Kelly SQL MVP
>
> "Nik" <sqlserverkb@.yahoo.com> wrote in message
> news:%23jvSu6SQFHA.1500@.TK2MSFTNGP09.phx.gbl...
>|||i know but this was a management decision, without the geting dba's opinion.
I know they had screwed up in that part, but do you guys think that CPU
speed is contributing to the slowness of the entire system,
the I/O subsystem is faster on the new box.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OltsgBcQFHA.3544@.TK2MSFTNGP12.phx.gbl...
> AFAIK, you can't event get Xeons/Pentium that slow anymore. Maybe IA64?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23GFEvOWQFHA.3336@.TK2MSFTNGP09.phx.gbl...
is[vbcol=seagreen]
different[vbcol=seagreen]
ghz[vbcol=seagreen]
on[vbcol=seagreen]
it[vbcol=seagreen]
17[vbcol=seagreen]
bring[vbcol=seagreen]
databases[vbcol=seagreen]
will[vbcol=seagreen]
more[vbcol=seagreen]
goes.[vbcol=seagreen]
your[vbcol=seagreen]
line[vbcol=seagreen]
sql[vbcol=seagreen]
>|||TempDb is on a raid 10,same with data and tran logs. they all are on
different drives..with individual controller
Tempdb is scattered on 4 data files..
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> wrote in message
news:F9CE53C8-8563-41F9-8A4A-9818B9C5C0C0@.microsoft.com...
> What about disk system and where are located tempdb, data and transaction
log.[vbcol=seagreen]
>
> AMB
> "Nik" wrote:
>
think[vbcol=seagreen]
sec to[vbcol=seagreen]
the[vbcol=seagreen]
reside[vbcol=seagreen]
have[vbcol=seagreen]
are[vbcol=seagreen]
than[vbcol=seagreen]
If[vbcol=seagreen]
I/O[vbcol=seagreen]
context[vbcol=seagreen]
while it[vbcol=seagreen]
causes[vbcol=seagreen]
is[vbcol=seagreen]
as[vbcol=seagreen]
much[vbcol=seagreen]
configuration[vbcol=seagreen]
migrated[vbcol=seagreen]
around[vbcol=seagreen]
9000/sec, I[vbcol=seagreen]
thread[vbcol=seagreen]
performance..Context[vbcol=seagreen]

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[vbcol=seagreen]
> 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
> offset
>

Constant locking issue

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: 0x000000004a9c00Could you run a diagnostic on your disk subsystem?
--
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: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|||I ran Dell's Hard drive diagnostics (Dell Server) seem ok
(Server has Raid 5 configuration, OS and SQL program installed on C: drive,
my application data MDF, LDF files on E: drive, and log and DB backups to G
drive with plenty of space. Moved page file to G drive from C
The error that I mentioned, never remember seeing on same locking issues
before. According to Microsoft articles, that type of issue is not easy to
pinpoint.
MC
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#MvpAszNGHA.2472@.TK2MSFTNGP11.phx.gbl...
> Could you run a diagnostic on your disk subsystem?
> --
> 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: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
>|||Your .MDF and .LDF files should be on separate drives. This is both for
performance as well as safety. If your E: drive blew, you'd be in trouble.
Also, RAID5 is slow for update. RAID10 is preferable, if you have space
and money.
Also, check my response re RAM. More is better.
--
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:O1HeACIOGHA.2268@.TK2MSFTNGP09.phx.gbl...
I ran Dell's Hard drive diagnostics (Dell Server) seem ok
(Server has Raid 5 configuration, OS and SQL program installed on C: drive,
my application data MDF, LDF files on E: drive, and log and DB backups to G
drive with plenty of space. Moved page file to G drive from C
The error that I mentioned, never remember seeing on same locking issues
before. According to Microsoft articles, that type of issue is not easy to
pinpoint.
MC
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#MvpAszNGHA.2472@.TK2MSFTNGP11.phx.gbl...
> Could you run a diagnostic on your disk subsystem?
> --
> 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: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
>|||When it comes to having LDF file being in different drive,
this is only valid, if you have 2 physical drives and not valid if you have
Raid 5, or Raid 10
(4 x SCSI disk)
This is how we have been tought and many people says the samething. Did I
miss anything here?
MC
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:uIsOohOOGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Your .MDF and .LDF files should be on separate drives. This is both for
> performance as well as safety. If your E: drive blew, you'd be in
trouble.
> Also, RAID5 is slow for update. RAID10 is preferable, if you have space
> and money.
> Also, check my response re RAM. More is better.
> --
> 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:O1HeACIOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> I ran Dell's Hard drive diagnostics (Dell Server) seem ok
> (Server has Raid 5 configuration, OS and SQL program installed on C:
drive,
> my application data MDF, LDF files on E: drive, and log and DB backups to
G
> drive with plenty of space. Moved page file to G drive from C
> The error that I mentioned, never remember seeing on same locking issues
> before. According to Microsoft articles, that type of issue is not easy to
> pinpoint.
> MC
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:#MvpAszNGHA.2472@.TK2MSFTNGP11.phx.gbl...
> > Could you run a diagnostic on your disk subsystem?
> >
> > --
> > 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: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
> >
> >
>|||Of course I meant that they should be on separate physical drives. That
also applies if you are using RAID. What if 2 disks fail in your RAID5?
That said, have you been able to use System Monitor to look at the Avg Disk
Queue Lengths on each physical disk set - both read and write queues? The
figure should not be 2X the number of spindles.
--
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:eYVKxqUOGHA.1360@.TK2MSFTNGP10.phx.gbl...
When it comes to having LDF file being in different drive,
this is only valid, if you have 2 physical drives and not valid if you have
Raid 5, or Raid 10
(4 x SCSI disk)
This is how we have been tought and many people says the samething. Did I
miss anything here?
MC
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:uIsOohOOGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Your .MDF and .LDF files should be on separate drives. This is both for
> performance as well as safety. If your E: drive blew, you'd be in
trouble.
> Also, RAID5 is slow for update. RAID10 is preferable, if you have space
> and money.
> Also, check my response re RAM. More is better.
> --
> 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:O1HeACIOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> I ran Dell's Hard drive diagnostics (Dell Server) seem ok
> (Server has Raid 5 configuration, OS and SQL program installed on C:
drive,
> my application data MDF, LDF files on E: drive, and log and DB backups to
G
> drive with plenty of space. Moved page file to G drive from C
> The error that I mentioned, never remember seeing on same locking issues
> before. According to Microsoft articles, that type of issue is not easy to
> pinpoint.
> MC
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:#MvpAszNGHA.2472@.TK2MSFTNGP11.phx.gbl...
> > Could you run a diagnostic on your disk subsystem?
> >
> > --
> > 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: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
> >
> >
>

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...
> > 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
> >
> >
>

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
>