Subject | performance improvements |
---|---|
Author | Gediminas |
Post date | 2003-10-19T23:10:54Z |
while reading tips to improve performance found statement, that dublicate
primary & foreign keys indexes downgrade performace.
If I have two tables A & B (master-detail relatioship), so I need to set
indexes only for A & B primary keys? do I need a foreign key for foreign
key in A table or this would downgrade performance?
if using stored procedures & select from it (select * from
StoredProcedure(params)), prepare would take everytime if I set SQL
dynamically (this select would occure everytime before opening one form
while other select would be set to open another forms)
--/ Gediminas /--
The Truth Is Out There
primary & foreign keys indexes downgrade performace.
If I have two tables A & B (master-detail relatioship), so I need to set
indexes only for A & B primary keys? do I need a foreign key for foreign
key in A table or this would downgrade performance?
if using stored procedures & select from it (select * from
StoredProcedure(params)), prepare would take everytime if I set SQL
dynamically (this select would occure everytime before opening one form
while other select would be set to open another forms)
--/ Gediminas /--
The Truth Is Out There