Please STOP auto-refresh!
PDinCA
Posts: 642 Silver 1
I know I've asked for this before, AND added a request to Uservoice, but after six YEARS of constantly being annoyed and LOSING TIME while reviewing the Activity History BECAUSE OF THE DARNED AUTO-REFRESH, could you please, like Microsoft so kindly gives in Profiler, GIVE US AN OPTION IN THE VIEW MENU TO STOP AUTO-REFRESH, PLEASE!
Sorry, just got another time-waster auto-refresh and I'm a bit peeved that I have to take a lot longer to do a simple thing than I should.
THANKS in advance.
Sorry, just got another time-waster auto-refresh and I'm a bit peeved that I have to take a lot longer to do a simple thing than I should.
THANKS in advance.
Jesus Christ: Lunatic, liar or Lord?
Decide wisely...
Decide wisely...
Comments
Thank you for your forum post.
A support call has been created for you the call reference is 8828. I have added the details of the support call and this forum post to an existing Bug Report / Feature Request whose reference is SB-3123. I will request the SQL Backup Product Manager to review SB-3123.
I will also provide an update to you from our call logging system.
Many Thanks
Eddie
Senior Product Support Engineer
Redgate Software Ltd
Email: support@red-gate.com
Here is the work around: Create a group for each instance and put the instance in that group.
I know, this is a real pain to do, but at least auto refresh does not kick in until you open the given group.
My Reply:
Referring to my final sentence, above, DOES MY REPLY CLARIFY THINGS?
Is this thread dead?
Is Support Case 8828 dead?
This is still causing issues as I cannot research an ongoing remote file erase issue, support case 10148, while this dumb refresh goes on sticking it to me by presenting the latest activity in my face all the time... Yes, Eddie has provided an "undocumented" workaround, but is that the best there is - turn off ALL refresh when only the lower pane refresh should be togglable? Not exactly desirable for everyday usage, IMO.
Yes, I'm a bit peevish because I've been using SQL Backup seems like since forever, and this ONE pain in the rear behavior is still a pain in the rear after how many years? Five? Six? Seven? Lost count...
"SQL Profiler behaves better than SQL Backup" - is that a statement to live down or what?
Decide wisely...
Sorry for the delay, I can confirm that we understand the scenario you've described. I'm currently working on SQL Backup planning, and this is on my list of things to be looked into.
Best regards,
Colin.
Cheers!
Decide wisely...
With regards to support call reference 8828. This call is on hold waiting for a bug fix, two bug fixes actually. The bug reference numbers are SB-3123 and SB-4400.
SB-3123 - Is an enhancement for SQL Backup users to be able to configure the GUI refresh rate.
SB-4400 - SQL Backup GUI fails or very slow to load backup history.
I understand your frustration, the near constant refreshing and poor performance loading backup / activity history is well known to me. Small improvements have been made since this style of GUI was introduced in SQL Backup V5, but further GUI work is still required.
Many Thanks
Eddie
Senior Product Support Engineer
Redgate Software Ltd
Email: support@red-gate.com
I want to query the history directly to determine things such as how the duration, raw size, and compressed size of the t-log backups varies through the day.
I can query MSDB to get some of the information I need but right now the only way I see to get the Raw and Compressed size is to laboriously page through the constantly updating GUI which does not even sort in a useful order. I.e., if you sort by Type then the Date is unordered. If you sort by date, then the Full and Diffs are hard to find.
Direct, Read Access to the history database would solve this issue.
This is stored in C:\Users\[username]\AppData\Local\Red Gate\SQL Backup\Server Data\1.dat
I’ve used tools like Database .NET ( http://fishcodelib.com/Database.htm - disclaimer: nothing to do with us) to query this. The activityhistory table has the data that’s likely to be of interest.
Please note that this database schema is not a managed schema, and whilst it’s unlikely that it’ll change we can’t commit to not making changes that might break any custom integration done against them.
Best regards,
Colin.