Dear Friends,
We're recently released SQL Clone v4, which introduces a
feature called Teams that allows administrators to control of data
security and access control, and then allow users the freedom to 'pull' databases,
and then use, reset and delete them, on demand. For developers it is, as Phil
Factor puts it, "the difference between waiting to be served lunch
and using a self-service canteen."
This month, I want to encourage any SQL Clone users among you to writing a short, technical article, about how you use the tool. It could be a high-level, strategic article explaining how you use SQL
Clone, where clones get deployed in your organization, who uses them and for
what reasons.
It could be a 'how to' article, demonstrating in more technical
detail how you work with SQL Clone, any issues you encountered
using it on your systems and how you dealt with them. It might cover the new Teams
feature, specifically, with advice on managing security/privileges for the
system. It might offer guidance on the architecture you've found works best for
SQL Clone, covering network connectivity between the various components,
characteristics of the fileserver holding the data image files, the Windows SQL
Server instances serving as the source of images or host for clones, and so on.
It might focus on automation, giving some example PowerShell scripts
demonstrating how you've used Clone to automate your database provisioning.
As with any of our tools, if you've experiences and knowledge that you think might help others be successful with SQL Clone, faster, I'd like
to hear from you. Even small pieces of advice can help a lot; just drop a comment on
this post, in the first instance. Also, feel free to share in the comments, any
problems you've encountered with SQL Clone that have made it harder to implement.
Cheers,
Tony.
Dear Friends,
We're recently released SQL Clone v4, which introduces a feature called Teams that allows administrators to control of data security and access control, and then allow users the freedom to 'pull' databases, and then use, reset and delete them, on demand. For developers it is, as Phil Factor puts it, "the difference between waiting to be served lunch and using a self-service canteen."
This month, I want to encourage any SQL Clone users among you to writing a short, technical article, about how you use the tool. It could be a high-level, strategic article explaining how you use SQL Clone, where clones get deployed in your organization, who uses them and for what reasons.
It could be a 'how to' article, demonstrating in more technical detail how you work with SQL Clone, any issues you encountered using it on your systems and how you dealt with them. It might cover the new Teams feature, specifically, with advice on managing security/privileges for the system. It might offer guidance on the architecture you've found works best for SQL Clone, covering network connectivity between the various components, characteristics of the fileserver holding the data image files, the Windows SQL Server instances serving as the source of images or host for clones, and so on. It might focus on automation, giving some example PowerShell scripts demonstrating how you've used Clone to automate your database provisioning.
As with any of our tools, if you've experiences and knowledge that you think might help others be successful with SQL Clone, faster, I'd like to hear from you. Even small pieces of advice can help a lot; just drop a comment on this post, in the first instance. Also, feel free to share in the comments, any problems you've encountered with SQL Clone that have made it harder to implement.
Cheers,
Tony.