Comments
Sort by recent activity
If I am running an expired version of the SQL Backup tool on my local workstation, and I update my servers copies of SQL Backup to 7.1, am I going to have any issues managing/seeing/monitoring from my older, expired version of my workstationi console? I'm running either 7.0.5.1 or 7.0.6.2.
Hi,
I'm afraid we cannot guarantee forwards-compatibility of the user interface. We support backwards-compatibility, meaning that you can run a later version of the UI with an older version of the server components, but not the other way around.
Are you having any problems upgrading the UI to 7.1?
Cheers,
Marianne / comments
If I am running an expired version of the SQL Backup tool on my local workstation, and I update my servers copies of SQL Backup to 7.1, am I going to have any issues managing/seeing/monitoring f...
Botht GUI (SQL Backup version) and the engine (Service application version) show 7.1.0.72. Am I running 7.1.0.214 or 7.1.0.72?
Hi Chris,
The About dialog (accessed from the user interface Help menu) gives the user interface version. The latest version of the UI is 7.1.0.214.
The Properties dialog (accessed from the user interface Edit menu, Properties option) gives the server components version. The server components are in two halves, listed as 'SQL Backup version' and 'Service application version', but should always be the same as each other. The latest version of the server components is 7.1.0.72.
From your previous post, I believe you're running version 7.1.0.214 of the user interface and version 7.1.0.72 of the server components.
Marianne / comments
Botht GUI (SQL Backup version) and the engine (Service application version) show 7.1.0.72. Am I running 7.1.0.214 or 7.1.0.72?
Hi Chris,
The About dialog (accessed from the user interface Help...
Hi Chris,
The version number in the About box refers to the version of the user interface, whereas the version number in the Server Properties dialog refers to the version of the server components.
I'll update the announcement to reflect this. Thanks for bringing this to our attention.
Marianne / comments
Hi Chris,
The version number in the About box refers to the version of the user interface, whereas the version number in the Server Properties dialog refers to the version of the server components....
Hi Chris,
Thanks for bringing this to our attention. It should be sorted out soon.
Cheers,
Marianne / comments
Hi Chris,
Thanks for bringing this to our attention. It should be sorted out soon.
Cheers,
Marianne
Unfortunately there was a minor issue with our release process yesterday. This has been fixed and the Backup and Restore Bundle now includes SQL Backup 7.1.
Thanks again for bringing this to our attention.
Marianne / comments
Unfortunately there was a minor issue with our release process yesterday. This has been fixed and the Backup and Restore Bundle now includes SQL Backup 7.1.
Thanks again for bringing this to our at...
Hi Chris,
Could you try upgrading again? Version 7.1 should be available now.
Thanks,
Marianne / comments
Hi Chris,
Could you try upgrading again? Version 7.1 should be available now.
Thanks,
Marianne
Hi
Thanks for both your forum posts. Can I check whether you added the sqbsetlogin stored procedure before calling it with blank values?
If the SQL Backup Agent Service was set to use SQL Server authentication when SQL Backup 6 was installed, the stored procedure will not have been added. If the sqbsetlogin stored procedure was used to change to SQL Server authentication later, it may have been dropped after use (as per the instructions in the forum post you refer to and Security Model (http://www.red-gate.com/supportcenter/Content/SQL_Backup/help/7.0/SBU_SecurityModel). In both these cases you would need to add the stored procedure again before being able to call it.
If this is the case, try adding the stored procedure:
execute master..sp_addextendedproc sqbsetlogin , 'xp_sqlbackup.dll'
Then call the stored procedure with blank values to use Windows authentication:
execute master..sqbsetlogin '', ''
Cheers,
Marianne[/code] / comments
Hi
Thanks for both your forum posts. Can I check whether you added the sqbsetlogin stored procedure before calling it with blank values?
If the SQL Backup Agent Service was set to use SQL Server au...
Hi Chris,
SQL Backup 7.1 will be released soon. We are expecting to release version 7.2 towards the end of Q3.
Cheers,
Marianne / comments
Hi Chris,
SQL Backup 7.1 will be released soon. We are expecting to release version 7.2 towards the end of Q3.
Cheers,
Marianne
Hi Chris
Apologies for not getting back to you sooner. This feature will not be in the next release of SQL Backup (7.1) but we are considering it for version 7.2.
I will add you to the list of users to be notified when this change is made.
Cheers,
Marianne / comments
Hi Chris
Apologies for not getting back to you sooner. This feature will not be in the next release of SQL Backup (7.1) but we are considering it for version 7.2.
I will add you to the list of user...
Hi,
It's the latter case: jobs that are scheduled to run at the same time are highlighted in the timeline as conflicting schedules to warn you of the demand on your server's processors and I/O. This may cause jobs to take longer to run.
Cheers,
Marianne / comments
Hi,
It's the latter case: jobs that are scheduled to run at the same time are highlighted in the timeline as conflicting schedules to warn you of the demand on your server's processors and I/O. Thi...