SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-28-2008, 05:50 AM
| ||||
| ||||
 Using Triggers to Maintain a Table to prevent complex join statements... We have a statement that joins 8 different tables to pull multiple rows from each table. I have heard of people using triggers to create, update and delete records in a table based on statements in other tables. The obvious result of this would be to SPEEEEEED up results right?  I'd love to find someone with experience with this that I can pick info from. lol There isn't really a 'best practices' guide that I can find beyond what is in the normal documentation.      |
|
02-28-2008, 05:50 AM
| ||||
| ||||
| Re: Using Triggers to Maintain a Table to prevent complex join statements... Cory Robin wrote: > We have a statement that joins 8 different tables to pull > multiple rows from each table. > > I have heard of people using triggers to create, update and > delete records in a table based on statements in other > tables. > > The obvious result of this would be to SPEEEEEED up results > right? > > I'd love to find someone with experience with this that I > can pick info from. lol Post the SQL you are using and I'll give you a hand. Cheers! Jay |
 |
« Alter table - adding constraints?
|
Duplicating contents of DB within same DB with different prefix »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 08:36 AM.
