|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Faster return of large recordset
Hi,
I remember reading somewhere that there is a faster way to retrieve a large recordset to display it in a table, could anyone point me in the right direction. Thanks, Sanjay |
|
#2
|
|||
|
|||
|
Faster than what?
|
|
#3
|
|||
|
|||
|
Your right, I'm using Dreamweaver to extract 1000 records but it takes a long time to display,
The query is: PHP Code:
I just wanted to know the most effeicient method for displaying these results (1000 - 1500) records with approx. 25 fields. Thanks, Sanjay |
|
#4
|
|||
|
|||
|
You can specify the column names individually rather than use *. Generally this is a bit faster.
Look at indexing the monthentry column if it isn't. |
|
#5
|
|||
|
|||
|
I'm retriving all the fields, should I still specify each column?
I'm looking at trying to optimise the DB, Is there any reason why I should not index say 10 columns rather than one? Also, should I increase the MaxBufferSize or MaxScanRows (not sure what they do) in the ODBC setup dialog? Thanks, Sanjay |
|
#6
|
|||
|
|||
|
Even if you need all the columns, specifying the column names saves the db server some work. I've read it's faster, but I don't work in heavily loaded environments often so I can't say for sure.
Indices put extra load on the server when inserting or updating, I try to index only what's necessary. If it's your server you can try tweaking the ODBC properties. |
|
#7
|
|||
|
|||
|
Thanks Doug,
We are on a dedicated server, I just wanted some help in what options I could set to maximise performance for the DB, I've not seen anything around - any help would be welcome. Regards, Sanjay |
![]() |
| Viewing: Dev Shed Forums > Programming Languages - More > ASP Programming > Faster return of large recordset |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|