Lynn Pettis (4/6/2012)
TravisDBA (4/6/2012)
We strictly handle SQL Server support. No Access, no applications, just SQL Server. We have well over 100 instances of SQL Server to administrate spread throughout the state of Iowa.
I totally agree with most of what you say. However, the problem is with that, is the people reporting the issue(error), as well as HelpDesk personnel on duty many times cannot always determine if the issue is database related, network related, or application(even Access) related. In many companies the Help Desk department has a constant turnover of people, so seasoned individuals that have the experience to detect the difference have often moved on or left. So, as a result, many times a DBA will get called for a wild goose chase anyway. Fortunately, in my company the Help desk people have been around for awhile and can usually ferret this out before the call is made. 😀
My experience has been it is ALWAYS a database issue until proven otherwise beyond any reasonable doubt.
I agree. I don't want to give the impression that we only receive pages or calls about SQL Server. But we are third level support; a problem has to pass through two other levels before we are paged. :doze:
Usually the service desk does what they can to help. If necessary it gets passed along to the application analyst on call who is responsible for the specific application. If the application analyst runs into problem then they contact our layer and the analyst are pretty good at notifying the teams that they think would be the most likely to help such as networking, server, application or client device people. :cool:;-) :hehe:
Our service center does a pretty good job of working out who to contact for a problem, which for SQL Server issues is about 95%+ of the time. The other 5% we scratch our head and wonder why it was sent to us.:crazy:
-----------------
Larry
(What color is your database?)