ApexSQL Complete Execution Alerts Statements without WHERE clauses

Hello!

I am running into a small issue where the Execution Alerts in ApexSQL Complete are alerting for statements that contain a WHERE clause, instead of statements that don't contain a WHERE clause. It seems after I change this setting it eventually defaults back to the wrong condition.

Thanks.

Top Replies

Zivko over 5 years ago +1 verified

Hi,

The easy fix is to go to Options > Execution alerts, delete all alerts, and use Default alerts to bring them back. This way, the conditions for all alerts will be right.

You can always select an alert…
jan vaes over 5 years ago in reply to Zivko +1

that doesn't change anything for me, they were never changed so have always been default, clicking that button doesn't take away the false positive
Zivko over 5 years ago in reply to jan vaes +1

Hi jan,

Did you perform the action like from the attached video: https://drive.google.com/file/d/1nUXlfZ3lkdEvOEXfQGgDEbuYMuscdiWS/view

Also, can you please check is the Where condition exists in the alert…

0 jan vaes over 5 years ago

I have the exact same issue and it's driving me bad. Can't rely on the software anymore now.
+1 Zivko over 5 years ago

Hi,

The easy fix is to go to Options > Execution alerts, delete all alerts, and use Default alerts to bring them back. This way, the conditions for all alerts will be right.

You can always select an alert from the list and click Edit to see if the conditions are correct

Hope it helps.
- 0 jan vaes over 5 years ago in reply to Zivko
  
  that doesn't change anything for me, they were never changed so have always been default, clicking that button doesn't take away the false positive
  - 0 Zivko over 5 years ago in reply to jan vaes
    
    Hi jan,
    
    Did you perform the action like from the attached video: https://drive.google.com/file/d/1nUXlfZ3lkdEvOEXfQGgDEbuYMuscdiWS/view
    
    Also, can you please check is the Where condition exists in the alert: https://drive.google.com/file/d/1pTn2G1a6MF7ILuRem9SO52kdz-nsOepJ/view
  - 0 jan vaes over 5 years ago in reply to Zivko
    
    sorry you're right, that works. thanks for the video!
- 0 bpardo over 5 years ago in reply to Zivko
  
  Thank you! This works perfectly.
- 0 cvillegas over 5 years ago in reply to Zivko
  
  You have to do this each time though.
0 cvillegas over 5 years ago

Hi I keep having this reset on restart and have to do this every time. Is this normal or a bug? I've had others reproduce in our environment as well.
- 0 bpardo over 5 years ago in reply to cvillegas
  
  I also see this issue when I restart SQL Server Management Studio, the conditions reset to the incorrect one.
- 0 jan vaes over 5 years ago in reply to cvillegas
  
  It's most definitely a bug, and it's really annoying too. Don't know if it started since the latest Apex update or the latest SSMS update. Version I'm currently running:
  
  SQL Server Management Studio 15.0.18338.0
  SQL Server Management Objects (SMO) 16.100.41011.9
  Microsoft Analysis Services Client Tools 15.0.19205.0
  Microsoft Data Access Components (MDAC) 10.0.19041.1
  Microsoft MSXML 3.0 6.0
  Microsoft .NET Framework 4.0.30319.42000
  Operating System 10.0.19041
  - 0 cvillegas over 5 years ago in reply to jan vaes
    
    At one point I had this working after a complete uninstall / reinstall of the version that released which was bugged about a week ago due to slow typing issues. Then when they rolled back that release I see the issue appearing again.
- 0 mparker over 4 years ago in reply to cvillegas
  
  It would be great if they would provide a fix for this that doesn't require these settings to be redone in each new SSMS session.
  - 0 Zivko over 4 years ago in reply to mparker
    
    Hi,
    
    In the latest version of ApexSQL Complete, this issue has been fixed.
    
    193838: Execution alert conditions are not being saved after either SQL Server Management Studio or Visual Studio restart
  - 0 mparker over 4 years ago in reply to Zivko
    
    Thank you. Installing the new release now.