SQL failover Issue

  • Hello Friends,

    There was a failover on my sql server clustered enviornment . Now I am just wondering if there is anyway for me to find out about this failover…When it happened? Why it happened? Was it manual or Automated failover..

    I did check the sql logs but notice only the sql start date and time and I am assuming that that’s the time when the failover happened..Is there any better way to get the information I mentioned above ?

  • keep in mind the sql server errorlog file is archived ( to errorlog.1 ) every time sqlserver starts or one performs a cycle errolog.

    Chances are you only got to see the current errorlog file.

    Also check the windows eventlog files and the cluster server log file.

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • As mentioned by Johan, the best bet is to look for Windows Event logs around the time frame when the failover happened, to know when the failover happened, there are multiple ways to find.

    Either from SQL Server error log(s) (but not always true as the error log can be recycled). You can also find from the Create date & time of the TempDB..


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • Thank you guys...that was really helpful!!

  • You are welcome !!!


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply