SQL Backup

Latest version: 7.2

SQL Backup

Knowledge Base

SQL Backup Reporting fails after upgrading to Version 6 from Version 5 for Multiple

Category: Troubleshooting & error messages
Date: 18 Sep 2009
Product: SQL Backup
To use reporting feature for Multiple Servers in SQL Backup V5, a Reports Database is required to collate the data from the SQL Server instances that you choose to report on.

Upon upgrading to SQL Backup V6, the report generation may fail with the following errors:

Insert Error: Column name or number of supplied values does not match table definition.
Insert Error: Column name or number of supplied values does not match table definition.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Backuplog_BackupHistory". The conflict occurred in database "SQLBackupReportingDatabase", "dbo.backuphistory".
Insert Error: Column name or number of supplied values does not match table definition.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Restorelog_RestoreHistory". The conflict occurred in database "SQLBackupReportingDatabase", "dbo.restorehistory".
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Restorelog_RestoreHistory". The conflict occurred in database "SQLBackupReportingDatabase", "dbo.restorehistory".
The statement has been terminated.
The statement has been terminated.
The statement has been terminated.

Delete the existing SQL Backup V5 Reporting Database.

Create a new SQL Backup V6 Reporting Database via the SQL Backup GUI ->Tools menu ->Reporting.

Further advice on configuring and using the reporting feature can be found in the SQL Backup Help file, using this link:

<http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Backup&c=SQL_Backup/help/6.2/SBU_Reporting.htm&toc=SQL_Backup/help/6.2/toc847165.htm>

Document ID: KB200909000422 Keywords: SQL, Backup,reporting,upgrade

Was this article helpful?

Search support
Forums
Visit the SQL Backup forum.

SQL Backup

all SQL products

all products