How to handle multi-user data storage (each client has a unique scheme)?

so I'm trying to set up a data warehouse for a service where each client has its own database with a unique schema. How can I configure the repository so that each client has its own semantic / relational model created automatically (since we (in the center) do not know what each database has). So that each client can easily report on their data? Is there any automatic process we can follow? Did I miss something?

+4
source share
2 answers

It depends on whether you want a consolidated view of the data or if each customer’s data remains divided.

If consolidation is the goal (and there are huge benefits for a multi-tenant SAAS tenant to have a consolidated overview of customer data), then Nithin B's offer is good.

If you need a separate warehouse, then you need to think about how to optimize your costs. The two largest components will be ETL / ELT and database hosting.

ETL/ELT - . - (http://ajilius.com/competitors). , ( / ), , .

? ? PostgreSQL SQL Server (SMP), Ajilius , MPP, .

+6

.

  • Landing .
  • .
  • . : Dim_Source
  • . , Dim_Source.
  • .

, .

BUS Kimball.

Nithin

0

Source: https://habr.com/ru/post/1674755/


All Articles