23 October 2017
23 October 2017

SQL Source Control v6 now supports SQL Server 2017, SQL Graph, and TFS 2018

SQL Server 2017 went on general release a couple of weeks ago and the latest version of SQL Source Control offers full support, as well as support for Team Foundation Server (TFS) 2018.

This brings a whole host of benefits and opens up cross-platform workflows, encompassing both on-premises and cloud, through connections to SQL Server instances on Linux and Azure Active Directory authentication.

This is good news if you work for an organization in which departments and divisions host their databases on various servers and systems, owned by teams in different geographical locations. You can continue working in the development environment you’re familiar with, using the tools you always use, only now you’ll have direct connections across the ever-changing server landscape.

Take advantage of SQL Graph

Microsoft SQL Server 2017 features the much-anticipated SQL Graph, which provides new graph database capabilities for representing complex many-to-many relationships. Social media platforms like Facebook and LinkedIn use graph databases extensively, and in the era of big data, use cases are emerging across many industries.

Businesses can explore these relationships to reveal valuable information, as you’re probably aware from changes in the types of structures and query abilities being requested of you and your teams. Whether it’s identifying similarities in customers behind trends in purchasing behavior, or mapping patterns in credit card usage to determine credit limits or risk indicators of defaulting on repayments, the introduction of graph capabilities to SQL Server makes the processes more streamlined.

Today’s release of SQL Source Control v6 joins Redgate’s recently released SQL Compare v13 in fully supporting SQL Graph, so if you’re experimenting with SQL Graph databases, or getting more BI requests through, you can now use a single query across relational and graph database objects, and deploy updated databases with the tools you know and love.

That’s not the end of the story

SQL Source Control v6 also delivers lots of improvements to user experience and workflows, many of which came about as suggestions from you in our Redgate Community Hub. Importantly, it does so with a much smaller footprint, thanks to an overhaul of the entire codebase, resulting in better stability overall.

You can happily explore all the new features in SQL Server 2017, knowing the industry standard for version controlling your databases won’t let you down. To find out more about the improvements in SQL Source Control v6, take a look at our release notes.

And to learn why it’s important to version control the database, read our recent blog post, Six reasons to version control your database.

 

Share this post.

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

You may also like

  • Article

    Merging a Conflict with SQL Source Control and Beyond Compare

    SQL Source Control (SoC) plugs directly into SQL Server Management Studio (SSMS) and is built with the singular purpose of providing an efficient interface between each developer’s local, working copy of the database, in SSMS, and the source control repository. It allows each developer to work freely, on their own sandbox database, committing tested changes

  • Article

    How to version control a database using GitHub and SQL Source Control

    Are you interested in version controlling your SQL Server database in GitHub? This article explains some simple steps to create a GitHub database repository and get your database code in there, using SQL Source Control. I assume you’re a SQL Server professional and don’t need a deep dive into how source control systems work, nor

  • Article

    Source controlling your database permissions

    The problem A common question we encounter when working with SQL Source Control is about database permissions. Different environments require different permissions, so should you just omit them entirely from Source Control? Or perhaps include only permissions for your production environment? Permissions are extremely important, so not source controlling them at all doesn’t seem right;

  • Article

    Versioning an existing database using SQL Source Control

    A while ago, maintaining a reliable database change history was an ongoing problem within our development team. It seemed we were forever asking questions such as “Who made this change?”, “When was the stored procedure last edited?”, “When was this view created?”, and so on. Our initial approach was simply to store a list of

  • University

    Take the SQL Source Control course

    This course takes you from installation all the way up to getting the most out of the advanced operations in SQL Source Control to help you set the foundations for CI/CD. Learn how to link a development database to your source control system, commit changes into a repository, produce a data deployment script, and more.

  • Forums

    SQL Source Control Forum

    Connect your databases to your source control system