Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
nscott
Starting Member
2 Posts |
 Posted - 2011-07-28 : 17:40:42
|
| I'm developing a Nagios plugin and only have access to SQL 2000. All of the sysperfinfo is stored in the master sysperfinfo, but Googling around reveals that this database was moved in SQL 2005 and 2008. If I use sysperfinfo will it not work with SQL 2005? I thought I read about sys.sysperfinfo allowing backward compatability but I have not SQL 2005 server to check it on.Also, every resource I've checked seems to reference sp_monitor while on my server it is spt_monitor. Why is this? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
nscott
Starting Member
2 Posts |
Posted - 2011-07-28 : 18:03:19
|
| Brilliant! Thank you so much for this info. I had gone to see what the price to buy 2008 was but hadn't even bothered to see if there was a free edition! Thats incredibly helpful.Checking the EOL on 2000 and 2005 even! Are there still a considerable amount of people using SQL 2000, enough to consider backwards compatiblity? |
 |
|
|
|
|
|
sysperfinfo and spt_monitor in SQL 2005 and 2008