Dynamic DB environment connection

[allam-sudhakar]

Hi,

I did some posts and answers on dynamic db connections, however, nothing is straight forward. Would it make sense to provide a user parameter before launching Looker just like any other desktop application for selecting the db environment that user would like to develop/test/run against? One can actually automate model population based on the user selection. It is understandable that schemas in different environments may not be in sync, but, that in itself is a good testing condition for developer to bridge the gap. If the user is not permitted then obviously nothing shows up even for running as security is checked before letting user do functions that he/she is entitled to do.

Not sure on what issues might have stopped implementing this functionality, however, could somebody please expand on this? 

Regards,

Sudhakar

[evelyn_s]

Hi Sudhakar - Most database connections can point dynamically to different databases by parameterizing the JDBC parameters with user attributes. See  https://cloud.google.com/looker/docs/connecting-to-your-db#additional_jdbc_parameters

In addition, it's possible to point to different schemas and tables within the same database connection using the method outlined in https://cloud.google.com/looker/docs/best-practices/how-to-create-a-dynamic-schema-with-user-attribu...

It's also possible to point to different databases depending on whether a user is in development or production mode: https://www.googlecloudcommunity.com/gc/Modeling/Auto-Switch-between-Dev-Prod-Schema-and-PDTs/td-p/5...