You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be neat if there was an easy way to verify tenant isolation after a migration. In a complex database, it can be hard to know if you mapped every FK as necessary. When you craft a migration in code with SqlMigrator, you simply go from memory/intuition about what FKs need to be mapped.
I'm picturing a helper class that can inspect all the FKs in a database and traverse them back to a tenant root table in order to verify that FKs don't cross tenant boundaries. I think this would output a large SQL script you can run yourself in SSMS to verify tenant isolation.
The text was updated successfully, but these errors were encountered:
copied from adamfoneil/SqlServerUtil#13
Would be neat if there was an easy way to verify tenant isolation after a migration. In a complex database, it can be hard to know if you mapped every FK as necessary. When you craft a migration in code with SqlMigrator, you simply go from memory/intuition about what FKs need to be mapped.
I'm picturing a helper class that can inspect all the FKs in a database and traverse them back to a tenant root table in order to verify that FKs don't cross tenant boundaries. I think this would output a large SQL script you can run yourself in SSMS to verify tenant isolation.
The text was updated successfully, but these errors were encountered: