I have to write a query with lot of computations.
Is it a good idea to create indexed view with this computed columns instead of writing a stored proc?
I have to write a query with lot of computations. Is it a good
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have to write a query with lot of computations.
Is it a good idea to create indexed view with this computed columns instead of writing a stored proc?
It depends!
If you create an indexed view you’ll be trading increased costs in terms of greaer storage space requirements and slower inserts, updates & deletes for increased speed of accessing these computed values. If you only want to use these values once or occassionally, you might be better off computing them on demand in a SP but, like I said, it depends!
There are other factors to consider to, including: over how many records do these computations need to execued? If it’s just a few, the indexed view approach may not be appropriate because it may affect all rows unless you limit it with sutable WHERE/HAVING clauses – remember that an indexed view isn’t parameterised.