Viewing 11 posts - 91 through 101 (of 101 total)
The last script builds a job that executes every Monday at 9am 🙂
April 19, 2011 at 6:38 am
Surely, someone's seen/heard of this issue before.
April 18, 2011 at 11:15 am
I do appreciate the work-around idea. But, I am still very curious as to why alerts aren't firing when the blocking threshold is reached.
April 18, 2011 at 8:10 am
server:
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build...
April 15, 2011 at 8:15 am
It is the first alert on both the dev server and my local sql laptop. I have also restarted sql agent on both, and still same issue. I...
April 15, 2011 at 7:34 am
I deleted mine, executed your script, same issue. Doesn't matter how long I set it up to lock, as soon as it frees up the email is sent. ...
April 15, 2011 at 6:59 am
type: SQL Server Performance condition alert
Object: SQLServer:Locks
Counter: Lock Wait Time (ms)
Instance: _Total
Alert if counter: rises above Value: 1
Response: Notify operators (email works)
The alert technically works, but only after the locking...
April 14, 2011 at 1:54 pm
The best way would be to create an email address table or add a column to an existing table for emails. The sp should go to the table.column for...
April 6, 2011 at 11:26 am
Thanks, that's what I thought. I appreciate the response.
April 5, 2011 at 7:14 am
Can't update original cte after the first select statement. Try adding a second cte something like this:
WITH CTE (ProblemID, Who, seq)
AS
(
SELECT X.problemId, X.Who,
ROW_NUMBER() OVER (PARTITION BY ProblemID...
March 23, 2011 at 9:28 am
Yep, replaced the part for 2k with a sql exec (@variable) and it worked, thanks a bunch!
November 8, 2010 at 1:14 pm
Viewing 11 posts - 91 through 101 (of 101 total)