DataMaskerCmdLine.exe

skattie22

Hi
I'm using WindowsLogin, how do I specify the target database in the parfile?
It doesn't like LOGINSUB=XXXX[YYYY]||Servername[DatabaseName]
In the old days it was: -D XXXX[YYYY]=ServerName[DatabaseName] 
Also, I presume the -R and -X parameters are superfluous now?
I'm using DM 6.3.14 
Thanks
Adrian
PS. The documentation specifies DATASETDIR but it is in fact DATASETSDIR
PPS when I enable the Bulk Substitution it just hangs half-way through the masking, but works fine without the switch

PlantBasedSQL

Thanks @skattie22 not a problem - the Clone question was more out of curiosity as it makes the process much easier and means you don't need to generate your own PARFILE.

Using the documentation link above I was able to connect with WINAUTH, I'll include my PARFILE below

PlantBasedSQL

Where in this case I changed the Masking set to SQL Auth, gave it the username placeholder-login, then switched back to Windows Auth. Then in the login sub you just provide the setup you have in the masking set, followed by the connection to the DB you want to mask this time, the key is the || LOGINMODE_IS_WINAUTH appended to the LoginSub.

skattie22

hello, is there anybody there?

PlantBasedSQL

Hi @skattie22 I can only apologies profusely for the delay in my reply to this. Unfortunately I wasn't notified via the RSS Feed I have set up for the Data Masker forum and have neglected to check until now.

Are you still having issues with this requirement? Is there anything I can help you with now?

Please feel free to reply on here or ping me a direct email chris.unwin@red-gate.com and I will do all I can to help out!

skattie22

Hello Chris, the original problem still stands, how do I specify the target database in the parfile when using windows login?

we have a workaround but it would be nice to use it cleanly

PlantBasedSQL

Thanks @skattie22 - out of curiosity are you using the same masking set for different databases with the same structure and in different locations or are you always using the same set to mask the same DB (i.e. it always has the same name/location)?

skattie22

The database will have a different name but will be in the same location, e.g.
MyMaskingServer\MyDatabase_20200202
MyMaskingServer\MyDatabase_20200209

PlantBasedSQL

Thanks @skattie22 that's super helpful! So I guess your workaround right now is to have multiple copies of the masking set with different connection strings to the various DBs and then running them with the command line but omitting the LOGINSUB argument from the PARFILE?

I'm going to investigate this for you this morning by following up with the team but a very quick question on this - do you also have access to SQL Clone as part of your use of Data Masker? I ask only because it would limit you to masking 1 copy as part of the Imaging workflow and then you could spin up multiple DB clones (which could potentially solve this problem) - just curious!

PlantBasedSQL

Just leaving the relevant documentation page here for my own record: https://documentation.red-gate.com/dms/data-masker-help/general-topics/about-command-line-automation/login-substitution-for-the-sql-server-command-line

skattie22

no we don't have clone, and no we don't have multiple masking files, we have a base file with xxxx/yyyy and replace it on the fly with the appropriate target

PlantBasedSQL

PlantBasedSQL

Also, on your original PPS with the bulk substitution hanging, this should have been fixed as of the latest versions (the team made a number of improvements to this to make it more resilient)

skattie22

Thanks Chris, I have got it working with the LOGINMODE_IS_WINAUTH which I somehow missed on the first pass.
- Adrian

PlantBasedSQL

Sorry for the delay in reply @skattie22 but I'm glad to hear you got this working!