I have tried various ways to get SQL monitor to create a 'log backup overdue' alert for a database using the simple recovery model but have not had any success. It would only alert after I had switched the database to Full recovery model (and performing some action) before switching back to the simple recovery mode. Can you provide any further details (sql server version, logs from sql monitor, screenshot of the properties > options section for the specified database, etc)?
SQL Server Version:
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
May 14 2014 18:34:29
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
Can you also check the Properties > General page tab for Datawarehouse4 and check the timestamps for both backup and log backup there (screenshot or otherwise)? I just want to ensure there isn't some errant process occurring that is switching between the different recovery modes for some odd reason. I'll continue replicating your setup as I can in the meantime.
Kind regards,
Alex Bartley
Product Support Engineer
Last db backup: 27/12/2014 02:13:17 (for Datawarehouse4: we do a full backup every Sat morning. no diff backups. no log backups)
Last db log backup: None
I have had no luck still in recreating this, bar having the Recovery model change. Are you aware of any maintenance tasks or other jobs occurring at around the times that the alert is being raised (6:00 AM or 15:30 PM)?
Are you able to provide any details of what the loading process entails (process, scripts, etc)? If it isn't changing the recovery model (which I wouldn't expect it to switch from simple either, but you never know) then something seems to be causing Monitor to think it has and I need to know what that is so I can reproduce the issue.
Comments
I have tried various ways to get SQL monitor to create a 'log backup overdue' alert for a database using the simple recovery model but have not had any success. It would only alert after I had switched the database to Full recovery model (and performing some action) before switching back to the simple recovery mode. Can you provide any further details (sql server version, logs from sql monitor, screenshot of the properties > options section for the specified database, etc)?
Kind regards,
Alex Bartley
Product Support Engineer
Have you visited our Help Center?
Thanks for getting back to me.
SQL Server Version:
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
May 14 2014 18:34:29
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
Screenshots and Logs
https://www.dropbox.com/sh/4y5hrpd8se85 ... iyV0a?dl=0
You asked for "logs from SQL Monitor". I couldn''t find any way to export logs from SQL Monitor, so included a screenshot of the alert details
previous post about this:
http://www.red-gate.com/messageboardold ... 37afdffe00
Hope that helps. If you need any more let me know.
Craig
Can you also check the Properties > General page tab for Datawarehouse4 and check the timestamps for both backup and log backup there (screenshot or otherwise)? I just want to ensure there isn't some errant process occurring that is switching between the different recovery modes for some odd reason. I'll continue replicating your setup as I can in the meantime.
Kind regards,
Alex Bartley
Product Support Engineer
Have you visited our Help Center?
Last db log backup: None
I have added the screenshot to dropbox:
https://www.dropbox.com/sh/4y5hrpd8se85 ... iyV0a?dl=0
I have had no luck still in recreating this, bar having the Recovery model change. Are you aware of any maintenance tasks or other jobs occurring at around the times that the alert is being raised (6:00 AM or 15:30 PM)?
Have you visited our Help Center?
Are you able to provide any details of what the loading process entails (process, scripts, etc)? If it isn't changing the recovery model (which I wouldn't expect it to switch from simple either, but you never know) then something seems to be causing Monitor to think it has and I need to know what that is so I can reproduce the issue.
Alternatively you can just disable that Alert for the affected databases (http://documentation.red-gate.com/display/SM4/Configuring+alerts).
Kind regards,
Alex
Have you visited our Help Center?