Comments
Sort by recent activity
I also found a red-gate log file in the sqlserver log directory from the maintenance plan running at 4:00am Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.1399
Report was generated on "DBSERVER3".
Maintenance Plan: Red-Gate Full Daily Backup
Duration: 00:00:07
Status: Succeeded.
Details:
Everything seems to think that is completes ok, but the return value is not being loved by sqlagent, or sql mgmt studio / comments
I also found a red-gate log file in the sqlserver log directory from the maintenance plan running at 4:00amMicrosoft(R) Server Maintenance Utility (Unicode) Version 9.0.1399
Report ...
I logged into a SQLServer 2000 machine, and used the old Query Analyzer to run the same Command that fails when running from the new SQL mgmt studio.
So, since the database is the same, 2005 standard, the only thing this test changes is the program, Query Analyzer, and how the old program actually makes a connection to the database.
Ok, strange, the results look the same (they seem to get cut off), but NO ERROR code is returned... Output from SQL Backup (3.2.0)
--------------------------------------------------------------------------------------------------------------------------------
SQL Backup 3.2.0.5, (c) Red Gate Software Ltd 2004 - 2005
Serial number: xxxxx
Backing up FogBugz (full database) to D:\SQLBackups\FogBugZ\FULL_(local)_FogBugz_20051118 074333.sqb ...
Backup data size : 96.688 MB
Compressed data
no log file is created, and the backup file IS Created.
Not sure if it's failing still, but the old query analyzer is not seeing it or not caring about the return code or ?????? / comments
I logged into a SQLServer 2000 machine, and used the old Query Analyzer to run the same Command that fails when running from the new SQL mgmt studio.
So, since the database is the same, 2005 standa...
Ok,
Updated software, fired up SQLBackup.exe, confirmed 3.2.0.5 from the About Box.
Did a backup from within there, just to make sure everything is still cool there.
Worked fine,
Ok, then I attempted to run the Maintenance Plan from SQL Agent.
That still failed with a generic "The Step Failed"
I then open a query window and executed it from there.
Results.... Output from SQL Backup (3.2.0)
--------------------------------------------------------------------------------------------------------------------------------
SQL Backup 3.2.0.5, (c) Red Gate Software Ltd 2004 - 2005
Serial number: xxxxxx ftware Ltd 2004 - 2005
Backing up FogBugz (full database) to D:\SQLBackups\FogBugZ\FULL_(local)_FogBugz_20051116 110738.sqb ...
Backup data size : 96.688 MB e) to D:\SQLBackups\FogBugZ\FULL_(local)_FogBugz_20051116 110738.sqb ...
Compressed data : 96.688 MB e) to D:\SQLBackups\FogBugZ\FULL_(local)_FogBugz_20051116 110738.sqb ...
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Now, all 3 steps above did create the .sqb files, and they are now ALL the same exact size down to the byte.
Have NOT done a binary comparsion yet, have to upload a utility.
I'm logged in as administrator (thru a remote desktop connection)
It's a Windows Server 2003 Standard SP1 (Single Xeon, 3GB Memory - RAID5 )
It only runs SQLServer, no other software besides OS components.
(does have IIS installed because SQLServer 2005 wants it installed for some of its features)
So, still the same problem / comments
Ok,
Updated software, fired up SQLBackup.exe, confirmed 3.2.0.5 from the About Box.
Did a backup from within there, just to make sure everything is still cool there.
Worked fine,
Ok, then I attempt...