Home/ Questions/Q 477527
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T00:36:00+00:00

I have a very limited experience of database programming and my applications that access

  • 0

I have a very limited experience of database programming and my applications that access databases are simple ones :). Until now :(. I need to create a medium-size desktop application (it’s called rich client?) that will use a database on the network to share data between multiple users. Most probably i will use C# and MSSQL/MySQL/SQLite.

I have performed a few drive tests and discovered that on low quality networks database access is not so smooth. In one company’s LAN it’s a lot of data transferred over network and servers are at constant load, so it’s a common situation that a simple INSERT or SELECT SQL query will take 1-2 minutes or even fail with timeout / network error.

Is it any best practices to handle such situations? Of course i can split my app into GUI thread and DB thread so network problems will not lead to frozen GUI. But what to do with lots of network errors? Displaying them to user too often will be not very good :(. I’m thinking about automatic creating local copy of a database on each computer my app is running: first updating local database and synchronize it in background, simple retrying on network errors. This will allow an app to function event if network has great lags / problems.

Any hints and buzzwords what can i look into? Maybe it’s some best practices already available that i don’t know 🙂

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Sorry this is prob not the answer you are looking for but you mention that a simple insert / update could take 1-2 minutes or even fail with timeout / network error.

    This to me sounds like there may be another problem rather than the network itself. If your working on a corporate network there would have to be insane levels of traffic for this sort of behavior. I would do everything in your power to look at improving the network before proceeding. Can you post the result of a ping to the db box?

    If your going to architect your application around this type of network it will significantly alter the end product and even possibly result in a poor quality product for other clients.

    Depending upon the nature of the application maybe look at implementing an async persistence queue and caching data on startup or even embedding a copy of the db into your application.

    • 0