Comments
Sort by recent activity
Hi Randy,
This error is encountered when SQL Backup attempts to write header information to the backup file and is unable too because another process has grabbed the file.
SQL Backup will attempt to write the data 4 times, if it fails the 4th time you are given the 775 error and the data is not written.
The backup is still valid but may cause problems if you try to restore multiple SQL Backup transaction log backups in the same job. This is because the LSN data is unavailable to put the backups in correct restoration order.
I hope this helps. / comments
Hi Randy,
This error is encountered when SQL Backup attempts to write header information to the backup file and is unable too because another process has grabbed the file.
SQL Backup will attempt t...
Hi Chris/All,
If you run check for updates now you should receive SQL Backup 6.5.1.9 which contains this fix.
There won't be an announcement on the forum as far as I'm aware.
Thanks, / comments
Hi Chris/All,
If you run check for updates now you should receive SQL Backup 6.5.1.9 which contains this fix.
There won't be an announcement on the forum as far as I'm aware.
Thanks,
Hi Jason.
The fix to correct the behaviour when the File locations drop down box was used with Overwrite existing database being selected is also in 6.5.1.9.
Could you email support@red-gate.com with details of the issue you are currently seeing and screenshots if possible?
Thanks, / comments
Hi Jason.
The fix to correct the behaviour when the File locations drop down box was used with Overwrite existing database being selected is also in 6.5.1.9.
Could you email support@red-gate.com wi...
Hi David,
The fix in this version was just to correct the behaviour when the File locations drop down box was used when Overwrite existing database was selected.
The issue with SQL Backup not reading the correct registry keys to obtain the SQL Server default data and log locations is a bigger one which we will hopefully fix in the next major release.
Thanks, / comments
Hi David,
The fix in this version was just to correct the behaviour when the File locations drop down box was used when Overwrite existing database was selected.
The issue with SQL Backup not readi...
Hi Andy,
It's just that the version number of the Server Components has now been incremented to match the GUI. The GUI however notices that the Server Components build number is older than the GUI and prompts for an upgrade.
Thanks, / comments
Hi Andy,
It's just that the version number of the Server Components has now been incremented to match the GUI. The GUI however notices that the Server Components build number is older than the GUI...
Hi Andrew/David,
If you would like to download this it should fix the issue with the Combo box when Overwrite existing database is selected.
Let me know how you get on.
Thanks, / comments
Hi Andrew/David,
If you would like to download this it should fix the issue with the Combo box when Overwrite existing database is selected.
Let me know how you get on.
Thanks,
Hi Andrew,
Thank you for pointing this out, we will take a look into it. Switching to Create new database and back to Overwrite existing should get you into a workable state when this does happen.
Out of interest, when you select a database to be overwritten by the restore what do you think should appear for the file locations by default?
SQL Server Data Directory.
Database file locations from the backup file.
Database file locations from the database being overwritten.
Thanks, / comments
Hi Andrew,
Thank you for pointing this out, we will take a look into it. Switching to Create new database and back to Overwrite existing should get you into a workable state when this does happen....
Hi rev,
Great news that it's now working. Unfortunately there isn't currently an option to choose where the trace files will be created. May I ask why you would like to have them somewhere other than the default log directory?
Thanks, / comments
Hi rev,
Great news that it's now working. Unfortunately there isn't currently an option to choose where the trace files will be created. May I ask why you would like to have them somewhere other ...
Thank you for your response. I'll feed that back to the development team.
Thanks, / comments
Thank you for your response. I'll feed that back to the development team.
Thanks,
Hi rev,
It's not pretty but if you put F:\\ in the Log location, SSMS will only strip one \ and the trace flag should then work!
Let me know how you get on.
Thanks, / comments
Hi rev,
It's not pretty but if you put F:\\ in the Log location, SSMS will only strip one \ and the trace flag should then work!
Let me know how you get on.
Thanks,