SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


A DBA at the Opera


A DBA at the Opera

Author
Message
Louis Davidson (@drsql)
Louis Davidson (@drsql)
SSC Veteran
SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)

Group: General Forum Members
Points: 263 Visits: 109
Comments posted to this topic are about the item A DBA at the Opera



Gary Varga
Gary Varga
SSC-Insane
SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)

Group: General Forum Members
Points: 20029 Visits: 6534
What is the old saying? "A stitch in time saves nine!!!"

There is no reason for computing to be any different to anything else. I cannot remember the number of times when I have said "I don't have to do it yet but I'll start in now and get it out of the way" only to find that my personal deadline has come and gone because of one issue or another.

I guess that no matter how much effort we put in to avoid the drama it will come anyway. However, as professionals we should be ensure that any drama remains that and doesn't end up being a crisis.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
SQLRNNR
SQLRNNR
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41361 Visits: 18565
Gary Varga (8/4/2014)
What is the old saying? "A stitch in time saves nine!!!"

There is no reason for computing to be any different to anything else. I cannot remember the number of times when I have said "I don't have to do it yet but I'll start in now and get it out of the way" only to find that my personal deadline has come and gone because of one issue or another.

I guess that no matter how much effort we put in to avoid the drama it will come anyway. However, as professionals we should be ensure that any drama remains that and doesn't end up being a crisis.


Here Here!!

+1



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Andrew Kernodle
Andrew Kernodle
SSC Eights!
SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)

Group: General Forum Members
Points: 918 Visits: 8135
Oh geez. I feel quite operatic in the sense of this article lately :-P

The sysadmin here decided a few weeks back that the CPU usage of the SQL Server was just too high after midnight, which just so happens to be the time when things like full backups, DBCC checks, statistics updates, and index rebuilds are done. Without informing he, he started restarting the server at around 1:00 A.M., right in the middle of all the maintenance work.

Today, he calls me and tells me about the problems, and says the maintenance stuff is making the CPU too high. I question why that's a problem, since everyone's off-premises, and the jobs finish by 7:00 A.M., and work for the day starts at 9:30 A.M. Plenty of leeway. "Well, the CPU is just too high! It's bad for the server!" Alright, well, the CPU will come down eventually, especially if you stop restarting the server every day, which forces recompilation on everything- "No! That's not it! There must be something on the SQL side of things messing it all up!" Well, technically, yes, if there wasn't interference with the processes meant to control that, and also, we don't have backups anymore since they haven't been allowed to run- "It's better this way!" ... *Sigh*.

I'm not looking forward to the final act, which will probably involve corruption and a few dead databases Hehe

- :-D
SQLRNNR
SQLRNNR
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41361 Visits: 18565
Andrew Kernodle (8/4/2014)
Oh geez. I feel quite operatic in the sense of this article lately :-P

The sysadmin here decided a few weeks back that the CPU usage of the SQL Server was just too high after midnight, which just so happens to be the time when things like full backups, DBCC checks, statistics updates, and index rebuilds are done. Without informing he, he started restarting the server at around 1:00 A.M., right in the middle of all the maintenance work.

Today, he calls me and tells me about the problems, and says the maintenance stuff is making the CPU too high. I question why that's a problem, since everyone's off-premises, and the jobs finish by 7:00 A.M., and work for the day starts at 9:30 A.M. Plenty of leeway. "Well, the CPU is just too high! It's bad for the server!" Alright, well, the CPU will come down eventually, especially if you stop restarting the server every day, which forces recompilation on everything- "No! That's not it! There must be something on the SQL side of things messing it all up!" Well, technically, yes, if there wasn't interference with the processes meant to control that, and also, we don't have backups anymore since they haven't been allowed to run- "It's better this way!" ... *Sigh*.

I'm not looking forward to the final act, which will probably involve corruption and a few dead databases Hehe


ROFLMAO

Amazing how stubborn sysadmins can get sometimes when they don't understand.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Gary Varga
Gary Varga
SSC-Insane
SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)

Group: General Forum Members
Points: 20029 Visits: 6534
Andrew Kernodle (8/4/2014)
Oh geez. I feel quite operatic in the sense of this article lately :-P

The sysadmin here decided a few weeks back that the CPU usage of the SQL Server was just too high after midnight, which just so happens to be the time when things like full backups, DBCC checks, statistics updates, and index rebuilds are done. Without informing he, he started restarting the server at around 1:00 A.M., right in the middle of all the maintenance work.

Today, he calls me and tells me about the problems, and says the maintenance stuff is making the CPU too high. I question why that's a problem, since everyone's off-premises, and the jobs finish by 7:00 A.M., and work for the day starts at 9:30 A.M. Plenty of leeway. "Well, the CPU is just too high! It's bad for the server!" Alright, well, the CPU will come down eventually, especially if you stop restarting the server every day, which forces recompilation on everything- "No! That's not it! There must be something on the SQL side of things messing it all up!" Well, technically, yes, if there wasn't interference with the processes meant to control that, and also, we don't have backups anymore since they haven't been allowed to run- "It's better this way!" ... *Sigh*.

I'm not looking forward to the final act, which will probably involve corruption and a few dead databases Hehe


Are you in a Jim Henson Production??? :-P

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Andrew Kernodle
Andrew Kernodle
SSC Eights!
SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)SSC Eights! (918 reputation)

Group: General Forum Members
Points: 918 Visits: 8135
... You know, now that I think about it... :-P

But eh, frustrating though it may be, I'll just have to get some climbing gear out and start scaling the cliff wall of management. Provided nothing too nonsensical happens, I should be able to get everything sorted out. Still, it's a little unnerving that a problem like this can just dive-bomb onto me when I thought I had everything on the server running quite well Crazy

- :-D
SQLRNNR
SQLRNNR
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41361 Visits: 18565
Andrew Kernodle (8/4/2014)
... You know, now that I think about it... :-P

But eh, frustrating though it may be, I'll just have to get some climbing gear out and start scaling the cliff wall of management. Provided nothing too nonsensical happens, I should be able to get everything sorted out. Still, it's a little unnerving that a problem like this can just dive-bomb onto me when I thought I had everything on the server running quite well Crazy


That's the beauty of IT. We can implement process to control most events that are computer related. Sadly we can't account for all of the possible stupid things other humans will do that will undo everything we have tried to accomplish.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Louis Davidson (@drsql)
Louis Davidson (@drsql)
SSC Veteran
SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)

Group: General Forum Members
Points: 263 Visits: 109
Wow. I couldn't make up a story so excellent as that one.

Louis



Gary Varga
Gary Varga
SSC-Insane
SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)

Group: General Forum Members
Points: 20029 Visits: 6534
...and for once it is not a "Stupid Developer" tale!!!

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search