November 13, 2009 at 8:44 am
I have a view which is called in the front end ,but the view contains 12 joins in it, using one view and several tables
we are planning to change that view and create a stored procedure and call that one
or else
move the whole data i.e view data into another table and place a trigger on the new table so that it updates when ever the data is updated on the view ie..the tables..
so please give me which one would be good performance wise....
November 13, 2009 at 5:14 pm
Views and stored procedures are used for two different things. A view encapsulates a single query and presents it as a table. A stored procedure is a code block.
What I'd suggest you do is post some DDL and the query and try to tune that better. 12 joins is not necessarily an issue, depending on what you have indexes and the query.
Using a trigger may or may not be warranted, but that might cause you blocking as well if you are already having performance issues.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply