Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

A DBA at the Opera Expand / Collapse
Author
Message
Posted Saturday, August 2, 2014 1:52 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Yesterday @ 4:49 PM
Points: 74, Visits: 86
Comments posted to this topic are about the item A DBA at the Opera


Post #1598856
Posted Monday, August 4, 2014 2:31 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:16 AM
Points: 5,740, Visits: 3,662
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!!!
Post #1599154
Posted Monday, August 4, 2014 8:47 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 12:45 PM
Points: 17,947, Visits: 15,941
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
Post #1599287
Posted Monday, August 4, 2014 8:56 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 3:25 PM
Points: 592, Visits: 7,022
Oh geez. I feel quite operatic in the sense of this article lately

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




-
Post #1599292
Posted Monday, August 4, 2014 9:02 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 12:45 PM
Points: 17,947, Visits: 15,941
Andrew Kernodle (8/4/2014)
Oh geez. I feel quite operatic in the sense of this article lately

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


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
Post #1599294
Posted Monday, August 4, 2014 9:11 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:16 AM
Points: 5,740, Visits: 3,662
Andrew Kernodle (8/4/2014)
Oh geez. I feel quite operatic in the sense of this article lately

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


Are you in a Jim Henson Production???


Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1599301
Posted Monday, August 4, 2014 9:13 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 3:25 PM
Points: 592, Visits: 7,022
... You know, now that I think about it...

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




-
Post #1599302
Posted Monday, August 4, 2014 9:20 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 12:45 PM
Points: 17,947, Visits: 15,941
Andrew Kernodle (8/4/2014)
... You know, now that I think about it...

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


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
Post #1599305
Posted Monday, August 4, 2014 9:27 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Yesterday @ 4:49 PM
Points: 74, Visits: 86
Wow. I couldn't make up a story so excellent as that one.

Louis



Post #1599308
Posted Monday, August 4, 2014 9:29 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:16 AM
Points: 5,740, Visits: 3,662
...and for once it is not a "Stupid Developer" tale!!!

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1599309
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse