30 November 2017
30 November 2017

Support for static data added to Source Control for Oracle

With the speed of software development increasing, more and more companies and organizations are recognizing that version controlling code is becoming as important for databases as it is for applications.

In recognition of this, Source Control for Oracle has been upgraded so that it now version controls static data within databases as well as database schemas.

Version 4 which has just been released links Oracle databases to source control servers like Git, Subversion and Team Foundation Server. Importantly, it now stores and shares reference data like lookup tables and metatables, enabling them to be version controlled alongside database code.

While a relatively small change, this is also an important one because everything necessary to update an Oracle database from its current state to the desired state can now be handled with the same version control platform used for applications.

This has been a widely requested feature because development teams want to optimize the way they update both their applications and their databases. With the new feature, Source Control for Oracle now can be used to deploy schema and static data changes within one tool.

The functionality is already a popular feature in SQL Source Control and the update puts Oracle users on a par with SQL Server users. This was another major driver for the change, because an increasing number of companies now use different database platforms to address varying business requirements. Users can now, for example, move from SQL Server to Oracle and still work with tools they are already familiar with.

It also means that if companies want to standardize their approach to database development by, for example, introducing DevOps practices like version control, they can do so across their whole estate of both SQL Server and Oracle databases, and have every team working in the same way.

Redgate’s State of Database DevOps Survey, released earlier this year, revealed that 80% of companies and organizations will have started applying DevOps practices to their software delivery within the next two years.

The upgrade of the Source Control for Oracle tool means that, whether SQL Server or Oracle – or a mixture of the two platforms – is the database of choice, it can still be included by starting the journey to DevOps with version controlling the database.

If you’d like to link your Oracle database to your source control server and ease database source control with Git, SVN and TFS, download a free and fully-functional 28-day trial of Source Control for Oracle.

Tools in this post

Source Control for Oracle

Easy database source control with Git, SVN and TFS.

Find out more

Share this post.

Share on FacebookShare on Google+Share on LinkedInTweet about this on Twitter

Related posts

Also in Hub

Finding code smells using SQL Prompt: procedures that lack schema-qualification

SQL Prompt implements a static code analysis rule, PE001, which will check code automatically, during development and testing work, for occurrences of a stored procedure being called, via the EXECUTE ...

Also in Product learning

How SQL Monitor Monitors Azure-based SQL Server Failover Cluster Instances

If you're working with SQL Server, one of the most appealing features of cloud-based computing services, such as Azure and AWS, is that they make it so much easier to design systems that are both high...

Also about static data

How to deploy a database plus static data using SQL Compare and SQL Data Compare

We can use the SQL Compare Pro command line with PowerShell to automate the process of creating a new build script for a version of the database, from the object scripts in the VCS. However, what if w...