Click here to Skip to main content
Rate this: bad
good
Please Sign up or sign in to vote.
See more: C# SQL database Solution problem , +
Hi everyone Smile | :)
 
I have a Store Management System for a company that have 4 branches and each branch have 4 system clients.
 
The 4 branches works on a central database over internet connection, the problem here is the data saving and retrieving are more slow.
 
So there is any solution for this problem or there is another module to be implemented ?
 
Thanks in advance
Posted 30-Apr-13 7:14am
Comments
learner'sbug at 30-Apr-13 12:43pm
   
So you have a common DB for all the clients ?
AhmedYehiaK at 30-Apr-13 12:44pm
   
ahaaa i have a common DB for all clients
learner'sbug at 30-Apr-13 12:49pm
   
So Data sync approaches that OP has suggested don't apply, first of all you need to identify the problem by doing some profiling. Try using fiddler for traffic information and use SQL profiler for SQL side of it.
AhmedYehiaK at 30-Apr-13 12:51pm
   
there is no problem if there are another module to be implemented like Data sync approaches if this module will solve the problem

1 solution

Rate this: bad
good
Please Sign up or sign in to vote.

Solution 1

There are various options to you, and this is a very broad approach to things.
It also depends how you want to operate.
 
If the sites do not need 100% up to date information then you could use Data Synchronisation approaches:
Choose a Data Synchronization Technology[^]
 
If they do need upto date information then you could work on a paging method when retrieving large amounts of data, or refine how your data is transmitted between them. When submitting information take advantage of threading and handling failures on a call back method. This means you can submit large amounts of data and keep using other aspects of the program while it submits if that suites your operation.
 
You could also look into compression which could be applied.
 
Without knowing much more about your system it is hard to advice but those are some approaches that could be considered.
  Permalink  
Comments
AhmedYehiaK at 30-Apr-13 12:48pm
   
Initially i think that data synchronization is more suitable
Pheonyx at 30-Apr-13 12:55pm
   
It is your system, as I stated without knowing a lot more about how you operate and what your business requirements are it is only loose advice we can give. If you only have 1 central database and do not want to have additional ones on the local sites then data synchronization is not applicable. If you are not bothered about adding "holding" databases at each site then it might be the right approach. There is a lot of information about this sort of thing available and I would advise looking at your chosen approach in a lot of detail before looking to implement it.
AhmedYehiaK at 30-Apr-13 20:22pm
   
thnx a lot :)

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
0 OriginalGriff 200
1 PIEBALDconsult 150
2 BillWoodruff 148
3 Jochen Arndt 135
4 DamithSL 130
0 OriginalGriff 5,695
1 DamithSL 4,506
2 Maciej Los 4,007
3 Kornfeld Eliyahu Peter 3,480
4 Sergey Alexandrovich Kryukov 3,190


Advertise | Privacy | Mobile
Web01 | 2.8.141216.1 | Last Updated 30 Apr 2013
Copyright © CodeProject, 1999-2014
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100