Drop Primary Keys

Search Knowledge Base by Keyword

< Back

The DROPPKEYS Action removes Primary Key Constraints from the Staging Database. It removes all Primary Key Constraints where:

  1. The Table is set to “Active” in the Tables Sheet.

Note: To run DROPPKEYS you must first run DROPFKEYS. DROPPKEYS will furthermore only run successfully if all the specified Primary Keys are found in the database. If the automated job fails, check the Tables Sheet sheet to make sure only keys present in the database are specified.

To run DROPPKEYS, open The VIP Server Controller from your desktop or start menu. You must open it as an administrator. If The VIP Server Controller is already running, make sure the relevant .vip workflows are Put in Memory. See this article for instructions.

Next, complete the mandatory parameters in the “Run Flow” tab. If working from a Config file created for the current Subset, you should only need to update the parAction argument and enter any additional optional parameters. You will need to update the location of the Subset Report and SQLActionsPath if these have changed. See this article for instructions on working with a Config file.

Specify “DROPPKEYS” for parACTION:

parAction= DROPPKEYS

Complete any optional parameters. See this Knowledge Base article for a full list of Arguments and example parameters.

Once you have parameterized the DROPPKEYS Action, make sure your Configuration Spreadsheet, Subset Report and Log file are all shut. Next, click “Create File” and then click “Start” to run the action.

In the output dialogue, you will see “Flow execution completed on remote server. Please check logs for details.” once the DROPPKEYS Action is complete”:

If you receive an error message in your output dialogue or log, please refer to this article to troubleshoot common issues. You can also run your Action on debug mode for a more detailed log. You can also check the Log File and Subset Report at this stage, to check that the Actions have performed correctly.

Next, check your Database to make sure the Primary Keys constraints have been removed. You can then update your Control Spreadsheet and Add Primary Keys if you want.

Note: DROPPKEYS will only run successfully if all the specified Primary Keys are found in the database. If the automated job fails, check the ForeignKeys sheet and Tables Sheet to make sure only keys present in the database are specified.

Run DROPPKEYS from the Command Line

To run DROPPKEYS from the Command Line, first open your re-usable .cmd script in a text editor. DROPPKEYS will furthermore only run successfully if all the specified Primary Keys are found in the database. If the automated job fails, check the Tables Sheet sheet to make sure only keys present in the database are specified.

If you have already configured a .cmd script for one Subset Action and wish to edit and re-use that script, you should only need to set “DROPFKEYS” for “Action”.

Otherwise, configure all mandatory parameters in the .cmd script.

You can also specify optional parameters at this stage.

Make sure your Control Spreadsheet, the Subset Report, and any Log Files are closed.

Run the script to remove the specified Primary Keys from your Staging Database.

Check the Log File and Subset Report at this stage, to check that the Actions have performed correctly.

Next, check your Database to make sure the Primary Keys constraints have been removed. You can then update your Control Spreadsheet and Add Primary Keys if you want.

Note: DROPPKEYS will only run successfully if all the specified Primary Keys are found in the database. If the automated job fails, check the ForeignKeys sheet