Technologies such as Hibernate, nHibernate, Linq, etc, etc have actually made good RDBMS DBAs and Developers much more in demand to fix all the performance problems those technologies leave in their wake.
The cloud isn't really changing the need... it's just changing the topography a bit. You still need people who actually know what they're doing with a database if you intend to do any batch processing or heavy duty lookups.
Shifting gears... the idea of handling data hasn't changed since the stone age. Even the methods have stayed pretty much the same. The only thing that has changed is some of the tools. The stuff I learned about data handling back in the 60s still applies today. It all boils down to 3 simple things... Input, process, output. Make any one of those 3 slow or inaccurate and your customers will see that you have hell to pay. It's not rocket science and the cloud really doesn't change any of that.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs