| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Cory Robin | Date: | February 21 2007 4:48am |
| Subject: | Using Triggers to Maintain a Table to prevent complex join statements... | ||
| View as plain text | |||
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.
| Thread | ||
|---|---|---|
| • Using Triggers to Maintain a Table to prevent complex join statements... | Cory Robin | 21 Feb |
| • Re: Using Triggers to Maintain a Table to prevent complex join statements... | Jay Pipes | 22 Feb |
