NEWBIE TO THE DBA LIFE

  • Hello ALL,

    I apologize if I'm posting this in the wrong section just didn't know where to post it (moderators please remove if needed).

    Just wanted to introduce myself to everyone, I already posted some questions without doing this so I felt it was necessary. 😉

    Just started my new job as Jnr Dba in a company in the UK (realized most users here are from the US I think) less than 6 months ago, this is my first role involving pure database & sql issues, prior I was doing mainly support and within 3 months I would nearly know everything about the role more or less, whereas now I'm currently still struggling with a lot of stuff (sprocs, tempdb issues, cpu usage, buffer pool, deadlocks, etc you name it it's there) :hehe::crazy:

    Not sure if that's normal but I do enjoy the role & I'm willing to learn more, I was wondering if you guys could give me any tips or directions that I could follow apart from you know just tackling each day as it comes and visiting forums & internet for help.

    I do want to learn everything I can but there's no exact guideline so one day I'm learning this & the following day something else so I do wonder if I'm doing it in the right way, I want to be a contractor eventually one day, so I wonder if I should specialize on something specific when it comes to database (security, administration, development) or just try learn a bit of everything and gather as much information as possible.

    Well basically what I'm saying it's if you have any tips on how you've become a full, snr or principal DBA etc, what I should do or learn....and enhance my skills

    Thank you in advance & apologies if I posted in the wrong section.

    Any tips at all will be appreciated.

    To know where you're heading, you gotta know where you been :alien:

  • Start with learning how to live up to your formal job description. Ask your immediate supervisor what's expected of you in terms of roles. You don't want to focus on something you're really interested in (like T-SQL development or building SSRS reports) when you're primarily responsible for backups and monitoring.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • Eric M Russell (11/16/2016)


    Start with learning how to live up to your formal job description. Ask your immediate supervisor what's expected of you in terms of roles. You don't want to focus on something you're really interested in (like T-SQL development or building SSRS reports) when you're primarily responsible for backups and monitoring.

    Hello Eric, thank you for your answer, well yes that was the initial stage, making sure I understand the backup process which I now manage mainly by myself & to monitor of any failures of jobs in all the different servers, however now it's more of a look at any live issues come over from other teams which can be anything; from blocks to latency, replication on old sql server version, high cpu usage etc. so it's a jungle lol

    To know where you're heading, you gotta know where you been :alien:

  • I strongly recommend getting a copy of Craig Mullins book: Database Administration. It covers the job, as a job. It's technology agnostic. It'll give you a more complete picture of what the role may entail. It also does a great job describing all the variations available within the position.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Oh, and welcome to the party.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Another book I'd suggest would be "Troubleshooting SQL Server: A Guide for the Accidental DBA"

    You can get the PDF for free from Red Gate (disclaimer: I don't work for Red Gate) or purchase a paper copy (which I'd actually suggest, much easier to browse through)

    And as Grant said:

    Welcome to the party!

  • Grant Fritchey (11/16/2016)


    I strongly recommend getting a copy of Craig Mullins book: Database Administration. It covers the job, as a job. It's technology agnostic. It'll give you a more complete picture of what the role may entail. It also does a great job describing all the variations available within the position.

    Thanks for the suggestion Grant, appreciated

    To know where you're heading, you gotta know where you been :alien:

  • jasona.work (11/16/2016)


    Another book I'd suggest would be "Troubleshooting SQL Server: A Guide for the Accidental DBA"

    You can get the PDF for free from Red Gate (disclaimer: I don't work for Red Gate) or purchase a paper copy (which I'd actually suggest, much easier to browse through)

    And as Grant said:

    Welcome to the party!

    Thank you Jasona, appreciate the help.

    To know where you're heading, you gotta know where you been :alien:

  • Welcome to the party, indeed. 🙂

    A couple of other suggestions.

    There's a 6 month DBA training by email thing from Brent Ozar (one email a week, every week). https://www.brentozar.com/needs/

    The "DBA Survivor" book by Thomas LaRock

    The "Become an Exceptional DBA" book by Brad McGehee (ex-Redgate) (free PDF)

    The books are not technical, but should get you into the right mindset. The training plan contains exercises that are firmly based in reality.

    Thomas Rushton
    blog: https://thelonedba.wordpress.com

  • ThomasRushton (11/17/2016)


    Welcome to the party, indeed. 🙂

    A couple of other suggestions.

    There's a 6 month DBA training by email thing from Brent Ozar (one email a week, every week). https://www.brentozar.com/needs/

    The "DBA Survivor" book by Thomas LaRock

    The "Become an Exceptional DBA" book by Brad McGehee (ex-Redgate) (free PDF)

    The books are not technical, but should get you into the right mindset. The training plan contains exercises that are firmly based in reality.

    Thank you Thomas appreciate the suggestions. Currently reading the PDF by Brad seems very interesting

    To know where you're heading, you gotta know where you been :alien:

  • I also am pretty new to the SQL DBA world. Besides the Accidental DBA book mentioned in this thread, I found Beginning SQL Server 2012 Administration by Walters & Fritchey very helpful. If you are interested in how the Database Engine works, I suggest watching Kevin Kline's SQL Server Internals video: https://www.youtube.com/watch?v=34VqSliEfsc

    That really helped me understand how data flows. My drive to work is about 40 minutes, so I listen to the Brent Ozar Office Hours Podcasts. The amount of resources are endless, and the community loves to answer questions.

  • One thing I have found of most successful DBA's is that they never stop learning, they never stop pushing the envelope of what they know. Knowledge is power. 😎

    For the older (ahem) peeps amongst us, be like Johnny Five (input-input-input!). 😀

    qh

    [font="Tahoma"]Who looks outside, dreams; who looks inside, awakes. – Carl Jung.[/font]
  • quackhandle1975 (1/3/2017)


    be like Johnny Five (input-input-input!). 😀

    qh

    Watched that with S.O. and a few years later brought up the input like and she did not know what I was talking about.:-D

  • Grant Fritchey (11/16/2016)


    Oh, and welcome to the party.

    This is a party?? - it feels more like a funeral wake ! 😀

    +1 to the books mentioned

    -------------------------------Posting Data Etiquette - Jeff Moden [/url]Smart way to ask a question
    There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan
    I would never join a club that would allow me as a member - Groucho Marx

  • I realize this post has been around for a while but my recommendation is that if you want to be a really good DBA, you'd better be really good at T-SQL.

    --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)

Viewing 15 posts - 1 through 15 (of 16 total)

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