Data Masker from command line-PowerShell
Arun72
Posts: 21 Bronze 1
Hello All,
I am trying to run the masking from the command line and replicated the same that shown in the video from the official website. I also added the path for "DataMaskerCmdLine" in the system variables. But still getting the below error.
Path: C:\Program Files\Red Gate\Data Masker for SQL Server 7
-------
I am trying to run the masking from the command line and replicated the same that shown in the video from the official website. I also added the path for "DataMaskerCmdLine" in the system variables. But still getting the below error.
Path: C:\Program Files\Red Gate\Data Masker for SQL Server 7
-------
& : The term 'C:\Program Files\Red Gate\Data Masker for SQL Server 7>DataMaskerCmdLine.exe' is not recognized as the name
of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again
--------
Thanks for the help!
--------
Thanks for the help!
Tagged:
Answers
& runs an executable but it looks like your path includes an invalid character ">", it should be used like this:
& "C:\Program Files\Red Gate\Data Masker for SQL Server 7\DataMaskerCmdLine.exe" PARFILE="C:\Users\arun72\Documents\Data Masker(SqlServer)\Masking Sets\MyParFile.PARFILE"
Let me know if this helps,
Kindest
Thanks for the response, the path was right ,but I entered it wrong in my previous post. I have tried multiple syntaxes, ran from command line as batch file and even the syntax that you suggested ,below is the error for both couple of syntaxes and I couldn't see any logs as well.
Syntax 1: & "C:\Program Files\Red Gate\Data Masker for SQL Server 7\DataMaskerCmdLine.exe" PARFILE="C:\Users\arun\Desktop\DataMasker\PowerShell\PARFILE.txt"
Syntax 2: & "C:\Program Files\Red Gate\Data Masker for SQL Server 7\DataMaskerCmdLine.exe" PARFILE="C:\Users\arun\Desktop\DataMasker\PowerShell\PARFILE.PARFILE"
Error:
PARFILE:
Thank you
It can be .txt or .PARFILE (still basically a .txt though) but it sounds more like a PARFILE issue than a cmdline issue!
It's DATASETSDIR (Not DATASETDIR)