Backup Monitoring and Reporting

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by Chad Miller » Backup Monitoring and Reporting

31 posts, Page 1 of 4

1 2 3 4 »»»

Backup Monitoring and Reporting

Rate Topic

Display Mode

Topic Options

Author

Message

cmille19

Posted Wednesday, June 03, 2009 11:33 AM

SSC Veteran

Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:46 AM
Points: 257, Visits: 671

Comments posted to this topic are about the item Backup Monitoring and Reporting

Post #728403

Ted Krueger

Posted Thursday, June 04, 2009 8:09 AM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, May 21, 2013 10:34 AM
Points: 47, Visits: 747

Very nice! I would optimize some things in the coding for large installations with hundreds of backups going on every hour (logs etc..) though. Example would be to the exclusion table and the "AND d.name NOT IN (SELECT db_name FROM dbautility.dbo.db_exclude)". Could be replaced with a JOIN logic and get the NOT out of there.

All in all I enjoyed reading it and I can see this benefiting quite a few DBAs out there. Thanks!

Post #728978

Paul Randal

Posted Thursday, June 04, 2009 10:19 AM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905, Visits: 1,601

Chad - excellent. I'll be adding a link to this in all my DBA classes.

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

Post #729110

Rui Nogueira

Posted Thursday, June 04, 2009 10:33 AM

Old Hand

Group: General Forum Members
Last Login: Wednesday, March 06, 2013 8:29 AM
Points: 351, Visits: 175

Good article, Backup Monitoring and Reporting

There is a mistake in it:

msdb.baclkupset -> msdb.backupset

Thank You

http://www.arcns.no.sapo.pt

Post #729130

Dugi

Posted Friday, June 05, 2009 1:03 AM

Ten Centuries

Group: General Forum Members
Last Login: Tuesday, April 02, 2013 1:48 AM
Points: 1,252, Visits: 3,367

Yea, very nice article! It is in my briefcase now! Thank you for sharing! Wink

============================================================
SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
http://www.sqlservercentral.com/articles/Best+Practices/61537/

Post #729445

sanderstad

Posted Friday, June 05, 2009 1:48 AM

Old Hand

Group: General Forum Members
Last Login: Tuesday, May 21, 2013 3:19 AM
Points: 382, Visits: 487

When I get execute the jobs I get the following error by starting the powershell script:

Exception calling "WriteToServer" with "1" argument(s): "Violation of PRIMARY K  EY constraint 'PK_backupset_dim'. Cannot insert duplicate key in object 'dbo.ba  ckupset_dim'.  The statement has been terminated."  At D:\CustomReports\backupAnalysis.ps1:59 char:28  +     $bulkCopy.WriteToServer( <<<< $dataTable)Exception calling "WriteToServer" with "1" argument(s): "Violation of PRIMARY K  EY constraint 'PK_backupset_dim'. Cannot insert duplicate key in object 'dbo.ba  ckupset_dim'.  The statement has been terminated."  At D:\CustomReports\backupAnalysis.ps1:59 char:28  +     $bulkCopy.WriteToServer( <<<< $dataTable).  Process Exit Code 0.  The step succeeded.

Post #729458

cmille19

Posted Friday, June 05, 2009 5:17 AM

SSC Veteran

Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:46 AM
Points: 257, Visits: 671

sanderstad (6/5/2009)

When I get execute the jobs I get the following error by starting the powershell script:

Exception calling "WriteToServer" with "1" argument(s): "Violation of PRIMARY K  EY constraint 'PK_backupset_dim'. Cannot insert duplicate key in object 'dbo.ba  ckupset_dim'.  The statement has been terminated."  At D:\CustomReports\backupAnalysis.ps1:59 char:28  +     $bulkCopy.WriteToServer( <<<< $dataTable)Exception calling "WriteToServer" with "1" argument(s): "Violation of PRIMARY K  EY constraint 'PK_backupset_dim'. Cannot insert duplicate key in object 'dbo.ba  ckupset_dim'.  The statement has been terminated."  At D:\CustomReports\backupAnalysis.ps1:59 char:28  +     $bulkCopy.WriteToServer( <<<< $dataTable).  Process Exit Code 0.  The step succeeded.

Try running update_server_dim_sp this wil update the server_dim.max_backupset_id column. Also keep in mind the primary key is defined as server_name and backup_set_id. The server name value is obtained from @@servername, so its possible to have duplicate names of your SQL Servers in your environment. Check @@servername on all servers you are polling and verify there are no duplicates.

Post #729578

cmille19

Posted Friday, June 05, 2009 5:28 AM

SSC Veteran

Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:46 AM
Points: 257, Visits: 671

Rui Nogueira (6/4/2009)

Good article, Backup Monitoring and Reporting

There is a mistake in it:

msdb.baclkupset -> msdb.backupset

Thank You

Thanks -- I made a few spelling and grammar corrections, it might take a few days to show up.

Post #729593

jackie.jones

Posted Friday, September 04, 2009 2:53 AM

Valued Member

Group: General Forum Members
Last Login: Friday, July 09, 2010 4:10 AM
Points: 70, Visits: 117

Really really helpful and well written - thank you very much.

Post #782775

BJCharly

Posted Tuesday, September 08, 2009 10:37 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, September 12, 2011 1:21 PM
Points: 3, Visits: 83

Nice article, thanks

Post #784393

« Prev Topic | Next Topic »

31 posts, Page 1 of 4

1 2 3 4 »»»

Permissions