Security on Source Server

clansing

Is there any way to ensure that users can't accidentally create databases on the image source server.  The other day a user was creating a clone and picked the source server, rather than their local instance, as the location to create the clone, and it went ahead and did that.  I tried giving the SQL Clone agent limited access on the source database server but the interface told me it needed sysadmin rights

Jessica R

Hi @clansing!

It will actually only come up as a potential clone destination if there is an agent installed on there (but you do need the agent there if you need to make images of databases on that server).

As Dan mentioned, we will pass on your feedback on this to our devs to consider when we start work on user permissions. So sorry there isn't a built in way to do this at the moment!

Dan B

Hi clansing,

At present this isn't possible but is certainly something we can look at when we start work on user permissions. 

Do you keep clones on the source instance? If not you do not require an agent on this server. 

We would also advise using backups over taking clones from the live database if you aren't already.

clansing

Thanks for your response,
Currently we have the application and an agent running on the source server, the agent is used to create images.  Clones are not created on the source server.  Even if we don't have an agent on the source server, no matter where the agent is, it's needs sysadmin access to the source server right?  And therefore it shows up as an option for clone destination, which is what we don't want.

We are having better performance not using backups and that part is not a problem

clansing

Not a big problem, appreciate the responses and taking this into consideration