Improving the reading time of an sql server view

Question

0.00/5 (No votes)

See more:

Hi ,

I have a view that is getting a large data.And i am calling this view through a web method.So i need to make reading this view faster since it is displaying data on a jquery map and i need it to be fast.So i had the idea of storing it in a session instead of hitting the database everytime but storing it in as session is not a good idea for large number of users.Also i thought about storing it in the cache but the user might disable caching or clear the cache.So is there any suggestion to read this view in a fast way ?

Thanks.

Posted 6-Jul-12 7:35am

mhamad zarif

Add a Solution

Comments

ZurdoDev 6-Jul-12 13:41pm

Depending on the type of view, you can at least index it to improve the performance. Otherwise cut down on the amount of data you are pulling.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Stephen Hewison · Accepted Answer · 2012-07-06T08:08:00

Using SQL Management Studio you can view the execution plan. This shows you how SQL builds your result set.

There are people who earn very good money reading these and squeezing the last few milliseconds out of them.

The following is a code project article with covers doing this with a very simple example.

SQL Tuning Tutorial - Understanding a Database Execution Plan (1)[^]

It's all about having the right indexes so that SQL can join the tables and filter the rows with the least effort. The execution plan shows you how long was spent at each point of the query so you can see which parts cost you the most processing time.

If when you get the correct indexes in the place and you can't squeeze any more out your query. You many need to consider using Analysis Services instead. Where you have queries with complex aggregations, you can get a huge reporting improvement by using Analysis Services. In a nutshell it pre-aggregates all the possible results. The following is a step by step introduction.

http://www.scribd.com/doc/88610541/SQL-Server-Analysis-Services-tutorial[^]

Despite this there are also application approaches to this that would also work. I agree putting large quantities of data into the session isn't a good idea. Especially if you've implemented web gardening and are having to serialise items in and out of your session state.

If you want to take the application approach, I'd write a self hosted WCF service. This is an introduction to WCF services. I'd always choose self hosted as you don't get multi-process issues associated with web gardening or start up latency issues associated with IIS worker processes.

http://invalidcast.com/2010/04/a-gentle-introduction-to-wcf[^]

When creating this kind service which is caching data it's important to understand Concurrency and Instancing to ensure subsequent calls have access to the same data. The following is an excellent article which explains the behaviour of theses.

WCF Concurrency (Single, Multiple, and Reentrant) and Throttling[^]