However per your other comment it is probably a network problem.
Your other comment suggest that a query without the image data is a "bit" faster.
A query without the image data would be smaller than one with it. And a network problem would have more problems with more data. Thus that fits.
A database problem with the size that you suggested in another comment seems very unlikely unless you did something very odd with the database. And I can't image how you could have messed up the client side that would cause a slow down.
There are various ways to test network performance which you can google for.
Thanks for all your help and suggestions and your time for replying.
With your suggestions and replies now am planning to change my application to take the image from shared disk using web browser control in my application and database connection would be using web services.
Hello, Can i get step by step tutorial on how to program fingerprint recognition using c#.
I don't know how to start fingerprint system with c#.
I want to know following.
1. what database is suitable used for fingerprint data saving? (mysql, access or ...)?
2. how to save image in database?
please help me.
thank u so much.
This depends on how much data you need to store in the database.
If its just a few users and you can store your database on a file server go for Access.
MySql provides you with a free option while you may need to pay for other databases.
Sql Server or Oracle would provide you with many powerful options for enterprise level applications.
The way you store images will be vary slightly from database to database.
Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore, Dream. Discover.
Search for digitalPersona in google. They are one of the leader in finger print recognition. You can purchase the devices and also you can get their SDK that make your life easy.
The SDK process has two important steps.
1) Registration: Forming single Registration template by taking the same finger input for at-least 4 times (This will be stored in the database as binary object. Kind of gray scale image formed from the registration templates). The template should be registered for a user of the application
2) Verification: Takes the finger input of the user, walk through the registration template in the in database (Actually you should read the template one by one and ask the sdk that verification succeeded) and a match occurs, you know who the user is..
Note: The finger prints are unique, if a match occurs between verification and already registered template, then you know who the user is.