As database environments evolve, so does the role of the database administrator (DBA). Take the movement to the cloud, for example. While it automates some tasks, like OS patching and backups, and frees up DBAs’ time, data governance, security and privacy become even more critical. And because businesses are demanding higher velocity at a lower risk, this ushers in a cultural change: DevOps, where developers and DBAs must collaborate more closely than before.

While migrating Oracle applications from physical to virtual OVM environments can be straightforward, it is important to take into consideration configuration issues regarding the interaction of the Operating System environment to the Virtual Environment. There are some gotchas that can complicate an installation despite assiduous attention to the installation and migration instructions. Figure 1 shows what a typical Oracle VM implementation may look like.

Over the coming weeks, SELECT and DBTA will be collaborating on a series of articles that have DevOps as their core theme. Like so many other buzz words in Information Technology today, there is no single agreed upon definition that has been set forth for DevOps, so the editors at SELECT decided that before we publish articles on DevOps, we should first describe what we view DevOps really means.

The concepts of Agile methodology and continuous delivery have become popular in software development, yet they are somewhat less mature among DBAs and database developers. Joyce Wells, editor at Database Trends and Applications (DBTA), spoke with Shay Shmeltzer, director of product management for Oracle Cloud Development Tools, to discuss how DBAs and SQL developers can take advantage of newer development approaches while also dealing with the unique challenges that exist in the world of database development.

Every now and again I come across the question: How can we lower latency and speed up data delivery? Irrespective of the target database, the desirable answer for the person responsible for implementing the data integration strategy may be to employ parallel processing. However, in many cases the decision to parallelize is the best answer only if better options have first been exhausted, and organizations don’t always explore those options.

Oracle introduced the autonomous database in the Oracle Cloud this past March of 2018. It is set up for data warehouse-type workloads and not yet for heavy transactional systems or even hybrid-type applications. As a Database Administrator (DBA), we know that most of our applications have hybrid to heavy transaction workloads, and of course a few data lakes or warehouses. Well, good news — on August 7, 2018, Oracle announced and made immediately available Oracle 18c autonomous database in the Oracle Cloud for transaction processing.

Check out this case study from Southern Utah University about how the university moved its entire infrastructure to the Cloud.

In an age where increased productivity is the gold standard, DBAs continuously seek new ways to become more efficient in their daily work. Amazon Web Services (AWS), an IOUG partner, recognizes this need and recently announced two new features to reduce and optimize vCPUs on the Amazon Relational Database Service (Amazon RDS) for Oracle Database.

Whether you’re an Oracle system/database administrator, an IT manager/executive or even just an end user/customer, security should be a key focus. Security breaches have happened at all levels within the industry. From the executive level to the end customer whose data is leaked, none of us want to be associated with a breach.

While you may or may not be considering a cloud migration or implementation of the Autonomous Cloud Data Warehouse via a Proof of Concept (PoC) or even a flushed-out roadmap, that activity is likely future looking or at best a work in progress. Security concerns are immediate, as well as future-facing.

So are there action items we can take right now? The answer is definitely yes!