How can we help you today? How can we help you today?
broughtie
Activity overview Badges (0) Posts (6) Comments (15)

Comments

Sort by recent activity
I currently use SQL Sentry to monitor our SQL servers, and although the product has a number of nice features, the section that monitors SQL Agent jobs is the part I use the most and if RedGate SQL Response if powerful enough, I'd probably dump SQL Sentry for SQL Response. If if only managing a single server, I still see the ability to configure incidents as one of the most important features. In the current beta of SQL Response, its a bit of a mystery what "incidents" are even being monitored. It would be nice to be able to pull up a list of all possible incidents and be able to configure each one (turn on /off, set default monitoring thresholds, etc). Specific to the topic of this thread, I thing every incident type need to be configurable for each object covered by that incident type. For example, lets look at the "Long Running Query" incident. Lets say I have three jobs setup in SQL Agent that execute some code. Job 1 runs continuously and never ends, Job 2 runs for about 3 seconds every 10 minutes, and Job 3 runs for about 15 minutes once a day. Now for each of these jobs, I'm going to want to configure individually how "Long Running Query" is defined. Job 1 shouldn't even be included in this incident type, Job 2 should be considered long running if it runs for more than 30 seconds, and Job 3 shoudl be considered long running if it runs for more than 20 minutes. Now no one is going to want to have to configure each incident for every object as part of the setup since that would be daunting in many environments, and the is where the concept of default values for an incident type come into play. Perhaps I can define "long running query" to be anything that take more than 10% of the average execution time. Or maybe anything that runs for more than 30 seconds. These defaults might cover 90% of my objects, and I could then go into individual objects and make specific adjustments for those objects that differ from the default. / comments
  1. Community
  2. SQL Response Beta
  3. Are thresholds configurable by user?
I currently use SQL Sentry to monitor our SQL servers, and although the product has a number of nice features, the section that monitors SQL Agent jobs is the part I use the most and if RedGate SQL...
0 votes
I would agree that the software must necessarily provide the ability specify a different Windows loing for each server as an option. We don't use SQL Server authentication, although I imagine there are other who are still forced to by vendors, legacy code, or poor judgement. / comments
  1. Community
  2. SQL Response Beta
  3. Domain Model
I would agree that the software must necessarily provide the ability specify a different Windows loing for each server as an option. We don't use SQL Server authentication, although I imagine ther...
0 votes
If there were no jobs, then the Agent Not Running incident would have not much value. Getting the "Job failed to start" incident is good and does provide a minimum level of alerting the Agent is perhaps not running, but take the following scenario: Somehow Agent is disabled/turned off at 2pm. You're next scheduled job is 1am. The "Job failed to start" incident would fire at 1am and it would be possible to respond and fix it, however, why should I have to wait until 1am and get woken up, when I could have found out Agent wasn't working 11 hours earlier and easily fixed it while I was at my computer. / comments
  1. Community
  2. SQL Response Beta
  3. Check Status of SQL Agent.
If there were no jobs, then the Agent Not Running incident would have not much value. Getting the "Job failed to start" incident is good and does provide a minimum level of alerting the Agent is p...
0 votes
I would also concur that adding an "Agent not running" incident would be a nice addition to the feature set. / comments
  1. Community
  2. SQL Response Beta
  3. Check Status of SQL Agent.
I would also concur that adding an "Agent not running" incident would be a nice addition to the feature set.
0 votes
As someone who already owns a number of tools in the "Toolbelt", I hope you'll consider upgrade pricing for existing owners. Also, will there be any early-bird pricing. Also, since the toolbelt incldues developer licensed vs server licensed products, are there discounts for additional server licenses of the toolbelt products? Should the there be a Developer toolbelt and a Server toolbelt? However it works out, I'm glad to see you offering a super bundle since I want everything you make! Not a dud in the bunch; once you upgrade SQL Prompt 2.0 that is. [image] / comments
  1. Community
  2. SQL Refactor Public Beta
  3. SQL Refactor pricing
As someone who already owns a number of tools in the "Toolbelt", I hope you'll consider upgrade pricing for existing owners. Also, will there be any early-bird pricing. Also, since the toolbelt i...
0 votes
That's disappointing, but I can understand how its too late in the cycle to bring in now. I really hope you look at reintroducing it in a future update, even if its relegated to a keyboard shortcut rather than a menu item. I have to imagine the code behind was simple enough so it was cut just to avoid feature bloat, but I was definitely useful when trying to clean up someone else's TSQL without wanting to totally reformat it. / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. Where's the "Uppercase Keywords" command
That's disappointing, but I can understand how its too late in the cycle to bring in now. I really hope you look at reintroducing it in a future update, even if its relegated to a keyboard shortcu...
0 votes
Ah, missed, that. Format SQL works great, thanks. Would have been nice to be able to import my refactor settings file, but I think I've got it setup the same again. / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. Uninstall SQL Refactor before installing SQL Prompt 5
Ah, missed, that. Format SQL works great, thanks. Would have been nice to be able to import my refactor settings file, but I think I've got it setup the same again.
0 votes
Layout SQL would be the command I'd like to see prioritized. / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. Uninstall SQL Refactor before installing SQL Prompt 5
Layout SQL would be the command I'd like to see prioritized.
0 votes
Okay, so now my SQL Refactor is broken and I can't get it back. I uninstalled every Red-Gate product on my computer and then reinstalled the latest SQL Toolbelt, with various reboots involved, and I STILL get the "The addin 'SQL Refactor 1.3' failed to load or caused an exception...." error. My menus in SSMS correctly show just SQL Refactor and SQL Prompt 4. SQL Prompt works fine. Very frustrating for the EAP to break a different product to this level. Where do I turn for help? / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. Startup errors in SSMS
Okay, so now my SQL Refactor is broken and I can't get it back. I uninstalled every Red-Gate product on my computer and then reinstalled the latest SQL Toolbelt, with various reboots involved, and...
0 votes
So I see various SQL Refactor features being added to SQL Prompt. Is the plan to just move all the functionality of Refactor into Prompt and give rid of SQL Refactor as a stand-alone product? I'd vote for that. / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. SQL Prompt 5 first early access release
So I see various SQL Refactor features being added to SQL Prompt. Is the plan to just move all the functionality of Refactor into Prompt and give rid of SQL Refactor as a stand-alone product? I'd...
0 votes
Total activity
33
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
12