Using Anonymizer with Navigator Optimizer

How to use Anonymizer with Navigator Optimizer:

  1. You type a password at the command line when you use Anonymizer to encrypt workload files. When you type a password at the command line, Anonymizer generates a .passkey file that you must use to recover the encrypted schema information. Anonymizer encrypts all sensitive information on the client. There is no data transmission over a network. The encrypted SQL queries retain their structure. SQL keywords, such as CREATE or INSERT, are left in plain text, but all table names and column names are encrypted and literals are masked. See Encrypting and Decrypting CSV Workloads or Encrypting and Decrypting SQL Workloads for details.
  2. After you encrypt the workload file, upload it to Navigator Optimizer cloud service where it is analyzed. Analysis is possible because Navigator Optimizer only uses the structure of queries to make recommendations, not the data itself. Literals are not sent to the cloud service because they are masked by Anonymizer on the client before uploading. Consequently, literals cannot be recovered after Anonymizer is run on a workload file unless you choose the -l or the --skip_mask_literals option when you encrypt the file. This option prevents Anonymizer from masking literals in the SQL queries.
  3. After Navigator Optimizer analyzes the encrypted workload and provides recommendations, decrypt the data in the Navigator Optimizer client-side browser window to see column names and table names:
    1. Click the eye icon in the top right corner of the Navigator Optimizer application window:

    2. In the Decrypt to see the original text dialog box, type the password you used when you encrypted the workload and click Choose File to upload the .passkey file that was created when you encrypted the workload file:
      "Decrypt to see the original text" Dialog Box

    3. Click Decrypt.
    No decryption is possible without the password and .passkey file, which are never sent to the Navigator Optimizer service. Instead, the password and .passkey file are used in the JavaScript that runs in your client-side browser. This is where all decryption occurs.