SQL Backup job failed with exitcode: 850

• 
  Looking through the error codes it points to SQL Syntax error, not sure how this could be I used the GUI to build the scheduled jobs just like my other cluster and other servers. I can email you the script if needed.

  tstadler February 07, 2006 07:46

  - 0 +
• 
  Well, when using Query Analyser to run the script, I get "Database name length exceeds maximum allowed length : db1,db2,*" (Actual names are longer) The issue is I have 18 Databases and only 14 of them do a transaction backup. Looks like a char length issue with the command in SQL Backup

  tstadler February 07, 2006 07:50

  - 0 +
• 
  Hello,
  
  There is a length limit in SQL Backup, but I believe it's something like 128 characters for the database name. Can you post the backup script? Thanks!

  Brian Donahue February 07, 2006 08:54

  - 0 +
• 
  I really don't want to post my db names here but I can confirm we are past 128 char because the Script that is built for the transaction logs is specifying each db name, exec master..sqlbackup N'-SQL "BACKUP LOGS [1, 3, 3, 4, 5, 6, 7,8,9,10,11,12,13,14] TO DISK = ''G:\SQLBackup\<DATABASE>\<AUTO>'' WITH NAME = ''<AUTO>'', DESCRIPTION = ''<AUTO>'', ERASEFILES = 2, COMPRESSION = 2, THREADS = 1"', @exitcode OUTPUT, @sqlerrorcode OUTPUT
  So I will need to break this down into multiple steps in the job. That will work.
  Thanks

  tstadler February 07, 2006 10:43

  - 0 +
• 
  There's a bug in version 4.0 that prevents the use of long sequences of database names, though it's perfectly valid. Will be fixed in 4.1.

  petey February 07, 2006 11:34

  - 0 +
• 
  128 char limit is pretty restrictive. I get the error on every server. When is the patch for this due?

  rdalton February 07, 2006 14:38

  - 0 +
• 
  We're going to release this by the end of the week. The 128 character limit that I was referring to was for a single database name, which is a somewhat unrelated issue and as far as I know will still exist in 4.1.

  Brian Donahue February 08, 2006 09:46

  - 0 +

Add comment

Please sign in to leave a comment.