May 6, 2015 at 11:31 am
Hi
I have a production SQL Server 2005. The last few Saturdays at different times of the day, applications were not able to connect to their databases. I would like to trouble shoot this problem with a scheduled Profiler job. I would like to capture cpu usage, disk i/o, what is running, number of connections. Any other suggestions?
Thanks
Kathy
May 6, 2015 at 12:08 pm
Those are good starting points, but if you're willing to work saturdays can you get someone to call you when an application is actually experiencing a problem?
May 6, 2015 at 12:21 pm
I was able to get myself added to the application as a sysadmin so that if a connection couldn't be made then I'd get an email. So I will have that possibility of getting notified. The reason I was going to have a profiler job ready was because there are other applications that have connection problems and I don't get notified if there is a problem. I have a dedicated admin setup so I can access the db engine and I have some scripts ready to run if I do get notified.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply