• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Looking to get into SQL DBA .. Advice ?

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    Looking to get into SQL DBA .. Advice ?

    Hi,

    I have been contracting for around 5 years, like most worked my way up from desktop support. Currently working as a network administrator.

    I am looking to take the next step in my career, the easiest and most logical would be to stay in Networking. But i feel the way the market has been the last few years .esp cisco contracts. i should take the plunge to another field. i.e. SQL DBA.

    Therefore over the last year i am on the verge of completing my MCSE. Next step would be to do MCDBA maybe MCT in SQL 2005.

    The question : How hard is it to break into the SQL job market with little experience ? Even if its a JR roll ?

    Also, developer or DBA ?

    Thanks for your help.


    #2
    QUOTE=UKContractor83;660236]Hi,

    I have been contracting for around 5 years, like most worked my way up from desktop support. Currently working as a network administrator.

    I am looking to take the next step in my career, the easiest and most logical would be to stay in Networking. But i feel the way the market has been the last few years .esp cisco contracts. i should take the plunge to another field. i.e. SQL DBA.

    Therefore over the last year i am on the verge of completing my MCSE. Next step would be to do MCDBA maybe MCT in SQL 2005.

    The question : How hard is it to break into the SQL job market with little experience ? Even if its a JR roll ?

    Also, developer or DBA ?

    Thanks for your help.

    [/QUOTE]


    If you accept very low rates than easy. easier to break into development than dba as the former allows u time but in the latter if a disaster occurs and your on cover...

    With Sql developer you will be more and more required to know an additional skillset for front end ie .Net/Asp etc

    And do MCT in 2005 not MCDBA in 2000 as thats getting out of date

    Comment


      #3
      I'm a SQL DBA and I got into it by doing a job supporting an enterprise application written by a software company that used SQL Server at the back end. So inevitably I got involved in DBA'ie type things so gaining that experience.
      That was in the days I was permie though.
      Yes 2000 is dying. Go for 2005 or 2008.

      Comment


        #4
        Originally posted by KentPhilip View Post
        I'm a SQL DBA and I got into it by doing a job supporting an enterprise application written by a software company that used SQL Server at the back end. So inevitably I got involved in DBA'ie type things so gaining that experience.
        That was in the days I was permie though.
        Yes 2000 is dying. Go for 2005 or 2008.
        WHS, started supporting an application with SQL 6.5 as backend and was a DBA through SQL Versions and some DB2 and teeny bit of Oracle for 10 years.

        Pay can be good but it's very steady eddie work so don't expect excitement unless everything dies and you are single handedly responsible for saving the company!

        Comment


          #5
          You might wanna consider the path I am taking (of least resistance) which is moving away from the DBA side of things to the SQL Server Business Intelligence stuff.

          You gotta do the Reporting Services, the Analysis Services, then the Business Intelligence courses and exams. Its more development than DBA.

          Comment


            #6
            I know it's OT and unhelpful, but I really really do wish that people would not say SQL when they mean SQL Server. I'm not just being pernickety, it's because it screws up searches (which is probably what MS had in mind).
            Last edited by expat; 23 October 2008, 07:38.

            Comment


              #7
              Originally posted by expat View Post
              I know it's OT and unhelpful, but I really really do wish that people would not say SQL when they mean SQL Server. I'm not just being pernickety, it's because it screws up searches (which is probably what MS had in mind).
              Its derived from Sybase SQL Server

              But, thats beside the point, I agree with you about shortening Microsoft SQL Server to "SQL" and I really hate it when agents do it
              Coffee's for closers

              Comment


                #8
                Originally posted by Spacecadet View Post
                Its derived from Sybase SQL Server

                But, thats beside the point, I agree with you about shortening Microsoft SQL Server to "SQL" and I really hate it when agents do it
                Yes: have "SQL" anywhere on your CV, and you will keep getting calls for SQL Server DBA roles

                Comment


                  #9
                  Originally posted by Stan.goodvibes View Post
                  You might wanna consider the path I am taking (of least resistance) which is moving away from the DBA side of things to the SQL Server Business Intelligence stuff.

                  You gotta do the Reporting Services, the Analysis Services, then the Business Intelligence courses and exams. Its more development than DBA.
                  I quite fancy doing that as I find that being a SQL Server DBA to a bit too quiet for my liking. Grabbing Business Objects experience seems like a good route to go down too.

                  Comment


                    #10
                    Originally posted by crimdon View Post
                    I quite fancy doing that as I find that being a SQL Server DBA to a bit too quiet for my liking. Grabbing Business Objects experience seems like a good route to go down too.
                    Yeah I have a developer background but have done a lot of T-SQL and BA database design stuff and prefer that to coding.

                    I'd be interested to hear from anyone who wants to comment on the availability of contracts for MS Business Intelligence

                    Comment

                    Working...
                    X