Deploying designs manually

If you choose not to have Database Designer deploy your design at design time, you can deploy the design later using the deployment script:.

If you choose not to have Database Designer deploy your design at design time, you can deploy the design later using the deployment script:

Make sure that the target database contains the same tables and projections as the database where you ran Database Designer. The database should also contain sample data.
To deploy the projections to a test or production environment, execute the deployment script in vsql with the meta-command \i as follows, where design-name is the name of the database design:
```
=> \i design-name_deploy.sql
```
For a K-safe database, call Vertica meta-function GET_PROJECTIONS on tables of the new projections. Check the output to verify that all projections have enough buddies to be identified as safe.
If you create projections for tables that already contains data, call REFRESH or START_REFRESH to update new projections. Otherwise, these projections are not available for query processing.
Call MAKE_AHM_NOW to set the Ancient History Mark (AHM) to the most recent epoch.
Call DROP PROJECTION on projections that are no longer needed, and would otherwise waste disk space and reduce load speed.
Call ANALYZE_STATISTICS on all database projections:
```
=> SELECT ANALYZE_STATISTICS ('');
```
This function collects and aggregates data samples and storage information from all nodes on which a projection is stored, and then writes statistics into the catalog.