February 21, 2008 at 8:49 am
Hello,
I work for a software company that creates applications that use SQL server for the backend. We have been in business for over a decade but only on SQL for ~3 years (we used MS access before ) I work in the support department and we have created a new position as of Jan 1 of this year. The position is Tech-Support DBA. Yah thats me! Just a little background on myself so you will have an approximation of what i know and what i don't know (or what i should know lol), I've been a MCDBA for about 3 years and have been working with SQL for the same amount of time. I also have MCSE and MCSA on 2000 and 2003.
Part of my new job, and the part I am writing about here, is to build a relationship with our client DBA's and identify issues they are having. Obviously short of saying "Hey what are your problems with our DB's" (which i certainly will ask) I want to have a performance monitoring plan setup. I have monitored many SQL servers individually and independently using perfmon and profiler but i want to setup something that is easily redistributable to many different clients and many sql servers that I have ZERO control over directly. Meaning I will need to hand the client DBA a package of sorts and say install this and send me the results. Server names and instances will be different for each client, permissions (logins, windows accounts) will be different per client.
Does anybody here work in a similar environment? I've written a few inno installers that distributed counter log settings in the past for non sql related performance issues. The first thing that comes to mind is since the instance name will be different for each sql server I will have to modify the counter log settings file to point to the correct instance name. I have never distributed profiler templates (other than manually).
If anybody has any words of wisdom or experience with the above that they wish to share please do so.
Jimmy
"I'm still learning the things i thought i knew!"February 21, 2008 at 9:30 am
I've never done this with perfmon, so I'll leave that to the experts.
Profiler is silly simple. You can create a stored proc that does everything you need. You can even generate the proc directly from Profiler. The only modification you'd have to make is providing a parameter for the path since, as you say, every environment it is going to be different. You can distribute it very simply then and collect the data from the client.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy