|
|
|
|
| Re: how can we make fast search in large no. of records? [message #137195 is a reply to message #136837] |
Tue, 13 September 2005 13:22   |
ribha
Messages: 17
Registered: August 2005
Location: pakistan
|
Junior Member |
|
|
well i m working on "attendance system" of an office well if there are currently 800 employees working and there are 600 are posted in different locations. what i want is to check the validity of employee by its card, the problem is that if the emplyee is posted some other location how can i check is he/she is valid for current location at attendance time, and there is no much time for checking each person's card. so i want a fast search to fine is the card no. is exist in 800 records or not.
|
|
|
|
| Re: how can we make fast search in large no. of records? [message #137216 is a reply to message #137195] |
Tue, 13 September 2005 19:15 |
 |
djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia
|
Senior Member
Account Moderator |
|
|
If the locations use their own database and don't all 'hook' into the one central system, I would suggest that you replicate the database between the various locations so that all the 'employee' details, that are needed for verifying access, exists at each location.
Alteratively, create a materialised view that is the union of the table from the separate installations. This would use dblinks to connect to the other databases on the different machines. This materialised view can then be indexed, but with 800 records making the materialised view memory resident is another alternative.
David
[Updated on: Tue, 13 September 2005 19:15] Report message to a moderator |
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
