Database schemas are subject to change, and Verb accommodates changes as broadly as possible. The Verb platform will adapt to your schema changes whenever possible. Any changes that we can internally resolve or reconcile will be automatically applied on your behalf.
However, there are times when changes to your schema may result in changes you need to address. Below are a few common examples.
It's not uncommon for columns to be removed from a database. However your dashboards are built from a schema that, at one point, included the missing column. In this case, you have a few options.
You can use the data source editor to disable a table column. Doing so will prevent any further attempts to ingest data from that column. This option is suitable when models and dashboard collections do not depend on the data in the removed column.
If the data in the removed column is used for reporting in one or more dashboard collections, the data source will need to be updated. You can edit your data source in the same way it was originally created. Verb will rebuild your schema without the deleted column and ingestion will resume with the updated configuration. This option is more aggressive and may result in additional data ingestion (possibly a full re-synchronization depending on your database's schema).
Similar to columns being removed, you will need to inform Verb of newly added columns. You can do so by simply editing your data source and configuring the new column to set type, aggregation, and display values. Once configured, the data for the new column will be ingested. If historical data for this column is important, a full synchronization may be necessary to include all data for the newly added column.
While column changes are often automated, table changes are not. Your schema as well as the data you synchronize with Verb has a particular "shape." Tables are the element that defines the schema's shape. In SQL terms, tables are used to join between data in various tables and views to produce a data set. If you remove a table from your schema, you will need to edit your data source to allow Verb to rebuild a map of your new schema. Depending on the complexity of your schema, this kind of change likely requires updating your models. Model use a similar "join" structure to understand the path between tables in your schema. Once your data source is updated, you can update your model accordingly. Finally, any dashboard tils that used data from the removed tables will need to be updated. Tiles are build from the models you create, so tile reconfiguration is as simple as selecting the right fields from the model you redefine.
Like adding columns, you will need to inform Verb of newly added tables. You can do so by editing your data source and configuring synchronization interval. Once configured, the data for the new table will be ingested. Data will follow the normal method starting with the oldest records until the data has been fully ingested.