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

Losing Data Expand / Collapse
Author
Message
Posted Sunday, June 16, 2013 9:33 PM


SSC-Dedicated

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

Group: Administrators
Last Login: Yesterday @ 4:10 PM
Points: 33,095, Visits: 15,202
Comments posted to this topic are about the item Losing Data






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1463980
Posted Monday, June 17, 2013 1:03 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 @ 2:18 AM
Points: 559, Visits: 1,159
This is why I love the Ola Hallengren backup solution - set it for all user databases and you know that anything developers create will get backed up even if you're on holiday.
Post #1464005
Posted Monday, June 17, 2013 2:09 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Wednesday, July 2, 2014 1:09 AM
Points: 834, Visits: 329
You have no backup until you have proven that the restore works.
Post #1464022
Posted Monday, June 17, 2013 8:05 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:48 AM
Points: 5,204, Visits: 2,835
You could even add the creation of the self-invite to a meeting to the script.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1464159
Posted Monday, June 17, 2013 8:07 AM


SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Yesterday @ 9:39 AM
Points: 156, Visits: 458
I agree completely, we should have not excuses to "forget" backing up a database. I have to admit, I have done that exact same thing in the past and we get busy and plan to get it done "tomorrow" and tomorrow gets here and we're busy with others tasks. It is difficult to keep an eye on everything. We are using virtual machines and our network guy has scheduled some snapshots of our system and at least once a day it runs throught each database and makes a backup. In addition to that, I also have scheduled backup scripts. It may sound too redundant but we have the means and we would hate to loose any data. I think we have a good balance. Team work it's important, it's true that DBAs are responsible for db backups but it doesn't hurt to have another team member watching your back too.

Post #1464160
Posted Monday, June 17, 2013 4:21 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 2:45 PM
Points: 2,267, Visits: 1,324
Excellent on all points, backup and test the backup. And monitor that it keeps happening. Check after events happen like scheduled down time, new hardware installations etc. Assume nothing and secure everything you can. And in reality a little healthy paranoia can be helpful here.




Not all gray hairs are Dinosaurs!
Post #1464423
Posted Monday, June 17, 2013 5:55 PM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 6:23 AM
Points: 617, Visits: 2,070
Miles Neale (6/17/2013)
... And monitor that it keeps happening. ....



The script I use to create the backup plan also includes steps to setup the e-mail system and attach notification to the backup job(s).

It never hurts to have that come in.




----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
Post #1464431
Posted Tuesday, June 18, 2013 1:24 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 1:17 PM
Points: 65, Visits: 413
One other reason to setup back-ups immediately and (performance) monitoring as soon as possible has to do with another phenomena: When a new version is released under time pressure, things are more likely to go wrong or cause trouble because testing in a production-like environment is usualy very time consuming.

Even without any problematic changes in the database itself, changes are bigger that a piece of newly developed or sligtly adjusted code will have a dramatic impact on query performance, cause deadlocks or corrupts the data in ways that could have been avoided with proper constraints if there had have been more time to implement and test them thoroughly.

One last additional advice: NEVER forget to back-up the database BEFORE you deploy a new version of the software. No matter how much you are in a hurry, you will always regret it when you can not restore the previous version. Too often it is needed when something goes wrong, just to make a side-by-side comparison, or to rerun the upgrade scripts when it gets stuck because some 'small' changes were made by hand in the test environment.

See you at the next upgrade!
Post #1464481
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse