I've only test SQL server with 4000-5000 records and have not seen this
problem. If you are returning 1.5 million records in a query with say
100 byte records then you are cacheing 150 MB on the server with this
query. Depending on the memory size on your server and how fast the
server can get this stuff off of disk maybe the reason for the slow
Better yet why don't you use PervasiveSQL (www.pervasive.com). It
contains a navigational as well as a relational SQL engine. It doesn't
consume any memory at all in navigational(aka transactional) mode
except for the records the user has on the screen. You can
simultaneously use the SQL engine with the navigational engine.
Although the SQL level support is not as accomplished as SQL server it
is starting to get there and the transactional model beats the pants
off SQL server "dumb stuff" if you know what I mean.
Professional Flight Managment
> I am using VB6 SQL7.0 and the ADO Connection
> SqlStr = "Select * FROM POS "
> rs.Source = SqlStr
> rs.CursorLocation = adUseServer
> rs.Open , , adOpenDynamic, adLockOptimistic
> then i fill a Grid in unbound Mode via the rs.move function. If i
> single steps it runs fast but a move from record 10 to record 20.000
> extremly long (22sec.)
> 1. I have to use the Serversided Cursor because the Database holds
> 1.5 Million Records. (A Client Cursor will copy the recordset in to
> clients memory)
> 2. I can not reduce the reordset with a "where" because the user has
> scroll the hole table
> any Ideas ?
> Christian Eckler
Sent via Deja.com http://www.deja.com/
Before you buy.