July 22, 2017 at 1:29 pm
I've recently come to a big career decision and thought the forum might be able to help.
A bit of background i'm 36 now, started my early days as C# programmer and then went into BI SSRS SSIS etc. not really SSAS.
Anyway fast forward 8 years I ended up not following the BI path but end up as a DBA at an e-commerce start up. The DB was a mess not one FK in sight . Anyway over the last 5 years I've got the DB(s) into a good state and recently started to manage a small team consisting of one other DBA and 3 software developers.
I am responsible for database architecture , database design , query optimization, a lot of SQL development (although ORMs are eating into that), and DBA duties, DR etc.. I'm well paid and really enjoy working there. The main database is my baby, I basically saved it and rebuilt it , optimized and rewrote a lot of logic into SP s etc. I'm involved in a lot business design decisions and meeting with different areas of the business. We practice SCRUM methodologies so there are no PMs BAs etc.
Anyway recently i was approached and offered a job in a different environment a corporate finance company and to work with Business Intelligence but managing no -one to start with.
Would it be a good career choice to pursue this business intelligence role , reporting, DWs, Tabular models etc (with training self and external) possibly Azure exposure? Therefore adding another notch onto my belt?
Or should i stay at a fun company as an Application DBA manager working on DB projects (schema design queries etc) managing a team? I feel I might stagnate only doing DBA related work even though I really enjoy it and like the company due to its google laid back non corporate vibe.
My main reason for the shift would be job security going forward , there seems to be lot more jobs in BI than DBA related roles where I live.
Thanks
D
July 24, 2017 at 3:34 am
Anyone? Maybe if someone has done this career shift can shed some light for me?
July 24, 2017 at 4:08 am
This is a question that only you can answer, I think. From here, it looks as if you enjoy the work, you enjoy the company and you're well paid, so why would you move? But there might be other stuff to consider, such as hours, holiday, commute. Or the pull of BI may be so strong that you can't resist. If you've never worked in BI before, you might consider doing a pet project at home, just to see whether you're really going to enjoy it.
John
July 24, 2017 at 11:54 am
John Mitchell-245523 - Monday, July 24, 2017 4:08 AMThis is a question that only you can answer, I think. From here, it looks as if you enjoy the work, you enjoy the company and you're well paid, so why would you move? But there might be other stuff to consider, such as hours, holiday, commute. Or the pull of BI may be so strong that you can't resist. If you've never worked in BI before, you might consider doing a pet project at home, just to see whether you're really going to enjoy it.John
Hi John,
Appreciate the reply. I have worked in BI before started there before being a DB engineer. I didn't enjoy it as much my current role. But the problem i'm facing is job security, the future of my current workplace is uncertain..I wont get into too much detail but where i live in is dominated by finance companies and all the current jobs listed are for BI skills not one for a DBA let alone DB developer/engineer. Everything seems to be bought off the shelf these days. So I'm just thinking down the line in 2 years what would happen if i had to leave my current company.
Thanks
July 24, 2017 at 12:22 pm
bugg - Monday, July 24, 2017 11:54 AMJohn Mitchell-245523 - Monday, July 24, 2017 4:08 AMThis is a question that only you can answer, I think. From here, it looks as if you enjoy the work, you enjoy the company and you're well paid, so why would you move? But there might be other stuff to consider, such as hours, holiday, commute. Or the pull of BI may be so strong that you can't resist. If you've never worked in BI before, you might consider doing a pet project at home, just to see whether you're really going to enjoy it.John
Hi John,
Appreciate the reply. I have worked in BI before started there before being a DB engineer. I didn't enjoy it as much my current role. But the problem i'm facing is job security, the future of my current workplace is uncertain..I wont get into too much detail but where i live in is dominated by finance companies and all the current jobs listed are for BI skills not one for a DBA let alone DB developer/engineer. Everything seems to be bought off the shelf these days. So I'm just thinking down the line in 2 years what would happen if i had to leave my current company.
Thanks
You may also want to see if there may be a small project you could pilot at your current company in the BI space. Never know, you may be able to make the change and stay where you are at the same time.
You just need to find something that would bring value to your company.
July 24, 2017 at 12:42 pm
I'm somewhat playing Devil's Advocate here, and all BI teams are different and subject to evolutionary change, but ...
The thing about working within the BI team, as opposed to being an enterprise-wide DBA or an application developer, is that you may be [unpleasantly] surprised by how little of your time will be spent on the more interesting technical aspects of databases. Do you enjoy two or three stand-up meetings per day? How about sitting through 2 hour long meetings listening to folks ruminate over the definition of "customer"? Another thing about BI is that they tend to use a lot of pre-built ISV databases and logical modeling tools that spit out database designs that are not very well engineered, and despite all your knowledge of SQL Server, you will have little influence over the architecture.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 24, 2017 at 12:47 pm
Eric M Russell - Monday, July 24, 2017 12:42 PMThe thing about working within the BI team, as opposed to being an enterprise-wide DBA or an application developer, is that you may be [unpleasantly] surprised by how little of your time will be spent on the more interesting technical aspects of databases. Do you enjoy two or three stand-up meetings per day? How about sitting through 2 hour long meetings listening to folks ruminate over the definition of "customer"? Another thing about BI is that they tend to use a lot of pre-built ISV databases and logical modeling tools that spit out database designs that are not very well engineered, and despite all your knowledge of SQL Server, you will have little influence over the architecture.
Definitely be careful of this, a lot companies that advertise BI openings really just mean build pretty looking reports.
July 24, 2017 at 2:03 pm
Lynn Pettis - Monday, July 24, 2017 12:22 PMbugg - Monday, July 24, 2017 11:54 AMJohn Mitchell-245523 - Monday, July 24, 2017 4:08 AMThis is a question that only you can answer, I think. From here, it looks as if you enjoy the work, you enjoy the company and you're well paid, so why would you move? But there might be other stuff to consider, such as hours, holiday, commute. Or the pull of BI may be so strong that you can't resist. If you've never worked in BI before, you might consider doing a pet project at home, just to see whether you're really going to enjoy it.John
Hi John,
Appreciate the reply. I have worked in BI before started there before being a DB engineer. I didn't enjoy it as much my current role. But the problem i'm facing is job security, the future of my current workplace is uncertain..I wont get into too much detail but where i live in is dominated by finance companies and all the current jobs listed are for BI skills not one for a DBA let alone DB developer/engineer. Everything seems to be bought off the shelf these days. So I'm just thinking down the line in 2 years what would happen if i had to leave my current company.
ThanksYou may also want to see if there may be a small project you could pilot at your current company in the BI space. Never know, you may be able to make the change and stay where you are at the same time.
You just need to find something that would bring value to your company.
Hey Lynn, this is what I'm negotiating now. To try and introduce power BI and Azure DW over qlikview. With the end goal being me convincing the board it better 😀
July 24, 2017 at 2:39 pm
Eric M Russell - Monday, July 24, 2017 12:42 PMI'm somewhat playing Devil's Advocate here, and all BI teams are different and subject to evolutionary change, but ...The thing about working within the BI team, as opposed to being an enterprise-wide DBA or an application developer, is that you may be [unpleasantly] surprised by how little of your time will be spent on the more interesting technical aspects of databases. Do you enjoy two or three stand-up meetings per day? How about sitting through 2 hour long meetings listening to folks ruminate over the definition of "customer"? Another thing about BI is that they tend to use a lot of pre-built ISV databases and logical modeling tools that spit out database designs that are not very well engineered, and despite all your knowledge of SQL Server, you will have little influence over the architecture.
Hey Eric, i do enjoy meeting and working with the business. I do this regularly now not only do I carry out DBA duties but also database design and development so meeting with the business constantly especially around new projects. Data does interest me a lot trends etc.
July 24, 2017 at 2:40 pm
ZZartin - Monday, July 24, 2017 12:47 PMEric M Russell - Monday, July 24, 2017 12:42 PMThe thing about working within the BI team, as opposed to being an enterprise-wide DBA or an application developer, is that you may be [unpleasantly] surprised by how little of your time will be spent on the more interesting technical aspects of databases. Do you enjoy two or three stand-up meetings per day? How about sitting through 2 hour long meetings listening to folks ruminate over the definition of "customer"? Another thing about BI is that they tend to use a lot of pre-built ISV databases and logical modeling tools that spit out database designs that are not very well engineered, and despite all your knowledge of SQL Server, you will have little influence over the architecture.Definitely be careful of this, a lot companies that advertise BI openings really just mean build pretty looking reports.
The job is to implement a reporting platform across all their different software/databases. however, yes it does involve developing pretty reports.
July 25, 2017 at 7:53 am
bugg - Monday, July 24, 2017 2:40 PMZZartin - Monday, July 24, 2017 12:47 PMDefinitely be careful of this, a lot companies that advertise BI openings really just mean build pretty looking reports.The job is to implement a reporting platform across all their different software/databases. however, yes it does involve developing pretty reports.
When I was looking for work a couple of months ago I found that, for a lot of companies, BI means just building the pretty reports and not working with the rest of the platform.
I'd suggest not switching just out of fear. Take the opportunity to figure out what you really like doing with SQL Server and following that path. When I was laid off, I took that as an opportunity to figure out what I really wanted. I then switched my pitch from "Senior BI Developer" to "development DBA / architect with a specialty in building BI solutions" as I found the database design and development (both applications / DW) to be what I enjoy the most.. Found something more in line with my long term goals.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply