Request for health check Script

Question

Request for health check Script

SQL Galaxy

One Orange Chip

Points: 29472
More actions
October 8, 2010 at 4:09 am

#97514

Hi,
Please give me a scirpt for SQL server 2000 health check report.
Thanks in advance
ananda

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Please be more specific as to what you want. What do you mean by 'health check'?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 2

Hi,

I am not comfortable as SQLDBA just new SQLDBA. As per my experience, I had understand and configured day to day activity in production SQL server as below

1.Verify database backup status

2.Monitoring data file size (MDF,NDF and LDF)

3.Verify SQL Jobs

4.Checking database free space

5.Verify SQL Error logs, windows event log,

Apart from those points, what should be monitoring in SQLSERVER day to day? I don’t have idea about SQL server database health checking, please suggestion me.

Thanks

ananda

Steve Jones - SSC Editor SSC Guru Points: 736642 More actions · Answer 3

You can look up scripts for each of these items. There isn't a comprehensive script I'm aware of that will do all of these.

You shouldn't have to monitor SQL Server on a daily basis. The server should just run for the most part. If jobs work, then things should be fine.

Data space you should pre-allocate to a level that allows you to leave the files alone for 3-4 months if not longer. When space gets low, you should add it in large chunks. Log space varies depending on the activity. The space you need depends on how often you do log backups and the only way to determine this is monitor the log backup size and make sure the log is large enough.

For logs, you should be scanning for errors, not warnings. There are scripts that can help you scan through these, or software available to notify you when something occurs.