Comments
Sort by recent activity
Brian Donahue wrote:
OK, I will close the ticket that this forum topic automatically raised and let you deal with that other ticket. I think it's been escalated already as several users have been affected and it's been identified as a problem rather than an isolated incident.
Hi Brian,
I had the issue with 3.4 and still have it with 3.5. Could you add me to any kind of "interested party" list so that when this is solved I get immediate notification from Red Gate please?
If you could update this thread with the incident number you're using for tracking, I'll keep a record.
If it has been escalated, are you able to tell those of us affected when we might see a patch release please?
Cheers! / comments
Brian Donahue wrote:
OK, I will close the ticket that this forum topic automatically raised and let you deal with that other ticket. I think it's been escalated already as several users have bee...
kondrich wrote:
What would be also great is: Red-Gate toolbar should remain where it is when it was moved by the user.
So if I move it from a dedicated toolbar row to a row with another toolbar to save vertical space, it should stay there after restarting SSMS.
Right now, it stays there after the first restart of SSMS. But after the second restart it magically hops to its own toolbar row again (with our without using it between those restarts).
Cannot agree more! PLEASE fix this utterly annoying behavior. Having run out of votes on Uservoice, this is currently my only way of saying, "please".
Thanks! / comments
kondrich wrote:
What would be also great is: Red-Gate toolbar should remain where it is when it was moved by the user.
So if I move it from a dedicated toolbar row to a row with another toolbar ...
That's true, Priyasinha, James is handling this.
The 3.3.0.270 installer was downloaded without incident. There's definitely something in the 3.4.1.4 exe that Sophos doesn't like the look of. Microsoft Security Essentials OK'd it, though.
Reverting to 3.3 was the only solution.
Note to self (and others), "When verification of an installer download gives this error, DO NOT continue - you will have to uninstall the product to get a working version". / comments
That's true, Priyasinha, James is handling this.
The 3.3.0.270 installer was downloaded without incident. There's definitely something in the 3.4.1.4 exe that Sophos doesn't like the look of. Mic...
I'm leaning more towards a MICROSOFT issue. There are frequent times when, for reasons known ONLY to Microsoft it seems, a window will open BEHIND the active window on whichever of the three displays I'm using.
In this case, SSMS2012 was open on the center display. While waiting for the download to complete, I interacted with pages in Chrome on the left display. Upon completion of the download, the installer window posted to the LEFT display, BEHIND Chrome, but did NOT register an open window on any of the task bars on any of the displays! I only found the "missing installer" when I closed Chrome down because SSDT "lost" the color picker for a report cell BEHIND the main window and there's no way on earth (known to me, at least) to get that dialog front and center! Minimize via Task Manager then Switch-to at least makes SSDT active again - close and reboot is the ONLY solution to the "hiding window issue" with W-8 that I'm aware of.
It would be great if the Red Gate installer forced itself to the front of the same display as the download was visible upon... Any chance of that, please?
Shy of that, I think this can be closed as "dumb Microsoft error", NOT a Red Gate bug... / comments
I'm leaning more towards a MICROSOFT issue. There are frequent times when, for reasons known ONLY to Microsoft it seems, a window will open BEHIND the active window on whichever of the three displ...
Priceless comments, Chris and freecell1. Just what I needed to enjoy the best of both worlds.
Cheers, to you, too...! / comments
Priceless comments, Chris and freecell1. Just what I needed to enjoy the best of both worlds.
Cheers, to you, too...!
Stunning that having been a user of SQL Prompt since version 2 I assumed it would be smart enough to prompt whenever I typed! Intelliview appears to be smarter.
Guess I'll have to suggest that it do that...
What's more strange is that if I type "SELECT * FROM x" I get a pick list, so I duly select the database and it's auto-filled. If I then DOUBLE-CLICK the database and immediately type "x" I get a pick list! And I didn't have to Ctrl+space to get it!
So, what it boils down to is that SQL Prompt exercises "situational compliance" with my double-click-type-and-expect-a-pick-list demands.
Perhaps you can now see why I consider the original post to highlight a BUG.
I would venture to suggest that SQL Prompt be made CONSISTENT. It is VERY typical for developers to double-click, type, and expect a pick list. Would you register a case, please, as a bug, and fix it? Maybe while you're at it you'd give an option for this kind of expected behavior (by some) to be "normal" or "inactive", so nobody is upset.
Thanks. / comments
Stunning that having been a user of SQL Prompt since version 2 I assumed it would be smart enough to prompt whenever I typed! Intelliview appears to be smarter.
Guess I'll have to suggest that it ...
Scope would appear to be the issue but having commented the go out, double-clicked 116, typed @S I get nothing at all by way of prompting. If I Ctrl+Space I get the variables, but I shouldn't have to do that... / comments
Scope would appear to be the issue but having commented the go out, double-clicked 116, typed @S I get nothing at all by way of prompting. If I Ctrl+Space I get the variables, but I shouldn't have...
Thanks, Chris, just goes to show how little time one has to read the user guide, despite having been an original user of SQL Response, then SQL Monitor!
Thanks for the info. / comments
Thanks, Chris, just goes to show how little time one has to read the user guide, despite having been an original user of SQL Response, then SQL Monitor!
Thanks for the info.
Makes sense, especially as I have a 2-week retention period.
Would you consider:
1. NOT purging "Open" Alerts like this.
2. Including the ORIGINAL Alert reference in the "Ended" email so it can be shown in the UI with one click.
3. Including a BIG BOLD "ALERT SPANS <LONG DURATION>" chunk of verbiage in the email to bring our attention to this kind of thing - I seriously don't have time to read every alert in detail so the more you can highlight "Weird stuff" the more help it is.
<LONG DURATION> should be anything more than the data purge period and optionally, configurable, perhaps, anything over X days. I typically only care about the ORIGINAL Alert email and not the Ended one for 95%+ of reported incidents - I investigate the original, deal with it, clear it, and move on. To be "woken up" so to speak, with really OLD NEWS is noise I don't need so anything you can do to reduce the noise level of Ended emails would be brilliant!
Cheers! / comments
Makes sense, especially as I have a 2-week retention period.
Would you consider:
1. NOT purging "Open" Alerts like this.
2. Including the ORIGINAL Alert reference in the "Ended" email so it can be ...
No need to remove the file after I whacked the extraneous backup history. All clients now refresh the activity history just fine.
I deployed the server bits to three more production servers that have only 30-day history retention and had no issues at all. Their backup schedules are very similar to the 6-month-retention machine, BTW.
The fact that SQL Monitor kicked out a Long Running Query Alert for sqbdata as the underlying process tells me that the issue lies in THAT process and that the volume of data gave it a two hour twenty five minute headache! / comments
No need to remove the file after I whacked the extraneous backup history. All clients now refresh the activity history just fine.
I deployed the server bits to three more production servers that h...