How can we help you today? How can we help you today?

Bugs in 5.0.3

in read only login mode the Alerts screen doesn't display correctly with the data details in the wrong columns. Each column has data meant for the column to the right of it!

Databases in Simple recovery mode generate the Log Backup Overdue message - this includes Master even though the description of the error states "It will not be raised for the master database. "
VoiceOfRock
0

Comments

5 comments

Sort by
  • Alex B
    Hi VoiceOfRock,

    The first issue with Read-only users is known with reference SRP-10168 and has been fixed to be released in v5.0.4.

    I have not been able to replicate the issue of databases in Simple recovery mode (nor the master database) creating log backup overdue alerts in 5.0.3 with SQL 2012 and 2014 - only those currently in full backup recovery mode are creating this alert (I started a db off in full and changed to simple and it still correctly doesn't create the alert). What SQL version are these datases in? Can you run:
    select name,recovery_model_desc as Recovery_mode from sys.databases order by name

    And ensure they are listed properly as FULL/SIMPLE?

    Kind regards,
    Alex
    Alex B
    0
  • VoiceOfRock
    Hi Alex,

    Hopefully you've received a few direct emails with screenshots.

    3 servers on 2008 Std Edition and one on 2008R2 Std are affected.

    all are Simple and have Full backups each night.
    VoiceOfRock
    0
  • Alex B
    Hi VoiceOfRock,

    Yes I merged the call from this post into your original call and will update here with the outcome afterwards.

    Kind regards,
    Alex
    Alex B
    0
  • NCstyle
    I can also verify the bug with DBs in Simple mode alerting for Log Backup Overdue. It's occurring on two of my servers which are both SQL 2012, but it doesn't occur on all of my SQL 2012 servers. So it doesn't appear to be tied to the SQL version.
    NCstyle
    0
  • Alex B
    Hi NCstyle,

    What OS version are you using with these servers? The only way we've been able to get a similar behaviour so far is to temporarily switch the recovery model to FULL then back to SIMPLE so want to ensure this isn't the case (seems unlikely but need to be sure). We are still looking into other reasons as well!

    Kind regards,
    Alex
    Alex B
    0

Add comment

Please sign in to leave a comment.