Best way create SQL db on network

Question

5.00/5 (1 vote)

See more:

I'm working on hospital project that will run the hospital over offline lan network, i created server pc and other pc's have no sql server or databases, just connect to the server directly, the system depends on sql dependancy to monitor the data changes by all pc's to get last updates from the server, but their are some problems in this way, sometimes booking updates delay

What I have tried:

i heared that there an another way like creating a sql database on each client pc and sync with the server, anyway i want to know what is the best way solution in this situation?

Posted 15-Feb-18 10:16am

XRushdy

Add a Solution

Comments

phil.o 15-Feb-18 16:32pm

Creating a database on each client PC would only add some overhead to the whole system, and would only make things worse. How much delay are we talking about?
You should carefully analyse your issue and find out the reason for the delay; adding layers onto existing one would certainly not resolve the issue.

mvdk72 5-Mar-18 7:59am

Creating real-time or near real-time solutions in an offline situation sounds like a contradiction to me. Either you start polling from the client every x seconds (near real-time) or, and that may be a better solution looking at your question, create a client-server solution where your client is listening to changes on the server side (WCF callbacks over TCP for example). Is there a compelling reason to work disconnected? Problem you are describing sounds more like an architectural issue then a technical issue at this point of time

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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