torquemonster
MIS
Let me preface this by stating that I am in NO way a DBA/SQL expert, nor do I play one on TV... I do networking, & work with SQL server just enough to hopefully keep it running until the knowledgeable folk show up.
At a VIP's request, I went to apply SP3 in order to address the issues raised by the Slammer worm. (No, our SQL server isn't connected to the 'net, but I do what I'm told...) Like a fool, I just downloaded the patch, ran the exe, & verified that it didn't produce any errors, & went on to the next project on my list. (I'll freely admit that I should have read the directions first, but I'm accustomed to the "Windows Update" style of patching, & it bit me this time. Lesson learned.)
Sometime thereafter, we had to restart the server (can't remember why right now, but it was nothing very alarming), & I started getting calls from users that told me that they couldn't access the SQL-dependent apps. I investigate, discover that the SQL Server service hadn't started, despite being configured to start automatically. When I try to start it, it consistently fails without logging any errors.
I've tried using both Windows authentication & SQL Server authentication, & it doesn't seem to make any difference. As a last resort, I've started the sqlserver.exe program as an application (rather than as a service) which allows the users to get things done, but it seems like a horrible kludge to me.
Any constructive feedback would be appreciated.
T.
At a VIP's request, I went to apply SP3 in order to address the issues raised by the Slammer worm. (No, our SQL server isn't connected to the 'net, but I do what I'm told...) Like a fool, I just downloaded the patch, ran the exe, & verified that it didn't produce any errors, & went on to the next project on my list. (I'll freely admit that I should have read the directions first, but I'm accustomed to the "Windows Update" style of patching, & it bit me this time. Lesson learned.)
Sometime thereafter, we had to restart the server (can't remember why right now, but it was nothing very alarming), & I started getting calls from users that told me that they couldn't access the SQL-dependent apps. I investigate, discover that the SQL Server service hadn't started, despite being configured to start automatically. When I try to start it, it consistently fails without logging any errors.
I've tried using both Windows authentication & SQL Server authentication, & it doesn't seem to make any difference. As a last resort, I've started the sqlserver.exe program as an application (rather than as a service) which allows the users to get things done, but it seems like a horrible kludge to me.
Any constructive feedback would be appreciated.
T.
