Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
gavinokane
Starting Member
5 Posts |
 Posted - 2009-07-11 : 19:42:09
|
| Hi,I've taken on a redevelopment project and i'm not a SQL expert although I have a fair amount of SQL knowledge.The first thing i spotted when looking at the database was that it was not normalised to any great extend. Not only this but any FK references were not actually specified in the database schema. When I queried this with the developers they said..."that's not a problem...we've got the tables joined in the queries using joins".My previous experience has taught me to create table joins when designing the database and implementing these constraints on the table at design time.What are the downfalls of not implementing the foreign key constraints on a database schema? (I assume referential integrity of data is one).RegardsGavin |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-07-12 : 04:15:28
|
| not implementing fk constraints means you need to manually check each time if referential integrity is maintained. setting fk will do this for you automatically and saves you some effort. |
 |
|
|
gavinokane
Starting Member
5 Posts |
Posted - 2009-07-12 : 16:56:27
|
| Thanks for your feedback. Much appreciated. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-07-13 : 14:28:09
|
| welcome |
|
|
|
|
|
|
FK versus Query table joins