7 August 2017

1 Comment

7 August 2017

1 Comment

New permissions features brings access control to SQL Clone

SQL Clone permissions give you simple control over who can access SQL Clone, and what they can do with it.

Ever since its launch, SQL Clone has been attracting waves of interest. By allowing SQL Server databases or backups to be cloned in seconds, as well as saving up to 99% of disk space, it removes the burden of database provisioning.

What about access, though?

Let’s say you have a mixed team of database developers, application developers, and BI analysts. All of them at some point may want a copy of the database. Maybe to test their changes against, try out a new feature, or identify a problem with a current feature.

At the same time, however, you probably don’t want a whole flock of users having full access to SQL Clone. If you have a large estate, for example, or many different environments, or environments that change frequently, it can result in a sprawl of images and clones created at different times from different versions of the database.

To address this, the latest version of SQL Clone includes role-based permissions.

What role are you?

The SQL Clone permissions feature now lets you award users one of three roles – and change and update them in future, literally at the click of a button:

SQL Clone permissions 1

The Admin role gives full control over SQL Clone, with the ability to add, change or remove roles, update licenses, and create images or clones. You might want to restrict this role to Database Administrators (DBAs) or Systems Administrators.

The Standard role allows users to create images and then create clones from those images. Perhaps that’s appropriate DBAs or lead developers.

The Clone only role limits users to creating images from clones. In the example, given earlier, this might apply to BI analysts or the rest of the development team.

Want to choose roles by user or group?

To make it easier, you can also apply permissions across groups using Active Directory:

SQL Clone permissions 2

In larger teams which see a changing roster of members, this is particularly valuable and lightens the load of managing access to SQL Clone yet further.

It also means that, even if you have different users or groups requiring different levels of access, you can still introduce a self-serve process, knowing that the role they have been designated will limit what they can do and prevent that sprawl that could otherwise occur.

Summary

SQL Clone permissions has been high on the wish-list for users and the new feature addresses it in an intuitive way that enables you to allocate and change permissions quickly and easily. To try it out yourself, go to Settings | Permissions from within SQL Clone.

If you’re new to SQL Clone and would like to discover this feature and the many others it offers, download a 14-day, fully-functional free trial.

SQL Clone permissions 3

Tools in this post

SQL Clone

Clone SQL Server databases in seconds and save up to 99% disk space.

Find out more

Share this post.

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

You may also like

  • Webinar

    Does your current provisioning process meet regulatory requirements?

    DevOps practices, applied to the database, aim to allow organizations to deploy databases at the frequency they need, without introducing an unrealistic administration burden, and without compromising that organization’s compliance with data privacy or security regulations. In this webinar, Product Manager Richard Macaskill explains how to incorporate Redgate’s new SQL Provision into your Database DevOps

  • Webinar

    Global Data Privacy Tales: The GDPR Effect

    Our expert global panel will be discussing what’s happened worldwide since the GDPR came into force one year ago. Discover how legislation has changed around the world, which companies have been caught out, who’s been fined, and what’s likely to come up in the year ahead. 

  • Article

    Create, protect and manage non-production databases with SQL Provision

    SQL Provision allows users to create copies of SQL Server databases in seconds, using a fraction of disk space, and mask any sensitive data to help address data privacy and protection concerns. It serves as a gateway between production and non-production environments, to ensure the safe distribution of database copies from one central location, without blocking the team's development and release processes.

  • Article

    Safely Deleting Clones and Images during Database Development and Testing

    Whenever you’re ready to refresh a test cell with the latest database version, you need a safe way to drop the current set of clones, and the parent image, without losing any unsaved work. Phil Factor provides a PowerShell script that automates this process so it runs in the time it takes to grab a coffee, after which can quickly deploy the new clones.

  • Webinar

    How to keep your delivery processes secure with Database DevOps

    Extending DevOps practices to the database, brings additional advantages, ensuring you protect personal data across your SQL Server estate, while also improving the efficiency and quality of software delivery. We’ll explore the impact database DevOps has on regulatory and compliance requirements and how approaches such as automation, can improve accuracy, transparency, and faster recovery across the entire database development cycle.

  • Forums

    SQL Clone Forum

    Create SQL Server database copies in an instant

  • Marshe Hutchinson

    Hi, what about if you want to restrict permissions for 1 specific image?

    Thank you,