1

I have an existing client-server 3-tier application with the following stack :

  • Smart-Client (Win-Forms)
  • IIS/ASP.NET
  • Sql server

Some of the data is stored in Entity–attribute–value (EAV) model. All primary keys are integer identity columns. Database operations are mostly performed using Stored procedures.

I am tasked with converting this application into an occasionally connected application (OCA)

There should be no issues with installation and resources limitation on the clients.

This is the first such project for me.

I have done some reading about

In order preserve existing code and limiting change impact, I am considering installing the the 3-tier application on each client , using sync framework to handle synchronization on the WS to handle synchronization. Also having one master server to which synchronizations will refer.

Does this solution look feasible?

Are there any other resources regarding converting an on always Connected 3-tier application to an occasionally connected application ?

Thank you .

JuneT
  • 7,840
  • 2
  • 15
  • 14
user3253163
  • 13
  • 2

1 Answers1

1

should be feasible. not much change in your app. you just have to install a local database on your clients.

however, your're using identity columns. unless you partitioned your identity values (client 1 is 1-1000, client 2 is 1001 - 2000, etc...) you will duplicate IDs when you upload them.

have a look at this: Database Sync:SQL Server and SQL Express N-Tier with WCF

JuneT
  • 7,840
  • 2
  • 15
  • 14