Re: Performance of Rushmore
- From: "Edhy" <erijo@xxxxxxx>
- Date: Sun, 22 Jan 2006 12:41:00 -0500
Waler,
FoxPro data is not a client server database, so always in a network situation all the data will travel over the wire and the filtering will be done in the temporary map of the data in the workstation. Te reason its faster the next time is because the data may be already in memory so it does not need to bring it all again, until you do a FLUSH or something that requires the data to be refreshed.
IOTH, using MySQL, ORACLE or MS-SQL with FoxPro Remote Views or Cursor Adapter, as long as you parameterized the view or CA you will get only the records you are filtering on, which makes VFP a big player dealing with remote data.
Edhy
"WPa" <wpaul_nospam@xxxxxxxxxxxxx> wrote in message news:e1LWPE3HGHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
I have an application written in old FPW 2.6. My question is:
when I make "SELECT * FROM xxxxx WHERE conditon", then all the data travels from the file server to the workstation, and the workstation does the filtering, as long as the condition is not Rushmore optimizable. But what happens when the condition is optimizable, that means can use an index in the cdx file? Do also all the records travel to the workstation? How can it be so fast?
Waler
.
- Follow-Ups:
- Re: Performance of Rushmore
- From: Matthew L Reed
- Re: Performance of Rushmore
- References:
- Performance of Rushmore
- From: WPa
- Performance of Rushmore
- Prev by Date: Performance of Rushmore
- Next by Date: Re: dbconnect to SQL Server
- Previous by thread: Performance of Rushmore
- Next by thread: Re: Performance of Rushmore
- Index(es):
Relevant Pages
|
