Bug in a Stored Procedure [sys].[sp_dbmmonitorupdate]

Hi guys,

I found an annoying bug in the system sproc [sys].[sp_dbmmonitorupdate]. There in line
308 : set @.database_name = db_name( @.database_id )
it should basically state
set @.database_name = QUOTENAME(db_name( @.database_id ))
because if a database has a space or point in the name this causes the sproc to fail with the error:
"Incorrect syntax near '.'."

has someone any idea how to change this sys sproc?
or an idea for a workaround?

thanks...
darkook, let me ask the other way around:

i cannot change the sys sproc, can I? in that case I need a sproc which is deployed in the msdb (there is a check in the sp_dbmmonitorupdate which says it must be executed in the context of the msdb). how ever, I understand that no sprocs should be deployed in msdb. any ideas how to solve this problem?

thx!

Buffer Cache Hit Ration on a Reporting DB

Hi all.
First off, I'm a sys admin, not a DBA.
I'm trying to improve buffer cache hit ratio on a reporting database.
Database is approximately 130GB. Current server is a Proliant ML530 G2,
2-way 3.6Ghz, 8GB RAM. Multiple datafiles spread out across 4 separate
raid 5 arrays. Disk queuing is pretty good. Sometimes we hit a rough
day.
I've read over and over how BCHR needs to be above 90%, optimally
around 98-99%. On the live OLTP database, BCHR is fine with 8GB in the
system. On the reporting DB, it often drops to 80% or below.
My question is, should a reporting database have this large of a
difference in the hit ratio?
I'm working with our developer & DBA to improve the reports, but I also
need to make sure that the hardware is performing as good as it can.
I've got a DL585, 4-core Opteron in the wings with 16GB running Win2K3
x64. We're waiting to make sure SP4 is completely kosher with our
application before upgrading.
Thoughts, ideas? Much appreciated!
-AJ<ajohnson@.echecktrac.com> wrote in message
news:1144442893.581038.299300@.e56g2000cwe.googlegroups.com...
> Hi all.
> First off, I'm a sys admin, not a DBA.
> I'm trying to improve buffer cache hit ratio on a reporting database.
> Database is approximately 130GB. Current server is a Proliant ML530 G2,
> 2-way 3.6Ghz, 8GB RAM. Multiple datafiles spread out across 4 separate
> raid 5 arrays. Disk queuing is pretty good. Sometimes we hit a rough
> day.
> I've read over and over how BCHR needs to be above 90%, optimally
> around 98-99%. On the live OLTP database, BCHR is fine with 8GB in the
> system.
Unfortunatly BCHR on OLTP databases is an irrelevant metric. A high BCHR
often results from inefficient queries reading lots and lots of pages in the
cache. And the memory size/database size ratio of an OLTP system often
doesn't even permit a low cache hit ratio.

>On the reporting DB, it often drops to 80% or below.
> My question is, should a reporting database have this large of a
> difference in the hit ratio?
Yes, it will quite likely be lower. It's a matter of the ratio between the
cache (<8GB) and the data (130GB), and the predictablility of the queries
and acess paths. Better indexing can help improve performance, although
since indexing reduces total IO, not just physical IO, you might not see a
better BCHR.

> I'm working with our developer & DBA to improve the reports, but I also
> need to make sure that the hardware is performing as good as it can.
> I've got a DL585, 4-core Opteron in the wings with 16GB running Win2K3
> x64. We're waiting to make sure SP4 is completely kosher with our
> application before upgrading.
>
Going all the way to SQL 2005 64-bit will help alot more. You can use all
that memory much more efficiently, plus it's easier to monitor the
performance and find the expensive queries.
David

Buffer Cache Hit Ration on a Reporting DB

