|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Monday, March 18, 2013 7:54 AM
Points: 27,
Visits: 421
|
|
[b]I still do not comprehend a lot of the disk mirror/replication Using software like doubletake, you can replicate (copy) disk array at data-block level to another environment and keep them in synch. Only the changed data-blocks will be copied.
Jason http://dbace.us
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: 2 days ago @ 10:14 PM
Points: 1,727,
Visits: 1,044
|
|
...we created a test system that took a known database, corrupted it randomly..
How do you manually corrupt the database?
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: 2 days ago @ 10:19 AM
Points: 1,910,
Visits: 1,606
|
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: 2 days ago @ 10:29 PM
Points: 2,178,
Visits: 3,599
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, March 25, 2013 4:45 PM
Points: 5,
Visits: 46
|
|
| Thanks Paul. You are extremely gracious with your time on these matters. You helped me a few years ago on a discussion board covering this very topic. We used the REPAIR_ALLOW_DATA_LOSS on a db with more torn pages than an eighth grade math book (ok, not that many). We recovered and restored an old copy of the db as you've suggested here to determine the problem data was outdated. Thanks again.
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Today @ 8:09 AM
Points: 568,
Visits: 3,063
|
|
Will a job with the following fail if corruption exists? Or will the job succeed?
DBCC CHECKDB(N'master') WITH NO_INFOMSGS
I'm suddenly feeling a bit exposed since I am not sure if I would get notified if corruption exists.
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 10:51 AM
Points: 1,562,
Visits: 1,932
|
|
Chrissy321 (6/25/2012) Will a job with the following fail if corruption exists? Or will the job succeed?
DBCC CHECKDB(N'master') WITH NO_INFOMSGS
The job would fail and report at least some of the errors it encountered. To see all errors you need to use "WITH ALL_ERRORMSGS". That can be combined with NO_INFOMSGS.
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: 2 days ago @ 10:19 AM
Points: 1,910,
Visits: 1,606
|
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: 2 days ago @ 10:19 AM
Points: 1,910,
Visits: 1,606
|
|
Be careful though because SQL Agent will only capture the first X bytes of the output (unless that changed in recent versions). You may want to go the route of using the undocumented WITH TABLERESULTS and storing the output in a table for later perusal. See here for an example.
Paul Randal CEO, SQLskills.com: Check out SQLskills online training! Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Today @ 8:09 AM
Points: 568,
Visits: 3,063
|
|
Thanks Paul I will definitely explore that option. I have a monitoring system for failed jobs so it sounds like I would at least be notied that something is amiss. Seems like a good example of maintenance plans being not quite as robust as built or borrowed maintenance scripting.
|
|
|
|