Comments
Sort by recent activity
Hi,
Apologies for the issue you are facing.
This looks like a bug with SQL Response. Since the model has now been changed to Simple hence the check has been stopped for this recommendation. I am afraid since recommendation doesn't get purged hence this cannot be removed. We will fix this for V 2.0.
The only workaround I can think of is change the model back to Full. Do a log backup and then wait for this recommendation to go away. Change the model back to Simple again.
Regards,
Priya / comments
Hi,
Apologies for the issue you are facing.
This looks like a bug with SQL Response. Since the model has now been changed to Simple hence the check has been stopped for this recommendation. I am af...
Hi,
Apologies for the issue you are facing. Please email your license keys to support@red-gate.com and then we can verify if activation has come through to the our licensing server or not.
Thanks,
Priya / comments
Hi,
Apologies for the issue you are facing. Please email your license keys to support@red-gate.com and then we can verify if activation has come through to the our licensing server or not.
Thanks,
...
Apologies Ian for copying the answer. I remember it writing on forum sometime back so copied it from my old answer!! ':oops:'
Yes, you are correct in saying that it is not clear. Ideally, we shouldn't let user configure anything which is less than our polling frequency. We will improve this in V 2.0.
Regards,
Priya / comments
Apologies Ian for copying the answer. I remember it writing on forum sometime back so copied it from my old answer!! ':oops:'
Yes, you are correct in saying that it is not clear. Ideally, we should...
Hi,
You are not getting Long Running with duration of 10 seconds because by default we poll only every 45 sec (for Long Running Query). So for a query to qualify for 'Long Running Query' alert it should ideally pass at least twice when we poll. So SQL Response can at best catch a query of duration 46 sec but it will always catch anything which is running for more than 90 sec (which is double the polling frequency). E.g. if you always want to catch a query which is of duration 40 sec or more then you have to reduce the polling frequency to 20 sec.
You can look at the config.xml (which is in install directory where you have installed your Alert Repository). This is by default should be at this location C:\Program Files\Red Gate\SQL Response 1\Alert Repository. Then look at this particular section:
<!-- This will affect the polling frequency for these alerts; Long running query and Blocked SQL Process - setting to every 45 seconds-->
<SysProcessesTime>45</SysProcessesTime>
You can change this to modify the polling frequency. But I would not recommend to set this to a very low value as this will have impact on the performance of your server.
If you want to test SQL Response for a Long Running Query then may be the easiest thing would be to use a waitfor delay statement. Something like Waitfor delay '00:02:00'
Thanks,
Priya / comments
Hi,
You are not getting Long Running with duration of 10 seconds because by default we poll only every 45 sec (for Long Running Query). So for a query to qualify for 'Long Running Query' alert it s...
Ideally ... the clean up process should have deleted these files after SQL Response used it. But looks like somehow they have been left behind. Yes, please delete all these files which are older than today. After that if you see this happening again i.e. if older files are not getting deleted then please let us know.
Regards,
Priya / comments
Ideally ... the clean up process should have deleted these files after SQL Response used it. But looks like somehow they have been left behind. Yes, please delete all these files which are older th...
Hi,
Please read this KB article. You will not lose any data. http://www.red-gate.com/supportcenter/C ... 000321.htm
Thanks,
Priya / comments
Hi,
Please read this KB article. You will not lose any data.http://www.red-gate.com/supportcenter/C ... 000321.htm
Thanks,
Priya
Hi,
The file which you have pointed are actually trace file created by SQL Response.
If you have turned trace ON on your SQL Sever instance then SQL Response creates these trace files. SQL Response creates these files and if any alert is raised then we copy parts of the trace in our alert snapshot file. These files have maximum size set (which is few KB) and they are deleted as soon as we have used it (generally within 5 minutes). Sorry but we do not have any way to manage these files. By default they go to SQL Server Data directory.
Thanks,
Priya / comments
Hi,
The file which you have pointed are actually trace file created by SQL Response.
If you have turned trace ON on your SQL Sever instance then SQL Response creates these trace files. SQL Response...
Hi,
If you are monitoring more than one server but you have only licensed few and other are still on trial .. in this case you will keep seeing the message "License: 13 days of trial remaining".
But if you licensed all the servers you are monitoring then the bottom status should go away. The status bar does take a while to refresh so if you keep seeing this message even after 2 hours then please do let us know.
The "Activate Server License" option is grayed out when your server is already licensed.
Hope this helps.
Regards,
Priya / comments
Hi,
If you are monitoring more than one server but you have only licensed few and other are still on trial .. in this case you will keep seeing the message "License: 13 days of trial remaining".
Bu...
Hi,
Apologies for the issue you are facing. I have just sent you an email regarding this.
Thanks,
Priya / comments
Hi,
Apologies for the issue you are facing. I have just sent you an email regarding this.
Thanks,
Priya
Hi,
Please read this article for more information. http://www.red-gate.com/supportcenter/C ... 20Response
Regards,
Priya / comments
Hi,
Please read this article for more information.http://www.red-gate.com/supportcenter/C ... 20Response
Regards,
Priya