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 «««1234

Backup and Housekeeping with Maintenance Plans Expand / Collapse
Author
Message
Posted Thursday, January 27, 2011 2:26 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, October 17, 2014 7:12 AM
Points: 1,030, Visits: 2,796
bcb (1/27/2011)
Well everybody, I'm pleased my comment about starting a db maintenance job with DBCC Checkdb inspired such discussion. Just to add some clarification... I have all of my sql agent jobs set to email me if a job fails. An interesting feature of SQL Server is that if a sql agent job has a checkdb step, and the step completes successfully but checkdb discovers corruption, SQL will still quit the job at that point with failure, and I get my email notification. :) (Now, I assume that is still true... I'm not sure because the last time I had db corruption was ten years ago, I believe in SQL 7.0.) Anyhow, hope that clarifies.
As an aside...I kinda chuckle when SQLServerCentral calls me grasshopper just because I hardly ever comment on articles. I've been a dba for 17 years.


BCB thanks for the clarification, that name gets given to you based on the number of posts you make, and number of QODs you get right, not on how long you have been 'doing the job'. Thanks for your contribution and the points you made, they are very informative.


Gethyn Ellis

gethynellis.com
Post #1054943
Posted Thursday, January 27, 2011 3:04 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, September 8, 2014 4:10 PM
Points: 21, Visits: 103
Thanks, Gethyn. :)


Post #1054967
Posted Monday, February 17, 2014 8:10 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 8:11 AM
Points: 138, Visits: 438
My only comment, and concern is the clean up of the history on msdb. I would prefer to keep 8 weeks of data in the history, as that can give a good trending on how long the backups take and any other maintenance jobs for that matter. Also by keeping the 8 weeks, I can extract a report on database growth for right sizing of the system and trending.
Post #1542144
Posted Monday, February 17, 2014 1:29 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 8:29 PM
Points: 18, Visits: 86
I would advise caution when putting your cleanup task before the backup task, I have seen this result in the tape backup running between the time of cleanup and database backup with the result of nothing being backed up to tape for offsite storage.

If you are lucky enough to have a fast server with SQL backup compression it always nice to have the SQL backup complete by the time the tape backup kicks off!
Post #1542267
Posted Monday, February 17, 2014 6:16 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:09 AM
Points: 35,348, Visits: 31,886
I have to agree with the others. This would have been an absolute "must read" article, especially for newbies, if emails were sent out on the failure of any node and if it were also demonstrated as to just how easy it is to setup Point-In-Time logfile backups as well.

Still, this is a great introductory article the clearly demonstrates that it doesn't take a rocket scientist to create scheduled backups and that there's absolutely no execuse to not have full backups.

Thank you very much for taking the time to write this article.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1542323
« Prev Topic | Next Topic »

Add to briefcase «««1234

Permissions Expand / Collapse