Feature requests
wonderbison
Posts: 18 Bronze 1
in SQL Clone
Hi
Now I have SQL Clone up and running local and evaluating (and already I am promoting it to other teams in my organisation and other companies) I would like to propose a few feature requests and reasons. I realise that this is version 1 of the product and the suggestions may already be in development.
1. Folder creation - If a folder doesnt exist then create/attempt to create/options for it to be created - Its annoying that I cant do this "in tool". I understand that there may be security implications and why they should be created ahead of time by a central resource however if we are given access to a specific SQL Clone drive, or folder, then SQL Clone could have the option of creating it?
2. Groups/Groupings of images - I look after many databases in 1 instance for 1 team. There are of course multiple teams in my organisation. The dashboard is going to get crowded very quickly. Being able to group my images by team, and then database would be good. Being also able to filter to only show my teams, or even my teams and any others I am interested in would be great
3. Retention period - Have a default retention period for images. After nn days they delete, or at least someone gets an email to delete especially if no clones. Or at least have the ability to put a retention period on an image if you want one. I realise that this could be catered for as drives fill but it would be good to get notified prior to this, especially if the drive is multi-teamed as nobody ever takes responsibility
A good product.
Now I have SQL Clone up and running local and evaluating (and already I am promoting it to other teams in my organisation and other companies) I would like to propose a few feature requests and reasons. I realise that this is version 1 of the product and the suggestions may already be in development.
1. Folder creation - If a folder doesnt exist then create/attempt to create/options for it to be created - Its annoying that I cant do this "in tool". I understand that there may be security implications and why they should be created ahead of time by a central resource however if we are given access to a specific SQL Clone drive, or folder, then SQL Clone could have the option of creating it?
2. Groups/Groupings of images - I look after many databases in 1 instance for 1 team. There are of course multiple teams in my organisation. The dashboard is going to get crowded very quickly. Being able to group my images by team, and then database would be good. Being also able to filter to only show my teams, or even my teams and any others I am interested in would be great
3. Retention period - Have a default retention period for images. After nn days they delete, or at least someone gets an email to delete especially if no clones. Or at least have the ability to put a retention period on an image if you want one. I realise that this could be catered for as drives fill but it would be good to get notified prior to this, especially if the drive is multi-teamed as nobody ever takes responsibility
A good product.
Tagged:
Comments
Thanks very much for taking the time to provide this feedback. I will pass this onto the team to see if we can add these features in the future.
We can't provide any feedback on when this would be included in the tool but please do keep an eye on the release notes here http://documentation.red-gate.com/display/CLONE1/Release+notes+and+other+versions
Dan Bainbridge
Product Support Engineer | Redgate Software
So for example, currently, we only have server installs of instances but local SSMS. The ability to create automatically local instances, or provide the commands for people who are less technical, would be excellent. PowerShell or whatever, don't mind. In my case I need to provide commands for our business users to create local instances for their clones.
Thanks
Could you give us more information about this, especially around how you see this working within the context of SQL Clone (e.g. during cloning process, etc.)? I doubt that we will be able to do this but would be great to understand a bit more.
Technical Lead, Data Privacy & Protection
Redgate Software Ltd.
Thanks for getting in touch tugberk. So there would be a couple of technical issues but have a basic config file that could be used. Then like the SingleUseSQLCloneAgentInstaller.exe have something that allows for the SQL Server setup to be run using the config. this would be a one off setup of course.
The issues would be the ability to run setup (finding the media but this could be requested during the initial screens), the user account to use or default to BUILTIN\Users (?)
You might not have Admin rights but the "executor" would have to get around this by either using a folder that they had admin rights on or to run the install as an Admin (for those that package).
All I was thinking would be to avoid having to go through the installer to setup a config which isn't a major point I grant you, however its just to give your tool the next stage of "completeness".
Thanks