How to Optimize SQL query speed and Large field data in SQL

Question

0.00/5 (No votes)

See more:

SQL-server-2000

SQL-Server-2005

, +

When the data up to 10000 my application had spent more than 10s get the data.So It big problem.How to reduce the select sentence time.In the structure of the table there have three big field data,length "varchar(3000)".Please help ,tell me how to Optimize.

All of the Data must be see.So if the table have 10000 ,it show 10000.It also pageing ！Now the Problem is how improve the speed and Optimize !

Posted 4-Jul-11 21:10pm

AngelLoose

Updated 5-Jul-11 16:57pm

v3

Add a Solution

Comments

[no name] 5-Jul-11 3:15am

please provide us the Query....
Because 10000 records are toooo less for SQL Server database to handle.

3 solutions

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)

fjdiewornncalwe · Answer 1 · 2011-07-05T16:38:00

Solution 2

Your data likely needs to have indexing set up and perhaps some normalization needs to occur. The likelihood that a user requires 10000 large records at a given time is highly unlikely and I would suggest that you need to perhaps use some form of paging instead of just looking at the query alone.

Posted 5-Jul-11 16:38pm

fjdiewornncalwe

Comments

harish85 5-Jul-11 22:53pm

my 5, and ignore my solution.

*dan!sh* · Answer 2 · 2011-07-04T22:17:00

Solution 1

You need to analyze your database schema and the way query has been written for that. This is far too less information to give a proper response.

Check the Execution plan for the query. You can also use SQL tuning advisor.

Posted 4-Jul-11 22:17pm

dan!sh

djrocks0101 · Answer 3 · 2011-07-05T16:43:00

Solution 3

I think Your database is not normalized and no indexing has been done. So Normalize your database and do indexing, it can help you a lot. If still you have performance related problems check execution plan for the query.

Posted 5-Jul-11 16:43pm

djrocks0101