Hendra-
You gain a small performance advantage by not defining referential integrity as
long as you define indexes on the Foreign Keys. When you have RI defined,
Access must probe the "parent" table each time you add a row in the "child"
table or change a FK value in the Child table. Why do you not want to define
RI? If you do decide to implement RI, be sure to delete all indexes on Foreign
Keys because Access will build an extra hidden index on the FK when you define
RI.
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Kirkland, WA)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of
agesthahendra@ymail.com
Sent: Monday, February 27, 2012 7:30 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Relationships
Hi All,..
Assumed :
- We have indexed all of the foreign key on many sides
- All Join are builded in Queries as we need
- Ignoring Enforce Reffrential Integrity
Do we still have to build relationships between tables..? What about
performance..? Are there any performance effects if we don't build relationships
between tables..?
Any explanation would be appreciated, thank you...
Regards
Hendra
------------------------------------
Yahoo! Groups Links
Tidak ada komentar:
Posting Komentar