SQL Database backup fails with warning "Failed to create table"


SQL Database backup fails with warning "Failed to create table"


Applies To

SQL Agent backups for database with very long names.

SQL Server 2008, 2008R2, 2005 and 2000

Symptoms / Description

Databases with names over 103 characters may fail to backup with the following messages:

FATAL: No backup data received from client.

Exit Code......: 2

Exit Status....: Misc error

Failed to create table '’, and will not be able validate sql checkpoint for differential and transactional backups for current backup group.



To protect database with very long names using the Unitrends VSS SQL Agent

  • Rename the databases to less than 102 characters
Refer to you application directions for renaming databases (references for SharePoint are provided under Third-Party Sources).  Alternatively, the Unitrends Windows agent can protect the files created using SQL Backup with the Recovery Appliance’s retention, backup archiving and vaulting. 

Third-Party Sources

Renaming Content Databases http://blogs.technet.com/b/wbaer/archive/2008/06/16/renaming-content-databases.aspx

Renaming crazy SharePoint Database Names http://blogs.technet.com/b/seanearp/archive/2009/03/14/renaming-crazy-sharepoint-database-names.aspx


The SQL Agent cannot create checkpoint tracking tables for database with names over 102 characters (Bug 13079).  While not common, long database names are typical of applications that automatically generate databases using GUID’s (such as SharePoint).


For more detailed information on backup failures and performance issues see Unitrends KB 5062 - Backup Failures and Performance Issues.

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section