Understanding different career options and employer requirements with SQL Server

  • I am trying to understand the different career options with SQL Server. I don't regret making the move from Access, but there is a lot to learn and the various paths are a little confusing for me at the moment.

    I went on a T-SQL course a few weeks ago as I was told that this is the most important aspect of SQL Server, but I am trying to do the rest on my own as I can't afford the general pricing of these courses. After T-SQL and knowing how SSMS works, I guess there are some possible next steps:

    - Move to .NET and using VS to develop bespoke applications - a developers job? This looks as though it will take a long time and I would rather delay getting overly involved in .NET and VB.NET/C#.NET development for now. I used an Access form as a front end for one database so can use that in the meantime if necessary as a temporary replacement for .NET.

    - Business Intelligence. It seems logical to start with SSRS. It looks as though employers are asking for a combination of SSRS, SSIS and SSAS. This may be a logical next step and then maybe SSIS followed by SSAS.

    - Look at what a DBA does - I am not sure I really understand this or the division between DBA and developer and how the business intelligence people fit in? Would it be possible for someone to clarify this for me as I'm a little confused about what I should be doing training wise.

    What I am doing now is continuing to work on T-SQL while getting to know SSRS and just very briefly delving into SSIS and SSAS. I don't know if that is enough or where that would categorise me in the job market.

    The danger at this stage is trying to learn too much and therefore not learning anything properly at all, however, I need to respond to the requirements of the job market and understand what these categorisations mean and where I should be heading.

    Many thanks for any advice.

Viewing 0 posts

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