We’ve started to hear this term coming up more and more as we meet with clients and partners – and while there isn’t a consensus on just what it means there are some definite benefits to exploring the concept sooner than later.  For most of our clients what moving anything to a “Service Model” means is that they can provide a consistent, controlled and scalable platform that allows them to react more quickly – and at a lower cost – to their (internal or external) customers needs.  Given the continued rapid growth of data within most organizations, looking at Database as a Service makes perfect sense in this context.

If your organization has siloed deployments – especially those with uneven utilization patterns – then you may already be looking at a database consolidation project.  Consolidation will give you better overall utilization, and planned properly can significantly lower both upfront capital costs as well as your on-going operating costs. In the process of consolidating, taking the extra step to plan out the platform as a “service” will help you understand how to continue to reap those benefits going forward – by including the provisioning, decommissioning and performance management capabilities into your consolidated infrastructure and processes.

Simply put – Database as a Service is a well-planned, forward looking consolidation effort.  It can live in your current environment, an internal private cloud – or in some cases in a public cloud setting.  The exact details of how your enterprise can best take advantage of this model depend on your specific situation.  That takes planning – but it isn’t rocket science.

We help clients with consolidation, virtualization and moving to a services model – we even wrote the book on some of the key tools, such as Oracle Enterprise Manager 12C Cloud Control, that get you there.  Figuring out what Database as a Service means for your organization starts with a conversation – one that can pay off with significant savings and happy customers.