Hi everyone!
Currently, we are dealing with a problem of browsing the database in the test and prod environments. We would like to have the possibility to see all the data from all the tables in the system.
We created something like a BackOffice, where we built views with tables to see all the data from database tables, but this creates three problems for us:
1. Every time a new column is added, we need to remember to add it to the BackOffice View - column, filter, searching
2. Searching, filtering, and joining are far harder without classic SQL. We added searching and sorting functionality to the BackOffice tables, but it's still not enough, because, for example, joining two tables is not possible.
3. It is not possible to modify the data. I mean, it is possible, but we would need to implement this functionality, which would take a considerable amount of time.
What is your solution for this kind of problem? Do you have any best practices for that case?
Hi,
Although not mentioned, I assume your issue is with a Cloud managed O11 or ODC infrastructure?
For O11 you can use SQL Sandbox, or the in Service Studio built in capability to query and edit tables directly.
For ODC there are similar Forge components available, like Database Access ODC. Also ODC Studio has the same features as Service Studio for directly querying and editing tables.
Regards,
Daniel
For ODC, I’d avoid maintaining a custom BackOffice for this. The built-in database tools in ODC Studio are much easier for ad-hoc querying and editing, and a Forge component like Database Access ODC is useful if you need similar access outside the development environment. This also saves you from updating views every time the data model changes.