I wouldn't take those Criticals too seriously, I set up most of those default numbers in my test environment, so take that for what its worth.
Agreed..However, clients are complaining of performance issues and so in our case it certainly seems to indicate that we have memory issues on that server which currently is operating in a 32 bit environment. I have plans to upgrade to a 64bit VM, double the ram and then I'm going to research and tweak the warning/critical values.
nscott wrote:Also, I'm gonna dive into this plugin tonight, there may be something wrong with the that page splits syntax, and I'd appreciate someone to test out some other updates to it.
Awesome! I'd be happy to test it out and provide feedback.
The --pagesplits works on a SQL Server 2000 server that I just set up for monitoring. Still no luck with SQL Server 2008. I still get "CRITICAL:Unable to access SQL Server." It's not a permissions issue because I am using top clearance for testing. However, it's good news that it works the older 2000 SQL server.
Hey I am still working on that script, but it is interesting, I actually wrote these scripts for a SQL 2000 Server database. I'll have to look into the 2008 way to get that info, thanks for the info.
I wouldn't take those Criticals too seriously, I set up most of those default numbers in my test environment, so take that for what its worth.
I'd be happy to test it out and provide feedback.