Comments
Sort by recent activity
Hi @rmg1 Thanks for coming back on this - absolutely you can put the backup & image files elsewhere on the network, they don't have to be on the same server as the instance creating the image. Geographic location can play a part in latency connecting to the image though so that's just something to be aware of (more on that in our best practices document here: https://www.red-gate.com/products/dba/sql-provision/resources/best-practices-sql-provision) but ultimately putting them on the file server should be fine, so long as the SQL Clone agent running on the nominated SQL Server has read/write access to network locations where images will be stored! Let me know if you have any other questions - thanks! / comments
Hi @rmg1 Thanks for coming back on this - absolutely you can put the backup & image files elsewhere on the network, they don't have to be on the same server as the instance creating the image. Geog...
Sounds great @rmg1 ! Let me know if you have any problems, happy Cloning! / comments
Sounds great @rmg1 !Let me know if you have any problems, happy Cloning!
Yes absolutely [image] 1 word of caution, that can catch some of our users out, if you have any maintenance - jobs on these servers that might also affect the Clones then this might cause them to grow (as it would technically be applying differences) - the chances are minimal, but I wanted to let you know just in case! / comments
Yes absolutely 1 word of caution, that can catch some of our users out, if you have any maintenance - jobs on these servers that might also affect the Clones then this might cause them to grow (as ...
Thank you for coming back on this @rmg1 We would expect the images to be, assuming you weren't making any changes to the Databases (.sql scripts or Data Masking .dmsmasksets) to be roughly the same size as the uncompressed backups / original databases). Let me know if you have any further questions. / comments
Thank you for coming back on this @rmg1 We would expect the images to be, assuming you weren't making any changes to the Databases (.sql scripts or Data Masking .dmsmasksets) to be roughly the same...
Not a problem @rmg1 The Clones are created as empty differencing disks (as per my post above). Fortunately, this means that on creation (assuming you have not altered them in any way) they should be around 50mb in size. Let me know if you have any additional questions! / comments
Not a problem @rmg1 The Clones are created as empty differencing disks (as per my post above).Fortunately, this means that on creation (assuming you have not altered them in any way) they should be...
Hi rmg1 thank you for your post, Once the Image has been taken from the respective databases they are immutable - meaning they are completely removed from the workflow of Production/Test and do not grow with additional information. The process would be: Images of the A databases would go onto Windows File Share and then Clones would go onto Server B and C. If you did no work on or made no changes to the Clones then these would not grow (only the differences are stored locally) - it wouldn't be until you created new Images and Clones that they captured any new data from the databases on A. How it works is described here: https://documentation.red-gate.com/clone3/getting-started/what-is-sql-clone Optimally, we would recommend you used backups of the databases on server A to create the Images so that the Databases on Server A never have any additional overhead on them from the Imaging process. I hope this makes sense - let me know if you have any further questions - thank you very much! / comments
Hi rmg1 thank you for your post,Once the Image has been taken from the respective databases they are immutable - meaning they are completely removed from the workflow of Production/Test and do not ...
Thank you for coming back on this @Robb_Keller The Export/Import Plan as csv is used for more easily managing your planning as to which fields should be masked. This would allow you to open it in i.e. Exel (e.g. a shared spreadsheet a team use to plan the masking together) and carry out your planning of how to mask outside of Data Masker and then import it, allowing it to update to match what you have done. This functionality is not used for modifying or creating the masking rules. Let me know if you have any other questions - thank you very much. / comments
Thank you for coming back on this @Robb_Keller The Export/Import Plan as csv is used for more easily managing your planning as to which fields should be masked. This would allow you to open it in i...
Hi @Robb_Keller Thank you for your post. The developers have heard of people generating the masking sets programmatically for the rules in the past, but we don't have specific examples of this (and I haven't tried this myself). Ultimately though the underlying DMSMaskSet file is just XML (try opening it in Notepad++ etc and having a look) It is technically do-able though and we would approach it as follows: 1) create a masking set with one rule in it. This rule would act as a template. 2) use a text editor to split the masking set into 3 parts. a) The first part is everything above the rule b) the second part is the rule XML c) the third part is everything below the rule 3) Then I would get a comma delimited list of the table and columns to be masked (and possibly the datasets the column is to be masked with). 4) Next write a program which loops through the table/column names and uses the rule XML as a template to do a replace operation 5) The generated XML for each new rule would be emitted sequentially to the same file. 6) The top, new middle part, and bottom would be concatenated together and everything should work. The big thing to take care of is that the rule numbers are not duplicated. This is very important. Remember the controller itself has a rule number (usually 01) so you should probably start at 02. I hope this helps? Let me know if we can help out any further! / comments
Hi @Robb_Keller Thank you for your post.The developers have heard of people generating the masking sets programmatically for the rules in the past, but we don't have specific examples of this (and ...
Hi @Robb_Keller Thank you for your post - can I possibly get more information on this, please? Which sub-rules are you using within the search-replace rule? Are you using a dictionary lookup, regular expression etc.? What are you trying to achieve with this rule and what type of information are you masking? The reason I ask these questions is that there may be a better way to achieve what you're trying to do and failing that I can speak with the development team about this, but would need some more specifics. Thank you very much! / comments
Hi @Robb_Keller Thank you for your post - can I possibly get more information on this, please? Which sub-rules are you using within the search-replace rule? Are you using a dictionary lookup, regul...
Hi @Robb_Keller I've just heard back from the Dev team and they have let me know that if you prefix your RegEx with (?i) this should make it case insensitive. i.e. (?i)dOCTOClone Let me know if you have any other questions - thank you very much. / comments
Hi @Robb_Keller I've just heard back from the Dev team and they have let me know that if you prefix your RegEx with (?i) this should make it case insensitive.i.e. (?i)dOCTOCloneLet me know if you h...