The database is for an insurance company. There is very much traffic at peak times. It has two servers, one located in the U.K. and another in India. The client machine is installed in India. From there they access both servers. At peak times the perfomance is very bad. All database design and other things are perfect. The problem is in the client application design, I think. Can we use the Singleton design approach on this application?
I'm assgned to suggest a redesign strategy for this one. If you are familiar with this kind of thing please re...
You should confirm that the database is not the bottleneck. The best way to do so is to trace a typical session. If the total elapsed time for database service is small compared to the total elapsed time for the operation, then the bottleneck is not in the database and you'll have to inspect other application or network components.