General discussion


Making the move from Business Analyst to Systems Analyst / DBA

By kilbey1 ·
My official title is "Business Systems Analyst." I started out as a designer in 1995, moved into development for several years, about a year of project management, 6 months as a system analyst, and eventually into the analyst role around 2006.

I have identified that my passion is working with data. Typically, that means digging into the database, analyzing the problem and coming up with solutions. That's a wide area, but it may mean resolving an issue in production support, creating custom SQL for a Business Objects report, setting up test cases in SQL, or validating an ETL job between databases (but not performing the ETL job itself). I have personally created complex queries in Oracle, MySQL and SQL Server, and am aware of some of the major differences between each platform.

I am looking to move into a Systems Analyst role, with the emphasis on 'Systems'. This could mean as a technical business analyst, a systems analyst, or a DBA. I already know that I need to beef up my PL/SQL. Apart from that, what other recommendations could be made to successfully make the transition? I am especially looking for technologies that might be carried across DB platforms. What do employers look for in today's DBA?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Security and Roles for one

by b4real Contributor In reply to Making the move from Busi ...

On access to data. Very important to be able to configure very explicit security models for data access and roles.

Collapse -

Well if you want to sell yourself as an Oracle DBA

by Tony Hopkinson In reply to Making the move from Busi ...

you need all their certs, which is an expensive do at best. Personally I'd concentrate on Database Design, then look at implementation. Far too many make the mistake of thinking SQL is database design it isn't, it's the language you describe or use your design in.

Look at it this way, if the query is complex
then the database isn't designed to do what you want. That can of course be perfectly reasonable, better to make that choice deliberately though as opposed to by accident.

Collapse -

What's wrong with...

by jmgarvin In reply to Well if you want to sell ...

having to do a left outer join just to see who created a record? ;-)

Really though, you are dead on. I'd also suggest trying to get the MS SQL certs as well as the Oracle (so you are a little more platform agnostic).

Also, keep in mind that Oracle is not databases, it is a product. There are other products that do the same thing, some better, some worse....

Collapse -

A good friend of mine is an Oracle DBA

by Tony Hopkinson In reply to What's wrong with...

It cost him a fortune. It's precisley the product aspect of Oracle that fills me with misgivings. We all know knitting together that many different functions gives rise to all sorts of nasty compromises. We all know that unless you spend a lot on the initial design , get it nearly right and put a lot of resource into keeping it right, all you get is more and nastier compromises.

Given a choice I won't go near the thing.

I did do support and development on MySQL, SQL Server and Sybase in past roles and I'm much stonger than your average developer on the DBA front, I wouldn't decscribe myself as a DBA though.

Related Discussions

Related Forums