Click here to Skip to main content
15,892,161 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I have an application tied to a SQL Server S005 DB that I'd like to ensure stays up to date between multiple clients. When one client updates a certain table, I'd like the other clients to show this change as well. The clients will all be on an internal network and in some cases a VPN. The number of clients probably wouldn't exceed 20 at any given time.

My lazy-man's take on this is to run a thread on the client that updates their dataset aggressively (pausing when the user needs to edit of course). I've implemented this and it works pretty well. But I'm a bit concerned with the server being hit every few seconds by x number of clients.

So my less lazy method is to register a service via RemotingConfiguration.RegisterWellKnownServiceType and write a second library with code for the SQL Server to run which will contact all known clients and force them to update. This also worked pretty well in testing outside of SQL Server. It did not work when testing from SQL Server.

I came to realize that the library System.Runtime.Remoting is not one of the allowed .Net assemblies.

I now have three options I can think of:
1. Write a server that the clients talk to in order to force an update.
2. Have the clients talk to eachother.
3. Have SQL Server execute the remoting code as a separate application.

Advice concerning these options or options which I have not considered would be greatly appreciated.
Posted

1 solution

Try using SQL server replication with trasact... replication
its more safer method to keep data cocurrently.
 
Share this answer
 

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900