Forum Discussion
Multiple Customer Solution in fabric
- 10 months ago
Hi DiKi-I,
I think this really depends on the business requirements here. I would not make a new mirrored DB for each user, that seems to be a little much.
What's the security requirements? Are all users access the same data, or are they each accessing different data from the same database?
Where my mind immediately goes for this is to have one workspace that contains the database, and then the users all connect to that same database in their workspaces.What could also work is one mirrored DB and then a lakehouse with shortcuts to the mirrored database.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
It depends what your customers intend to do with the data once it is in fabric.
For example, do they intend to keep using the data in a relational database or is the idea now to to move the data for analytical purposes? If it is for analytical purposes mirror db may not be the ideal solution and you may want to consider alternatives.