Desired result is not getting from SQL query when the number of rows become large

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

I am using SQL Server 2005 Express edition for my Application. I gets the correct result for the queries with smaller number of rows. But the number of rows become 12000 or greater, result is not in the desired order.

(My machine's configuration is Intel core 2 duo processor, 2 GB RAM, Windows Xp Professional service pack 2.)

Is this the problem of SQL Server 2005 Express edition,or my query?

Please help me... Thanks in advance...

Posted 5-Jan-12 20:07pm

ArunBose

Updated 5-Jan-12 20:11pm

v2

Add a Solution

Comments

devbtl 6-Jan-12 2:20am

put some piece of code here.

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)

Mehdi Gholam · Answer 1 · 2012-01-05T20:17:00

Solution 1

Most likely it is your query and you need to build indexes for your tables.

Posted 5-Jan-12 20:17pm

Mehdi Gholam

Sridhar Patnayak · Answer 2 · 2012-01-05T20:21:00

Solution 2

Dear Arun,

I think it requires indexing.

use this link to create indexes

Defining Indexes with SQL Server 2005[^]

creation of primary key and foreign key relationship in database , will make faster access.

Thanks,

Posted 5-Jan-12 20:21pm

Sridhar Patnayak

Updated 5-Jan-12 20:22pm

v2

unclejimbob · Answer 3 · 2012-01-06T01:17:00

"But the number of rows become 12000 or greater, result is not in the desired order."

If this is the crux of the problem then I am guessing the query contains a clause you expect to order the result but which isn't, or rather which _sometimes_ orders the result, i.e. a 'group by' or a 'select distinct'

Again without actually seeing the code I'm just taking an educated guess but if you are expecting the result to appear in a particular order then the only way to ensure this is to use an 'order by' :-)