New Posts New Posts RSS Feed: Working with a Distributed Database
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Forum LockedWorking with a Distributed Database

 Post Reply Post Reply
Author
Customer View Drop Down
Senior Member
Senior Member
Avatar
User Submitted Questions to Support

Joined: 30-May-2007
Location: United States
Posts: 260
Post Options Post Options   Quote Customer Quote  Post ReplyReply Direct Link To This Post Topic: Working with a Distributed Database
    Posted: 06-Jun-2007 at 3:47pm

Question:

There are many aspects to your product that are appealing; however, it appears as though there is a fixed architecture based on a centralized database.

Is it possible to have a distributed database architecture where individual clients have their own specific data and communicate with a central database for updates?

SQL Server is ideally suited for this, with distributed, royalty-free SQL Express clients communicating via a service broker to a centralized main SQL Server. However, from my quick assessment this capability does not appear to be supported within your framework.

Back to Top
IdeaBlade View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 30-May-2007
Location: United States
Posts: 353
Post Options Post Options   Quote IdeaBlade Quote  Post ReplyReply Direct Link To This Post Posted: 06-Jun-2007 at 3:48pm

Answer:

It is true that most of our documentation describes building applications using a centralized database, but one of the strengths of our product is the ability to provide disconnected support.  When working while disconnected, there are two different strategies.  The first (and simplest strategy) allows objects in the persistence cache to be stored and loaded into and from files in the file system.  These files can be encrypted if desired.  You can see an example of this strategy in our tutorials. 

This strategy works fine in many situations, but in other situations where the application is more complex and the database is quite large, we recommend the use of a local database such as SQL Server Express.  We do have customers who started out providing disconnected support to their customers through the simple local file mechanism, and then moved to a distributed database design.

 A distributed database design requires support for a number of features.  One of these features is good support for concurrency conflict resolution.  We provide excellent support in this area, and I would encourage you to look at our tutorial on this subject.    We do not yet have a service broker that allows SQL Express clients to communicate with a main SQL Server, but we'd be happy to talk to you about this requirement.  There is nothing in our architecture that prohibits the use of such a broker, and, in fact, it is a crucial component of our long-term plan to provide ever better support for disconnected use.


 

Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down