Activity overview
Latest activity by mattchandler
Can you help us improve SQL Toolbelt for teams?
Hi Everyone,
I'm a developer on the Spiders dev team at Redgate. We're responsible for SQL Compare, and at the moment we are also researching how SQL Toolbelt tools such as SQL Compare, SQL Source...
Hi Andrew,
As you found, I'm afraid we don't support the SQL Backup pre-release server components in the released SQL Backup 6 GUI. This is because of a change in the schema of our internal data store.
Sorry for the inconvenience, / comments
Hi Andrew,
As you found, I'm afraid we don't support the SQL Backup pre-release server components in the released SQL Backup 6 GUI. This is because of a change in the schema of our internal data s...
Hi Andrew,
A bug that's come up with the pre-release is that backup can fail when you delete all but the last 'x backups', but there are encrypted 5.4 (or earlier) backups where you're backing up to. If you're backing up multiple databases the same issue can lead to SQL Backup hanging.
I suspect this is what's happening here - if you could try removing older backups files from the folder, I'd be interested to hear if the job starts working.
The fix for this particular bug is already implemented in our internal builds, and this shouldn't affect the final 6.0 release.
Thanks for getting in touch, / comments
Hi Andrew,
A bug that's come up with the pre-release is that backup can fail when you delete all but the last 'x backups', but there are encrypted 5.4 (or earlier) backups where you're backing up t...
FullLogging should be all one word (unlike what I wrote earlier - sorry!)
Hopefully that really should work now! Thank you for your patience. / comments
FullLogging should be all one word (unlike what I wrote earlier - sorry!)
Hopefully that really should work now! Thank you for your patience.
Hi Andrew,
That ought to work, although I should have mentioned that if you're using an x64 machine, the registry should be at:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Red Gate\SQL BackupThe log files should be in:
"C:\Documents and Settings\[your username here]\Local Settings\Application Data\Red Gate\logs\SQL Backup\"
It ought to be obvious whether the registry key is effective - the log files will grow significantly larger (without the setting we will log very little).
I hope that helps, sorry I wasn't clearer the first time. Thanks for all your help. / comments
Hi Andrew,
That ought to work, although I should have mentioned that if you're using an x64 machine, the registry should be at:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Red Gate\SQL BackupThe log fi...
I should mention that you are still able to restore the backup, by selecting the file directly, using the folder browser. / comments
I should mention that you are still able to restore the backup, by selecting the file directly, using the folder browser.
Hi Andrew,
Thanks for raising this. This is an issue that we've seen before. Our UI developer hoped he had fixed it in this release, but obviously its still live.
A workaround for this problem should be to delete the UI data cache - first you will need to close the GUI, and then delete all the files (should be called 1.dat, 2.dat, etc) in the application data. This will probably be found at:
"C:\Documents and Settings\[your username here]\Local Settings\Application Data\Red Gate\SQL Backup\Server Data"
or at: "c:\users\[your username here]\Appdata\Local\Red Gate\SQL Backup\Server Data\", on a Vista machine.
I'd be grateful if you could let us know the details of when this happened. What OS were you using and which version of SQL Serve?. Were you in the middle of doing anything before this issue manifested itself? Any information would be useful.
There is a registry key that will enable verbose logging in the UI. If possible it would be great if you could: Set the registry key "HKEY_LOCAL_MACHINE\Software\Red Gate\SQL Backup\Client\Full Logging" to "1" (creating 'client' and 'full logging' if they don't already exist), and then send us the log files if this issue happens again.
Many Thanks, / comments
Hi Andrew,
Thanks for raising this. This is an issue that we've seen before. Our UI developer hoped he had fixed it in this release, but obviously its still live.
A workaround for this problem sh...
Hi Andrew,
Thanks a lot for getting back to us,
I believe you've reproduced a bug here that we've seen previously. Could you please try removing any old backup files (from SQL Backup 5.4 or earlier) from the folder you're backing up to, and then run the same command again. If I'm right, the error message should stop happening then.
We have fixed this issue for the 6.0 release in our internal builds, so it shouldn't affect anyone when the final release comes out. / comments
Hi Andrew,
Thanks a lot for getting back to us,
I believe you've reproduced a bug here that we've seen previously. Could you please try removing any old backup files (from SQL Backup 5.4 or earlie...
Thanks for the feedback. I agree that the file browser functionality isn't right coming from the restore wizard. I've raised a bug internally about this, so I hope we can get the fix into the forthcoming release. / comments
Thanks for the feedback. I agree that the file browser functionality isn't right coming from the restore wizard. I've raised a bug internally about this, so I hope we can get the fix into the for...
Hi Jonathan,
I had seen this previously in testing, but have had real trouble reproducing the problem. Could you show me the command run by the offending job? If you'd rather not post it in the forum, you can email me on backup.prerelease@red-gate.com
Thank you, / comments
Hi Jonathan,
I had seen this previously in testing, but have had real trouble reproducing the problem. Could you show me the command run by the offending job? If you'd rather not post it in the f...