Comments
Sort by recent activity
I got around the problem by creating a step before creating the release script, using the DLM Release 2 widget to copy the production schema over the top of the test database schema. The create the release script, then deploy. That seemed to work. / comments
I got around the problem by creating a step before creating the release script, using the DLM Release 2 widget to copy the production schema over the top of the test database schema. The create the...
Hi Chris
I'm using version 3.1.0.125 for SqlMonitor.
The database version is Sql Server 2008.
Thanks / comments
Hi Chris
I'm using version 3.1.0.125 for SqlMonitor.
The database version is Sql Server 2008.
Thanks
Hi Priya
Thanks for the email for the fix. I will install it soon.
I ran the DBCC SHOWCONTIG WITH TABLERESULTS, FAST and it came up with 6 indexes that were greater than 1000 pages and all had logical fragmentation of 24%-97%
Thanks
Rakesh / comments
Hi Priya
Thanks for the email for the fix. I will install it soon.
I ran the DBCC SHOWCONTIG WITH TABLERESULTS, FAST and it came up with 6 indexes that were greater than 1000 pages and all had log...
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...
Hi Chris,
Sorry for the late reply, i've been off for two weeks. It's a Check Database Integrity Task from a maintenance plan / comments
Hi Chris,
Sorry for the late reply, i've been off for two weeks. It's a Check Database Integrity Task from a maintenance plan
Hi Chris
I've taken BACKUP out of my T-SQL filtering so that it is now just CHECKDB.
The process filter still contains Microsoft Office 2003.
I will see what happens tomorrow morning after the backups complete, and provide you the feedback.
Thanks
Rakesh / comments
Hi Chris
I've taken BACKUP out of my T-SQL filtering so that it is now just CHECKDB.
The process filter still contains Microsoft Office 2003.
I will see what happens tomorrow morning after the back...
Hi Chris
Just checked the SQL Monitor email alerts for this morning and i have started getting the long running backup jobs through again, so yes, BACKUP filtering was filtering. Still getting the CHECKDB ones through even thought that's still specified in the filter.
Thanks
Rakesh / comments
Hi Chris
Just checked the SQL Monitor email alerts for this morning and i have started getting the long running backup jobs through again, so yes, BACKUP filtering was filtering. Still getting the...
Hi Chris
Sorry. I didn't realise that Microsoft Office 2003 and BACKUP|CHECKDB were AND's. I thought they were OR'd. That would explain why CHECKDB wasn't being filtered.
It would be nice then, to be able to set up multiple conditions on an alert not to be sent out as i can't see how i would do what i'm trying to do right now, that is filter out Microsoft Office 2003 OR BACKUP|CHECKDB.
Thanks
Rakesh / comments
Hi Chris
Sorry. I didn't realise that Microsoft Office 2003 and BACKUP|CHECKDB were AND's. I thought they were OR'd. That would explain why CHECKDB wasn't being filtered.
It would be nice then, ...