Activity overview
Latest activity by mglenn
Has Red-Gate looked into performance tuning sqbdata? Activity History still takes forever to populate--GT 5 minutes for us on a server that contains 1 year of history.
Customers should not be forced to delete important backup history as a workaround for a poorly performing SQL Backup process. / comments
Has Red-Gate looked into performance tuning sqbdata? Activity History still takes forever to populate--GT 5 minutes for us on a server that contains 1 year of history.
Customers should not be force...
Option to Autoselect Identity Columns for Matching
I only use SQL Data Compare occasionally, so this may already exist, but I could use a per-session option to automatically use an Identity column for matching when no primary key is set. One of our...
Another (Futile?) Enhancement Request
The Multi Script option "Include database name in results" removes Server Name as well as Database Name column. I don't know if this is a bug or feature, but would prefer if it did not also remove ...
SQL Backup Templates
SQL Backup templates are missing a few very basic features. Still waiting for the ability to:
(1) Rename an existing template.
(2) Modify existing templates. Currently we have to write down or memo...
Compression Analyzer Suggestion
It would be nice if compression analyzer also showed estimated duration and CPU utilization for each compression level along with size.
My experience was that upgrading from 5.4 to 6.1 worked without any problems for multiple SQL Server 2000 and 2005 instances. The only problem I had was upgrading the repository server (SQL Server 2005). The failure pattern was identical to fatherjack's original post (failing on: "The SQL Backup extended stored procedure DLL version is 5.4.0.55, and 6.0.0.412 was expected.")
After 5 or 6 unsuccessful attempts from the client, I switched to manual upgrade on the repository server after first stopping the SQL Backup service. Even that failed, but gave a somewhat different error msg: "The extended stored procedure file (xp_sqlbackup.dll) that exists is an earlier version. Check that you have rights to overwrite the existing file,and run the installation again."
It was no surprise to find that the DLL was locked (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xp_sqlbackup.dll).
To successfully upgrade the repository server, I had to unlock the DLL (using unlocker), run SQBServerSetup again, delete and re-register the two extended stored procs:
sp_addextendedproc 'sqlbackup','xp_sqlbackup.dll'
sp_addextendedproc 'sqbutility','xp_sqlbackup.dll'
and restart the SQL Server instance.
By the way, the repository runs in a SS 2005 default instance on the same server with a SS 2000 named instance. I did not have any problems upgrading the SS 2000 named instance prior to the above adventures with the repository instance. / comments
My experience was that upgrading from 5.4 to 6.1 worked without any problems for multiple SQL Server 2000 and 2005 instances. The only problem I had was upgrading the repository server (SQL Server ...
SQL Backup Pro 5 - Nice Upgrade!
I just installed SQL Backup Pro 5.1. Congratulations on a nice upgrade.
A couple of small things on my wish list:
1. Ability to disable jobs from the UI.
2. Ability to remove SQL Backup Pro server ...
Thanks. Refresh is indeed enabled at the server level. I just started using SQL Backup a couple days ago. Also I just read a post about why Refresh function was recently disabled at the database level. / comments
Thanks. Refresh is indeed enabled at the server level. I just started using SQL Backup a couple days ago. Also I just read a post about why Refresh function was recently disabled at the database le...
SQL Backup 4.6 GUI Issues
I leave the GUI open for a few days with a specific database selected. Then SQL Server Agent backup jobs run using the SQL Backup extended stored proc. The new backup jobs do not appear automatical...