Product articles SQL Clone Compliant Database Provisioning
New permissions features brings access…

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

Create SQL Server database copies in an instant

Find out more

You may also like

  • Article

    How to automatically provision sanitized data using SQL Clone, Data Masker and PowerShell

    Chris Unwin describes a strategy, using data masking, cloned databases and PowerShell, which will allow you to sanitize data before provisioning test or development environments.

  • Webinar

    How to treat compliance in DevOps as serious business

    We hosted this webinar to discuss how, by embedding ‘Privacy by Design’ in your Database DevOps practices, you can introduce a framework that builds a bridge between fast AND secure software development. We arm you with practical tips on how to discover, classify, protect and monitor your SQL Server estate, and therefore ensure that your Database DevOps practices are secure

  • Article

    Testing Databases: What's Required?

    Phil Factor reviews the various types of database test that need to run during development work, what sort of test data they require, and the challenges with managing this data, and in keeping the test cell stocked with the correct database, and data, in a way that allows rapid cycles of database testing.

  • Article

    A behind the scenes glimpse of SQL Clone

    It has always been a difficult task to provision development and test environments so that they reflect as closely as possible what’s present in production. With the rise of containerization and Infrastructure as Code (IaC) technologies, some parts of this are becoming much easier. We can automate the process of spinning up and configuring new virtual

  • Webinar

    Data privacy & protection: A logical extension to DevOps

    Are you considering data privacy and protection as part of your DevOps process? In light of legislation like GDPR, making sure that any personally identifiable information (PII) is protected as it moves through your development and testing environments, is now an essential part of the process to ensure that your Database DevOps practices are compliant.

  • Forums

    SQL Clone Forum

    Create SQL Server database copies in an instant