Although Eddie sent me an email to which I replied very swiftly, SILENCE has ensued, sadly...
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?
| Quote: |
| Eddie Davis (Support) Nov 29 09:48 (GMT) Hi This is an undocumented feature which allows SQL Backup users to disable the timeline component of the SQL Backup GUI. By enabling this feature, you may experience improved performance of GUI. If you wish use this feature, please follow the instructions: To disable the time line, close the SQL Backup GUI and add the following registry key on the machine where the GUI is installed: HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\Client (please note, you may need to create the 'Client' folder). Create a new string value called DisableTimelineItemRequests and set the value to = 1 or true Restart the SQL Backup Agent service for each of the registered servers. Open the SQL Backup GUI and see if the performance has improved in populating the registered servers. Once the spinning wheel has stopped, it appears that the registered server is not connected. You will need to expand the registered server to see a successful connection and to see entries in the Activity History. KNOWN ISSUES Upon opening the GUI and once the registered server or servers has completed loading, it appears that the registered server is not connected. You will need to expand the registered server to see a successful connection and to see entries in the Activity History or the other bottom grid items. When navigating through the databases listed for a registered server, you may experience that the entries in the Activity History disappear. Simply click on another server or database and then click back to the original server or database to reload the Activity History or the other bottom grid items. Many Thanks Eddie Davis Technical Support Engineer Red Gate Software Ltd |
My Reply:
| Quote: |
| Thanks for the info BUT that doesn't address the issue at hand. If you refer to the behavior cited in Profiler, the top pane continues to function with auto-scroll turned off. The lower pane is then static, allowing the user to choose which activities to view. The auto UPDATE of the chronological pane should continue, just DON'T move the lower pane - that is what constitutes a huge time waster when paging through the Activity History, as in: I scroll down to the activity I'm interested in, then, having found the group of backups to investigate, along comes auto-refresh and resets the list to the top - stop THAT! Hope this clarifies. |
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?