How can we help you today? How can we help you today?
patelrk
Thanks Chris I did already have the low and medium alert thresholds disabled so i would never have seen the original sql fragment. That's why i couldn't figure out why the alert wasn't being filtered out. I can't see this situation happening very frequently so am happy to add blobeater to my regex, but with the lack of sql fragment history as the alert escalates (if you don't have the low and medium level alerts selected), makes diagnosis quite difficult. For example, in my situation where i have only High selected the alert chain would look a little like: Alert level High -> -- network protocol: LPC set quoted_identifier on set arithabort off set numeric_roundabort off set ansi_warnings on set ansi_padding on set ansi_nulls on set concat_null_yields_null on set cursor_close_on_commit off set implicit_transactions off set language us_english set dateformat mdy set datefirst 7 set transaction isolation level read committed USE [RedGateMonitor21] DBCC CHECKDB(N'RedGateMonitor21') WITH NO_INFOMSGS Alert level Low-> DECLARE @... VARBINARY(8000) SELECT @... = CheckIndex (ROWSET_COLUMN_FACT_BLOB) FROM { IRowset 0x70C6840502000000 } GROUP BY ROWSET_COLUMN_FACT_KEY >> WITH ORDER BY ROWSET_COLUMN_FACT_KEY, ROWSET_COLUMN_SLOT_ID, ROWSET_COLUMN_COMBINED_ID, ROWSET_COLUMN_FACT_BLOB OPTION (ORDER GROUP) Thanks Rakesh / comments
Thanks Chris I did already have the low and medium alert thresholds disabled so i would never have seen the original sql fragment. That's why i couldn't figure out why the alert wasn't being filte...
0 votes