Red Gate forums: SQL Response 1

RE: Extend "SQLResponsedb.trc" lifetime

xexex — Thu, 28 Jun 2012 03:11:31 GMT

Thanks for reply, I create a job which will copy the trace files to another location.
The UI of SQL response is better than SQL monitor, there are more details, icons and color in "Performance Snapshot => Statement", so there're no planning for upgrade.

RE: Extend "SQLResponsedb.trc" lifetime

james.billings — Wed, 27 Jun 2012 09:54:02 GMT

Thanks for your post regarding SQL Response. Unfortunately, the tracing (as described [url=http://www.red-gate.com/supportcenter/Content?p=SQL%20Response&c=SQL_Response\help\1.3\SR_Collecting_Trace.htm]here[/url] cannot really be configured in any way. I double-checked the config file to see if there was a hidden option, but nothing appeared.

Unfortunately, SQL Response was discontinued almost 2 years ago and no further development will take place, so this isn't a change you're going to see in the future I'm afraid.

Extend "SQLResponsedb.trc" lifetime

xexex — Tue, 26 Jun 2012 04:20:27 GMT

We're using SQL Monitor 1.3 and enable "collection of trace data", trace files are obtained in "C:\Program Files\Microsoft SQL Server\MSSQL\Data", they will be kept 20 mins.

Can I extend the lifetime of those files without copying to another location every 10 mins, e.g. keep files 1 day or longer?

Thanks

RE: Monitoring interval

priyasinha — Fri, 04 Mar 2011 10:54:41 GMT

Hi John,

I have just sent you an email with polling frequency for all the data collection. Please let us know if you dont receive it.

Thanks,
Priya

RE: Monitoring interval

priyasinha — Thu, 03 Mar 2011 17:06:07 GMT

Hi John,

Different data collection has different frequency. It can vary anything from 10 seconds (for pings) to ones a week (for index collection). If you want to know rate of any particular data collection then please ask. I can send you the detail.

Thanks,
Priya

RE: Monitoring interval

JohnWCrosby — Wed, 02 Mar 2011 16:35:33 GMT

I'm actually more interested in simply knowing what the intervals are at this point. We are looking to use the information gathered for performance benchmarking, so one major question is, how often is the data gathered? Every 15 minutes is useless for example because it's too large of a gap.

RE: Monitoring interval

priyasinha — Tue, 01 Mar 2011 15:53:02 GMT

Hi John,

We have a dedicated forum for SQL Monitor. You might want to post your queries here http://www.red-gate.com/messageboard/viewforum.php?f=133 instead.

Regarding monitoring frequency, though you can change via this config file RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config which is located in C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Monitor 2 (or equivalent location) ... I wouldn't recommed it. These schedule have been set up with optimum results in mind for things like performance, data availability etc. Changing the schedule can affect alerts adversely.

Also, would be good to know though that why do you want to change it? Is there any specific problem you are facing?

Thanks,
Priya

RE: Monitoring interval

JohnWCrosby — Tue, 01 Mar 2011 13:02:45 GMT

I can not locate a config.xml file on the machine where SQL Monitor is installed - by the way I'm using SQL Monitor which I thought was simply the replacement product for SQL Response - how can I adjust the intervals for SQL Monitor?

RE: Monitoring interval

priyasinha — Tue, 01 Mar 2011 10:11:55 GMT

Hi,

You can change it via config file but it is not exposed in UI. You can navigate to the folder where you have installed "Alert Repository", there is a file called Config.xml here. This lists all the polling frequency.

Please always take a backup of this file before making any changes. Also, you would need to restart the service after you have edited config.xml.

Thanks,
Priya

RE: Monitoring interval

JohnWCrosby — Mon, 28 Feb 2011 19:10:13 GMT

I was reading this post from 2 years ago, was the ability to change the interval ever introduced? Additionally, what is the current interval?

RE: Windows 7 - Exception conn to old Repository on ntwk svr

dlkj — Thu, 03 Feb 2011 10:29:29 GMT

Hi,

I think the problem here is when some machines have http://support.microsoft.com/kb/969083 installed and some don't. If you are seeing this issue, we'd recommend ensuring the hotfix is deployed on all machine you are using with SQL Response.

Cheers,
--
Daniel

RE: Windows 7 - Exception conn to old Repository on ntwk svr

jasonmowbray — Thu, 03 Feb 2011 10:05:47 GMT

Hi all,

I found further information on this problem here:
http://social.msdn.microsoft.com/Forums/en/vststest/thread/37861b71-1613-436d-93dc-8e7a46d6f4d4

which suggests removing KB968389 and editing the registry followed by reboot.

Was there any conclusion on which patch to apply to fix this? I'd much rather move forward than uninstall an existing patch which may well break something else in future.

Regards,

Jason

RE: Long running query - (database mail) sp_readrequest

Brian Donahue — Fri, 21 Jan 2011 15:14:17 GMT

SQL Monitor (Response's successor) has the ability to ignore based on a regular expression. This is what users are currently doing to avoid notifications about Database Mail.

RE: Long running query - (database mail) sp_readrequest

jasonmowbray — Fri, 21 Jan 2011 14:46:56 GMT

Dear Brian,

I am having the same issue as clombardo, running SQL Response 1.3. 0.58. Is there a way to avoid this?

Regards,

Jason

RE: SQL Trace Files Location & Deletion

Sian.Williams — Wed, 17 Nov 2010 17:21:07 GMT

Hi Lori,

Thanks for your post.

Generally we only recommend having Trace turned on if you're looking for a specific issue on a problematic server as it can use up to 5% extra CPU usage and potentially more memory. It can, as you've experienced here, also log a large amount of data which effectively becomes useless if you're searching for a specific problem.

There isn't a way of changing the place in which the files are logged, and it can't be reduced.

For more information on collecting trace data please click the following link;

http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Response&c=SQL_Response\help\1.3\SR_Collecting_Trace.htm

The new version - SQL Monitor - initially gathers the information collected in a trace file when Trace is turned on, however after this point it routinely overwrites it once the data file gets too big.

Also, for your information - if you still have active support and upgrades attached to your SQL Response license, you're eligible for a complimentary upgrade to the SQL Monitor which has many new features and benefits. You can check it out here - http://www.red-gate.com/products/SQL_Monitor/index.htm

If you email our sales team at sales@red-gate.com they can look into this for you.

Thanks,