Comments
Sort by recent activity
@jamesgally are you able to get the masking statistics (table and rule stats) that should be part of the log files when this job runs? The split ranges sound like they're running suuuuuuuper slow so I'm wondering if you check the results how many rows/s are getting masked. / comments
@jamesgally are you able to get the masking statistics (table and rule stats) that should be part of the log files when this job runs? The split ranges sound like they're running suuuuuuuper slow s...
Hi @RobGeorge - for simplicity I think you'd be best off with the (Correlated) option. If you set all Dates to be varied with this option any correlated variation will be the same across the table to help keep the alignment of before/after dates. [image] [image] [image] / comments
Hi @RobGeorge - for simplicity I think you'd be best off with the (Correlated) option. If you set all Dates to be varied with this option any correlated variation will be the same across the table ...
@CorvetteFan are your clones 10s of GBs right away after provisioning? If the clones have been around for a while and grown then I'd recommend source controlling any changes, deploying and then refreshing your Clone Image and Clones anew so you're back to a couple dozen MB. If the Clones bloat to 10s of GBs right after provisioning it could be that there were some pending changes being made as the image was finalized, and these transactions are being replayed on the clone as it's created (in which case you can add a wait command during Image modifications so everything is complete when the image is created), or it could be that the Clones are being upgraded so you might benefit from an image that is a more compatible SQL Server version - guidance here on the Clones: The files behind the Clone have grown to be very large - SQL Clone 5 - Product Documentation (red-gate.com) Shrinking, or doing anything to a Clone will just cause more differences because they're not full copies of the DB and therefore won't respond to normal space saving techniques (i.e. you can truncate all tables in a clone and it'll actually get bigger because it is storing the differences) There should be (if you're using SQL Clone 4.4+) the option to also compact your image during creation: Image compaction - SQL Clone 5 - Product Documentation (red-gate.com) / comments
@CorvetteFan are your clones 10s of GBs right away after provisioning? If the clones have been around for a while and grown then I'd recommend source controlling any changes, deploying and then ref...
Hey @... have you tried using a Sync Manager? You can use the same method mentioned here: Masking Primary and Foreign Keys - Advanced Operations with Data Masker for SQL Server - Redgate University (red-gate.com) The values don't actually need to be PKs/FKs rather can be a distinct set of values across 2 tables with no PK/FK relationship between them / comments
Hey @... have you tried using a Sync Manager? You can use the same method mentioned here: Masking Primary and Foreign Keys - Advanced Operations with Data Masker for SQL Server - Redgate University...
Hey @SQLSi - I think you can do this with a Table-Internal Sync Rule, once you've masked the Usernames run through the Table with a dependant Table-Internal rule using the UserGUID as a key and the Username to be updated, that should get things looking how you want! / comments
Hey @SQLSi - I think you can do this with a Table-Internal Sync Rule, once you've masked the Usernames run through the Table with a dependant Table-Internal rule using the UserGUID as a key and the...
@Gert_Vlot no problems! The support team at Redgate is awesome so I'm sure they'll have some great ideas! :-) In my experience when clones go missing it's been because: 1) Someone who has admin access to the SQL Clone console has been deleting them thinking they're cleaning them up OR 2) A PowerShell script (or Agent Job) has been set up to drop databases in the environment as part of a weekly/monthly refresh of environments, or clearing up certain databases with certain naming patterns OR 3) Someone is dropping the databases e.g. through SSMS thinking they're no longer required Whatever happens, the activity history in the Clone server, status of the Clones from the SQL Clone Config DB or SQL Server logs should shed some light on it! I'd be curious to hear if SQL Clone still thought the clones exist although they've been removed from the Instance. / comments
@Gert_Vlot no problems! The support team at Redgate is awesome so I'm sure they'll have some great ideas! :-)In my experience when clones go missing it's been because:1) Someone who has admin acces...
@Gert_Vlot did you get an answer to this? Did you find out why this was happening? If you look at the SQL Clone DB and look in the Clones table it should tell you the status of any clones (in particular the ones that went missing) and it might help you shine a light on why it's happening...? / comments
@Gert_Vlot did you get an answer to this? Did you find out why this was happening?If you look at the SQL Clone DB and look in the Clones table it should tell you the status of any clones (in partic...
Does that mean you're using Clones to support application instances in Prod or that need to be backed up? Or by application aware is it a backup of the SQL Clone server itself and the databases on it? / comments
Does that mean you're using Clones to support application instances in Prod or that need to be backed up? Or by application aware is it a backup of the SQL Clone server itself and the databases on it?
@Censor1983 is there any reason why you're backing up a Clone / Clones? Clones are intended to be ephemeral copies of the Image you create and any delta changes you make can be recorded in Source Control - and they should only be on Dev/Test instances. I'm not sure I understand how Veeam plays or should play a role in this. / comments
@Censor1983 is there any reason why you're backing up a Clone / Clones? Clones are intended to be ephemeral copies of the Image you create and any delta changes you make can be recorded in Source C...
@rallen can I check what you're looking to test with this? Just to make sure I have the right context at least. My approach if I needed to keep the town, state and zip code correct in the set would be either: 1) Create your own correlated data set with a dump of "real" addresses that are publicly available from the internet and mask those values in so the addresses are all real but not YOUR real addresses 2) Use a shuffle rule to group shuffle the 3 columns together, that way all the addresses are real and they're your addresses so they're the same spread, but they no longer relate to the original row in that specific table / comments
@rallen can I check what you're looking to test with this? Just to make sure I have the right context at least.My approach if I needed to keep the town, state and zip code correct in the set would ...