• Alejandro Santana - Tuesday, March 6, 2018 1:44 PM

    Hello!

    I'm fairly new to SQL Server and i have been wondering if you guys masters, professionals who have been in the IT Field as DBA for years give me some kind of idea or ideas for reports and health checks for everyday routine.
    ¿What kind of health check you guys do everyday, weekly or monthly to your SQL Server Database?
    ¿What kind of reports you guys made to check for instant diagnostics besides the SQL Server Log?

    Sorry for the english if misunderstood something, my native language is spanish.

    Greetings and thank you for your time.

    The absolute most important thing to check on is... did the backups work and are they viable for a restore.  Don't think of another thing until that's hammered down 110%.  Nothing else matters until that's guaranteed and the backups are on a different machine than the databases themselves  and any tapes are safely stored offsite.  That includes at least weekly test restores.  I do daily test restores (fully automated, of course).

    The second most import thing is to determine who has what privs.  Lock down the server.  Devs and other so called "super users" should not have privs to deploy their own code and access to data must be locked down lest you read about yourself in the morning news.

    The third most important thing is DBCC CHECKDB and it's not far behind backups/restores in criticality.

    All three things must be done in very short order and maintained at all times.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)