Sensitive information might be there for grabs by some bad intention-ed users. Also when running Multi-Tenant DW where you have multiple users speared by each project you don`t really want to give this opportunity on seeing resource pools definition or any user specific definition. -- see more on how to enforce this at --http://wp.me/p5zzAw-Yb
In this short article i will go over the steps used to create a simple Vertica UDP (user defined procedure) that will help us create a new schema and also create the database roles in a single SQL command. This will help you work faster and spend less time writing simple SQL code. Make your comments or suggestions on the procedure. Thx
Migrate one Schema fast and dirty from one Vertica Cluster to another.
This approach is used when :
you don’t have Vertica Cluster configuration the same in both Clusters and copy cluster won’t work. no INBOUND access is available to the source Vertica Database(Production security needs to be strict). different Vertica Server Version. to many constraints dependencies in the tables for the schema you wanna export, so vbr.py backup on the schema is to painful.