Handling Database

[Jayakrishnan]

i have to search data from a database containing 2 million records. i get timeout error while using order by statement
(in order to paging using top *)
pls sugest me any new methods.....

[wrack]

First of all I would suggest you not to use Access if you are using.

Second use some proper Database System like SQL Server or Oracle.

Also use some sort of filtering mechanism which allows you to lower the number of records you are going through.

If nothing is possible then this is how it's going to work. On my P3 800 MHz machine with 384 MB or RAM in access database it takes 16 seconds to sort 50000 records so it will take nearly a minute to do what u want.

Change the timeout value to something larger like 120 seconds.

Cheers.

[Jayakrishnan]

i am using sql server 2000

its a search engine like web application

i want to show total matches , and show the result page by page

its ok in my system, but when uploaded to sever it gives unexpected results.

pls comment on it

[wrack]

You do understand the amount of data generated by such a huge dataset and since you are taking about web application it's not wise to handle that much data in one go.

What kinda errors you are getting..?

Cheers.

[MrNorth]

* Why not use SQL code to return only the amount of rows you want to see on the client side

*If you return that many posts, I recommend you return them to a datagrid with paging enabled.

*I suggest you provide the user with more parameters for the search to limit the stress of the webserver/database server

Also if you haven't set

if not page.ispostback then

binddata()


then please do so. Also remember that events like "onindexchanged" are handled AFTER pageload...

just a few quick tips that came in my mind