Hi all.
First off, I'm a sys admin, not a DBA.
I'm trying to improve buffer cache hit ratio on a reporting database.
Database is approximately 130GB. Current server is a Proliant ML530 G2,
2-way 3.6Ghz, 8GB RAM. Multiple datafiles spread out across 4 separate
raid 5 arrays. Disk queuing is pretty good. Sometimes we hit a rough
day.
I've read over and over how BCHR needs to be above 90%, optimally
around 98-99%. On the live OLTP database, BCHR is fine with 8GB in the
system. On the reporting DB, it often drops to 80% or below.
My question is, should a reporting database have this large of a
difference in the hit ratio?
I'm working with our developer & DBA to improve the reports, but I also
need to make sure that the hardware is performing as good as it can.
I've got a DL585, 4-core Opteron in the wings with 16GB running Win2K3
x64. We're waiting to make sure SP4 is completely kosher with our
application before upgrading.
Thoughts, ideas? Much appreciated!
-AJ<ajohnson@.echecktrac.com> wrote in message
news:1144442893.581038.299300@.e56g2000cwe.googlegroups.com...
> Hi all.
> First off, I'm a sys admin, not a DBA.
> I'm trying to improve buffer cache hit ratio on a reporting database.
> Database is approximately 130GB. Current server is a Proliant ML530 G2,
> 2-way 3.6Ghz, 8GB RAM. Multiple datafiles spread out across 4 separate
> raid 5 arrays. Disk queuing is pretty good. Sometimes we hit a rough
> day.
> I've read over and over how BCHR needs to be above 90%, optimally
> around 98-99%. On the live OLTP database, BCHR is fine with 8GB in the
> system.
Unfortunatly BCHR on OLTP databases is an irrelevant metric. A high BCHR
often results from inefficient queries reading lots and lots of pages in the
cache. And the memory size/database size ratio of an OLTP system often
doesn't even permit a low cache hit ratio.
>On the reporting DB, it often drops to 80% or below.
> My question is, should a reporting database have this large of a
> difference in the hit ratio?
Yes, it will quite likely be lower. It's a matter of the ratio between the
cache (<8GB) and the data (130GB), and the predictablility of the queries
and acess paths. Better indexing can help improve performance, although
since indexing reduces total IO, not just physical IO, you might not see a
better BCHR.
> I'm working with our developer & DBA to improve the reports, but I also
> need to make sure that the hardware is performing as good as it can.
> I've got a DL585, 4-core Opteron in the wings with 16GB running Win2K3
> x64. We're waiting to make sure SP4 is completely kosher with our
> application before upgrading.
>
Going all the way to SQL 2005 64-bit will help alot more. You can use all
that memory much more efficiently, plus it's easier to monitor the
performance and find the expensive queries.
David

BSOD blamed on nlemsql.sys

We have Server 2003 crashing every day or so, saying:
*** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x0000
0000
*** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
There are only two references to nlemsql on Google, neither of which are
related to a crash.
We're trying to narrow down what happens just before this, but haven't
managed to get any useful information yet.
It's a stab in the dark, but: anyone seen this before?
Rikthat's the good ole KERNEL_MODE_EXCEPTION_NOT_HANDLED, an error which the os
did not know how to handle. These are almost always hardware compatibility
issues, you need a firmware or driver update. The question is which one, it
looks like the driver for nlemsql.sys. That driver is not part of SQL
Server. Search your system looking for it and when you find it right click
on it and look at properties, and then the version tab. There should be a
clue as to what this driver is for, or who made it somewhere here. You can
also open it in text pad looking for clues. Another thing you can do is to
check the directory it is in which occasionally well tell you something.
this file is not part of SQL 2000 or SQl 2005.
I would also contact your vendor of the server.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rik Hemsley" <rik@.rikkus.info> wrote in message
news:uy$h8OSZGHA.3972@.TK2MSFTNGP04.phx.gbl...
> We have Server 2003 crashing every day or so, saying:
> *** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x0000
0000
> *** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
> There are only two references to nlemsql on Google, neither of which are
> related to a crash.
> We're trying to narrow down what happens just before this, but haven't
> managed to get any useful information yet.
> It's a stab in the dark, but: anyone seen this before?
> Rik

BSOD blamed on nlemsql.sys

We have Server 2003 crashing every day or so, saying:
*** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x00000000
*** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
There are only two references to nlemsql on Google, neither of which are
related to a crash.
We're trying to narrow down what happens just before this, but haven't
managed to get any useful information yet.
It's a stab in the dark, but: anyone seen this before?
Rikthat's the good ole KERNEL_MODE_EXCEPTION_NOT_HANDLED, an error which the os
did not know how to handle. These are almost always hardware compatibility
issues, you need a firmware or driver update. The question is which one, it
looks like the driver for nlemsql.sys. That driver is not part of SQL
Server. Search your system looking for it and when you find it right click
on it and look at properties, and then the version tab. There should be a
clue as to what this driver is for, or who made it somewhere here. You can
also open it in text pad looking for clues. Another thing you can do is to
check the directory it is in which occasionally well tell you something.
this file is not part of SQL 2000 or SQl 2005.
I would also contact your vendor of the server.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rik Hemsley" <rik@.rikkus.info> wrote in message
news:uy$h8OSZGHA.3972@.TK2MSFTNGP04.phx.gbl...
> We have Server 2003 crashing every day or so, saying:
> *** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x00000000
> *** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
> There are only two references to nlemsql on Google, neither of which are
> related to a crash.
> We're trying to narrow down what happens just before this, but haven't
> managed to get any useful information yet.
> It's a stab in the dark, but: anyone seen this before?
> Rik