How can we help you today? How can we help you today?
don_don

Activity overview

Latest activity by don_don

Hello, PlantBasedSQL!  It looks like your suggestion works and will fill the gap until an interface-based solution is provided.  Thanks again for the time you spent putting this together and for sharing your expertise. / comments
Hello, PlantBasedSQL!  It looks like your suggestion works and will fill the gap until an interface-based solution is provided.  Thanks again for the time you spent putting this together and for sh...
0 votes
Hello, PlantBasedSQL!  Thank you for taking the time to respond to my post.  I apologize that I wasn't very clear. [address] and [address_version] are not in the same data model - at least not at the same time.  v1 of the data model contains [address] with 12 columns.  v2 of the data model has [address_version] with 16 columns; the first 12 are exactly the same in the same ordinal order as [address] - the last 4 are date columns used to version the rows.  [address] is dropped from the model and replaced because [address_version] is the 'upgrade' to [address]. Since [address_version] is the 'upgrade' I had hoped I could just point the [address] rule to [address_version] and move on.  The rules for [address_version] will remain the same as [address] since the additional date columns are non-sensitive. Regarding the 500 tables - that was a tongue-in-cheek reference to the overall data model.  I am at the mercy of a third-party vendor who is still in the process of maturing their model and offering new features as other clients request them -- all of which translates to a more fluid model that one might expect from such a provider.  I do have a lot of tables to review, but the vast majority of them do not contain sensitive data.  But as the data model is 'upgraded', I need to review (and where necessary) modify the Masker ruleset. I am at a sort of borderline; there are enough tables to mask and review on each 'upgrade' that I might be justified in integrating Data Catalog -- but not quite so much as to justify the distraction from my other tasks to integrate Data Catalog.  I appreciate the reminder about Data Catalog, though, thank you for mentioning it. If we're talking about putting this in front of the dev team, it would be a very helpful feature to be able to 'map' prior-version tables and rules to new-version tables and rules, in bulk.  So long as I'm dreaming.  [image] Anyway, directly modifying the xml in DMSMASKSET seems to be my short-term way forward.  I am comfortable with json and xml, so this shouldn't pose too big a hurdle - I just didn't know I had that sort of access.  I'll be sure to be careful.  [image] So now that I've written a novel, I'll just say thank you again for your time to research this and provide a solid suggestion to move my projects forward; I'll give that a whirl. / comments
Hello, PlantBasedSQL!  Thank you for taking the time to respond to my post.  I apologize that I wasn't very clear.[address] and [address_version] are not in the same data model - at least not at th...
0 votes
updated table model - same rules?
Not sure how this will translate in text, but here goes.v1 of a data model has a table [address], which I've masked with various rules.v2 of the data model has a table [address_version]; this table...
2 followers 6 comments 0 votes
change db owner / set read_only with clone template .. ?
I realize I could do the subject tasks in a separate step using a number of different approaches -- but I'm curious why I can't during the cloning process with a template.  The help files tell me t...
2 followers 2 comments 0 votes