SQL Backup Extended Stored Proc Is Truncating database name

ryanchaz · January 23, 2011 11:06AM

Trying to backup one of our Sharepoint TLOGS, and it's a goofy system-generated name, which can't be changed. When I call the sqlbackup xp with this set of parameters, it returns the following results, clearly showing that it doesn't know how to deal with this name:

Parameters:
-SQL "BACKUP LOG SharePoint_AdminContent_ee6e586c-90de-45f0-9e3d-20bf30104edf TO DISK = 'D:\MSSQL.1\MSSQL\Backup\<AUTO>.sqb' WITH COMPRESSION = 3, ERASEFILES = 4, VERIFY"

Result:
Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database 'SharePoint_AdminContent_ee6e586c'. No entry found with that name. Make sure that the name is entered correctly.

The database DOES exist in the sysdatabases, but under the full database name.

Is there a way to deal with this, or a workaround?

Many thanks in advance for any input.

Chuck

ryanchaz · January 23, 2011 11:13AM

Oh, and one more thing -- when I use the syntax that includes brackets around the database name, it does the same thing.

petey · January 23, 2011 8:05PM

I could not reproduce the error using SQL Backup 6.4. Which version of SQL Backup are you using?

Thanks.

ryanchaz · January 24, 2011 10:29AM

We're actually on version 5.4.0.55

petey · January 24, 2011 7:53PM

I could not reproduce the error using version 5.4.0.55 either.

Could you please use Profiler to identify the SQL command used by the SQL Backup Agent (executable name is SQBCoreService.exe) that is causing the error?

Thanks.

ryanchaz · January 29, 2011 6:11PM

My apologies -- it turns out that this issue was happening later in the stored procedure, but appeared to be caused by the SQL Backup call in the log results. It appears we are now working correctly.

SQL Backup Extended Stored Proc Is Truncating database name

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk