It seems that Open Source Db are taking edge over relational and Commercial DB like Oracle and Sql
Does it mean after 10 years Sql will not be at all there in Market (Microsoft is making sure to make it more and more costlier with every version) or it will be there but with very few client which in turn will reduce overall Jobs in Sql
My company is switching to Opensource same happend in my previous company as well
They are telling me to become a full stack developer instead I want to move ahead and become a BI developer
I am very much worried now as to where should I go ahead become a Full stack developer or try for a BI developer
I had a 5 years of experience In sql sserver
This question comes up quite a bit. There's no right answer. I don't think SQL Server is going away anytime soon. Also see http://db-engines.com/en/ranking
It's worth bearing in mind that once an organisation decides to go with database X it's very hard, expensive and unpleasant to decide to go to database Y. There has to be a compelling reason. So if you make yourself an expert in a given technology while everybody else becomes Jack-of-all-trades in whatever happens to be flavour of the month, you can actually become pretty indispensable.
answered May 10, 2016 at 01:14 PM
Depends on what you mean by OS databases, if you're referring to NoSQL, do not buy-in to the idea that NoSQL is a replacement for relational databases. The two are very different. Have a look at the term polyglot persistence by Martin Fowler, which addresses the issue of impedance mismatch.
There will always be a place for relational databases, however it will be in support of additional databases. Try writing SQL to traverse relationships and tell me how many degrees of separation there is between you and I on facebook or twitter. Doing this in a relational database is very hard, yes you can do it, but it is hard. Do the same operation in a graph database and it is easy.
Should you store cost data in a graph database? Well graph databases have acid compliance so surely you can, you could but it would be silly. You want both to support each other. If your application has many half completed orders, dont store it in a relational database as you will need to NULL all the columns, store it in a documentDB.
The ethos of polyglot persistence is picking the right tool for the job. Dont just pick a relational database because you can.
Both @GPO and @SQLShark have great answers (+1 to both). I just want to add one other point. SQL Server 2016 will be officially released in 12 days, on June 1st. Microsoft is investing a lot (billions?) in the technology platform. They don't believe it's going away, and nor do I.
Okay. I'll add another point, lol. When you say "open source", it sounds like you're comparing an opensource database engine to that within SQL Server. But the engine itself is only part of the picture. With SQL Server, you also get an ETL tool (SSIS), a reporting tool (SSRS), an analytics engine (SSAS), scheduling (SQL Agent), integration with .NET (CLR), and more. Sure, some of those things could be obtained through other opensource projects or by purchasing less expensive options, but then the developers would need to learn a set of products that may or may not always work well or be supported together.
answered May 20, 2016 at 02:36 PM
Tom Staab ♦