Activity overview
Latest activity by Sire
Has there been any progress on this? We got this error now when we deleted and then restored a database (with a gap of perhaps a minute or two). We cannot restart the SQL Server because it's running in production. / comments
Has there been any progress on this? We got this error now when we deleted and then restored a database (with a gap of perhaps a minute or two). We cannot restart the SQL Server because it's runnin...
I don't consider this an enhancement since it worked in the previous version.
I consider it a pretty serious bug, one which makes the software almost useless for me, since I get alerts all the time, and can't figure out the exact subquery that causes the alerts.
I hope you consider making this a priority. Thanks! / comments
I don't consider this an enhancement since it worked in the previous version.
I consider it a pretty serious bug, one which makes the software almost useless for me, since I get alerts all the time...
Chris Spencer wrote:
There's nothing in this fragment that matches the "IndexOptimize|DatabaseBackup" regex but I'm finding that I can filter out this alert by using "IndexOptimize|BACKUP DATABASE|RESTORE VERIFYONLY".
Thanks I will try this. I haven't been getting these warnings for several weeks before updating to the release version, so there might be a "breaking change" on your side? One could argue it shouldn't be necessary to know what subqueries are run by the sp.
Chris Spencer wrote:
Which version of SQL Server are you running these queries on out of interest? Also do you execute these scripts from within jobs or from directly from SSMS?
SQL Server 2008 Enterprise 64bit.
Executing from scheduled jobs.
Thanks for your help! / comments
Chris Spencer wrote:
There's nothing in this fragment that matches the "IndexOptimize|DatabaseBackup" regex but I'm finding that I can filter out this alert by using "IndexOptimize|BACKUP DATABA...
Chris Spencer wrote:
Sire wrote:
Are you able to post the SQL statements that you are trying to match? I'm guessing that these refer to stored procedures?
I'm using the famous Ola Hallengren scripts (http://ola.hallengren.com/).
SQL process fragment that fails to match on the regexp "IndexOptimize|DatabaseBackup": -- 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
SET QUOTED_IDENTIFIER OFF SET TEXTSIZE 4096
EXECUTE [dbo].[DatabaseBackup] @Databases = 'USER_DATABASES', @Directory = N'C:\SqlData\Backup', @BackupType = 'FULL', @Verify = 'Y', @CleanupTime = 336, @CheckSum = 'Y'
/ comments
Chris Spencer wrote:
Sire wrote:
Are you able to post the SQL statements that you are trying to match? I'm guessing that these refer to stored procedures?
I'm using the famous Ola Halleng...
The reg exp is clearly not the problem here. And btw, the best product is http://www.regexbuddy.com/ [image] / comments
The reg exp is clearly not the problem here. And btw, the best product is http://www.regexbuddy.com/
Using relase version 3780 also. / comments
Using relase version 3780 also.
I have a bug report regarding this.
When updating to the latest (beta) version about a week ago I started seeing long running query warnings that were excluded successfully in the previous version. The settings were unchanged, and the exclude text was still "IndexOptimize|DatabaseBackup" (not multiple lines).
I tried removing the text and entering it again.
Please check this and get back to me. Thanks! / comments
I have a bug report regarding this.
When updating to the latest (beta) version about a week ago I started seeing long running query warnings that were excluded successfully in the previous version....