"SQL Agent - Alert Engine"

Question

"SQL Agent - Alert Engine"

Mr_Q

Ten Centuries

Points: 1005
More actions
January 17, 2016 at 12:26 pm

#151450

Hi,
In SQL Server 2005 Standard Edition SP 1, i made a selection from sys.sysprocesses. One of processes is called "SQL Agent - Alert Engine". I need to know IF this process involve problems and in which conditions WILL start this process ?
What involve running of this process ?
Is possible to have tables locks in DB because of this process ?
Thank you.
G.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1003863 More actions · Answer 1

Mr_Q (1/17/2016)
Hi,
In SQL Server 2005 Standard Edition SP 1, i made a selection from sys.sysprocesses. One of processes is called "SQL Agent - Alert Engine". I need to know IF this process involve problems and in which conditions WILL start this process ?
What involve running of this process ?
Is possible to have tables locks in DB because of this process ?
Thank you.

Yes, it is possible to have "tables locks" in DB but not just because of this process. Such locks (and gross CPU usage) would occur depending only on what you told SQL Server to do if there was an "alert".

Based on your question, I strongly recommend that you read the following article and make sure that you also follow the links in the article.

https://msdn.microsoft.com/en-us/library/ms189237(v=sql.130).aspx

I also strongly recommend that you update your 2005 SP1 installation to at least SP3. Of course, it would be even better to update your system to the latest version but I understand that's not always an option and does take some time but it IS important to get to at least SP3 for 2005 (mostly security updates but some having to do with engine performance).

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Mr_Q Ten Centuries Points: 1005 More actions · Answer 2

The article is for SQL Server 2016.

Is this problem serious or can I ignore it?

Thank you.

G.