Referential integrity in a relational data warehouse. Is it worth it? and what are the alternatives?

If you needed to create a relational data warehouse of biblical proportions using SQL Server 2008, would you use foreign keys to ensure data integrity or would you use other methods?

I like foreign keys because you only need to get them right away, and they are always there to protect integrity. I was thinking of disabling, loading, enabling the route.

Any thoughts?

Thanks in advance.

+5
source share
3 answers

-, , () . "" , SQL?

+2

, ! , - , . , , . () , , ?

, - , - , .

, , - , , . , , . , ( ), , , , .

, !

+1

, . , , , , .

, : ; ; , ; , .

+1

All Articles