Looker will not be updating this content, nor guarantees that everything is up-to-date.
I am migrating to a new database, but my existing LookML projects are currently configured to my old database connection. I don't want to lose my projects, and I don't want to have to rewrite them from scratch for the new database connection. Is there a way to update the existing LookML to work with the new database connection?
The solution below outlines a high-level workflow for adapting LookML projects to a new database connection.
Communicate with your developers and freeze all development during the migration process to avoid large-scale merge conflicts. Only one developer or admin, with development permissions for all affected projects, should make the changes described in this article.
If your database migration resulted in a SQL dialect change, be sure to check SQL syntax in all sql-based parameters, such assql_always_where
andsql_on
, as well assql
for fields and Native Derived Tablederived_columns
. Also be sure to check the SQL in any SQL-based derived tables to determine whether any syntax updates are needed.
Now your projects are ready for use with your new database connection!