Activity overview
Latest activity by andy.c
Hi,
I think I found the trigger that causes the SQLite Exception in the SQL Backup GUI. I think it may have something to do with the way that DNS names are handled in the gui or the backup service.
I was entering a CNAME record into the 'SQL Server' text box in the 'Add SQL Server' form in the SQL Backup GUI. This was causing the SQLite exception. When I add the 'A' record for the same instance in the 'SQL Server' text box the SQL Backup GUI accepts the new instance with no problems.
My question is why would adding a CNAME record as the DNS name for some SQL Server instance cause this unhandled exception?
Thanks,
Andy / comments
Hi,
I think I found the trigger that causes the SQLite Exception in the SQL Backup GUI. I think it may have something to do with the way that DNS names are handled in the gui or the backup service....
This exception is generated when ever I add one of our production clustered instances into the SQL Backup client server list.
This is the SQL Server version that the cluster is running:
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Here is the version of SQL Backup that the cluster is running:
5.0.0.2770
The transaction log backups seem to be taking place. Would an exception like this cause any problems with the backups themselves?
Thanks,
Andy / comments
This exception is generated when ever I add one of our production clustered instances into the SQL Backup client server list.
This is the SQL Server version that the cluster is running:
Microsoft S...
SQLiteException
Hi,
When I fired up the SQL Backup client I got this unhandled exception:
SQLBackup v5
The database disk image is malformed
database disk image is malformed
WorkerExecutionException
at RedGate.SQLB...
Thanks for your help on this Bart.
One work-around that you could try if you have any procs with that strange character combination would be this:
1. Disable SQL Prompt
2. Format the SP using SQL Refactor
3. Re-enable SQL Prompt
For the SP created in the script above the character combination was removed and then SQL Prompt was able to process the SP just fine.
It seems however that the production procs that SQL Prompt was having problems with were already run through SQL Refactor but the character combination remained. / comments
Thanks for your help on this Bart.
One work-around that you could try if you have any procs with that strange character combination would be this:
1. Disable SQL Prompt
2. Format the SP using SQL R...
Unhandled exception in SQL Prompt 3.5.0.333
Hi there,
I have been using a licensed version of SQL Prompt 3.5.0.333 for a few days. It is a great tool but I found that SQL Prompt was throwing unhandled exceptions when I was trying to modify a...