asked on saving data in temporary file and transferring it to db when network connectivity is avialable
I have vb.net application running on windows 8 tab, Requirement is, doctor enters the investigation advised in a tab while going to rounds for a patient which has to be saved to temporary file.( this is because, some places wi connectivity may not be available).
When the connectivity is established, the data saved in file should get automatically transferred to the DB in the background.
How to achieve this result.
When the connectivity is established, the data saved in file should get automatically transferred to the DB in the background.
How to achieve this result.
Visual Basic.NET
Last Comment
vensali
I would use a local database and replication.
ASKER
how to handle the connectivity issue between local db and production DB. can it be automated? I,e a background process will keep checking the connectivity between the two dbs and when the connection is established, it automatically replicates the data.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
As i see the typical set up in my case would be as mentioned below,
I have multiple tabs (win 8) with sql server 2008r2 std edition installed. Each instance of the tab will be configured as publisher. i have one server configured as distrubutor and one server configured as subscriber. the data is captured in each of the tab will be consolidated in the subscriber sql instance.
publisher
Tab 1 - Hosp no 1 -- row 1
row 2
Tab2 - Hospno 2 -- row1
row2
Subscriber
Win2008 server with sql2008r2
Hospno1 row1
row2
Hospno2 row1
row2
What is the ideal replication configuration in this scenario
I have multiple tabs (win 8) with sql server 2008r2 std edition installed. Each instance of the tab will be configured as publisher. i have one server configured as distrubutor and one server configured as subscriber. the data is captured in each of the tab will be consolidated in the subscriber sql instance.
publisher
Tab 1 - Hosp no 1 -- row 1
row 2
Tab2 - Hospno 2 -- row1
row2
Subscriber
Win2008 server with sql2008r2
Hospno1 row1
row2
Hospno2 row1
row2
What is the ideal replication configuration in this scenario