Showing posts with label logging. Show all posts
Showing posts with label logging. Show all posts

Monday, March 26, 2012

how to influence SQLAgent's poll interval ?

SQLAgent is logging "[425] delay_between_response attribute (10 sec) of alert (9) is less than poll interval for this alert (20 sec)"

How can I modify this poll interval ?

We are getting this as well. We just migrated from SQL 2k to 2k5 and these errors are the only we receiving after migration. Have you found a solution or hear back on any other forum?|||I get the same log item when I restart SQL Server 2005. It is flagged as an Alert only but I am having performance issues and wonder whether this could be contributing.|||

Up until today I haven't found a solution or a work around.

I not aware of this issue having some relation to performance issues.|||

Ok, I don't know how to configure the poll interval for a poll < 20 seconds, but I removed the errors on startup by changing the settings on configured Alerts. Alerts of type 'SQL Server Event Alert' have a configuration value in the options tab/form where you set the 'Delay between responses'. For all the Alerts that were migrated from my SQL 2000 configuration the delay was set to 10 seconds which is less than the interval the system is polling at. I changed this value for each of these alerts to something equal to or greater than 20 seconds (depending on the alert) and the issues/errors on start were gone.

Hope this helps. Keith

|||

Indeed, if you don't need responce < 20 seconds, then that's the way to overcome this warning.

I would like a responce < 20 seconds and cannot find a way to change the pollinterval to less than 20 sec.

how to influence SQLAgent's poll interval ?

SQLAgent is logging "[425] delay_between_response attribute (10 sec) of alert (9) is less than poll interval for this alert (20 sec)"

How can I modify this poll interval ?

We are getting this as well. We just migrated from SQL 2k to 2k5 and these errors are the only we receiving after migration. Have you found a solution or hear back on any other forum?|||I get the same log item when I restart SQL Server 2005. It is flagged as an Alert only but I am having performance issues and wonder whether this could be contributing.|||

Up until today I haven't found a solution or a work around.

I not aware of this issue having some relation to performance issues.|||

Ok, I don't know how to configure the poll interval for a poll < 20 seconds, but I removed the errors on startup by changing the settings on configured Alerts. Alerts of type 'SQL Server Event Alert' have a configuration value in the options tab/form where you set the 'Delay between responses'. For all the Alerts that were migrated from my SQL 2000 configuration the delay was set to 10 seconds which is less than the interval the system is polling at. I changed this value for each of these alerts to something equal to or greater than 20 seconds (depending on the alert) and the issues/errors on start were gone.

Hope this helps. Keith

|||

Indeed, if you don't need responce < 20 seconds, then that's the way to overcome this warning.

I would like a responce < 20 seconds and cannot find a way to change the pollinterval to less than 20 sec.

how to influence SQLAgent's poll interval ?

SQLAgent is logging "[425] delay_between_response attribute (10 sec) of alert (9) is less than poll interval for this alert (20 sec)"

How can I modify this poll interval ?

We are getting this as well. We just migrated from SQL 2k to 2k5 and these errors are the only we receiving after migration. Have you found a solution or hear back on any other forum?|||I get the same log item when I restart SQL Server 2005. It is flagged as an Alert only but I am having performance issues and wonder whether this could be contributing.|||

Up until today I haven't found a solution or a work around.

I not aware of this issue having some relation to performance issues.|||

Ok, I don't know how to configure the poll interval for a poll < 20 seconds, but I removed the errors on startup by changing the settings on configured Alerts. Alerts of type 'SQL Server Event Alert' have a configuration value in the options tab/form where you set the 'Delay between responses'. For all the Alerts that were migrated from my SQL 2000 configuration the delay was set to 10 seconds which is less than the interval the system is polling at. I changed this value for each of these alerts to something equal to or greater than 20 seconds (depending on the alert) and the issues/errors on start were gone.

Hope this helps. Keith

|||

Indeed, if you don't need responce < 20 seconds, then that's the way to overcome this warning.

I would like a responce < 20 seconds and cannot find a way to change the pollinterval to less than 20 sec.

How to index tune 15 minutes of live activity?

With SQL 2005 Std. I once saw there is a way to use PerfMon (I think), or
some other logging tool, grab 15 minutes of data being executed on the live
SQL Server, and then do an index tuning analysis on that. Can someone
please tell me how?There is a tutorial on Database Engine Tuning Advisor on BOL. Go to SQL
Server 2005 Tutorials, SQL Server Tools Tutorials, Database Engine Tuning
Advisor Tutorial.
Ben Nevarez, MCDBA, OCP
Database Administrator
"D. Patrick" wrote:
> With SQL 2005 Std. I once saw there is a way to use PerfMon (I think), or
> some other logging tool, grab 15 minutes of data being executed on the live
> SQL Server, and then do an index tuning analysis on that. Can someone
> please tell me how?
>
>sql

How to index tune 15 minutes of live activity?

With SQL 2005 Std. I once saw there is a way to use PerfMon (I think), or
some other logging tool, grab 15 minutes of data being executed on the live
SQL Server, and then do an index tuning analysis on that. Can someone
please tell me how?There is a tutorial on Database Engine Tuning Advisor on BOL. Go to SQL
Server 2005 Tutorials, SQL Server Tools Tutorials, Database Engine Tuning
Advisor Tutorial.
Ben Nevarez, MCDBA, OCP
Database Administrator
"D. Patrick" wrote:

> With SQL 2005 Std. I once saw there is a way to use PerfMon (I think), or
> some other logging tool, grab 15 minutes of data being executed on the liv
e
> SQL Server, and then do an index tuning analysis on that. Can someone
> please tell me how?
>
>