Question

Here's my problem at a high level:

We have two business applications. App1 inputs and stores a large set of data. We need something that will transfer data from App1 to App2 whenever any relevent data in App1 has changed. Essentially we want the data in App2 to be synchronized from App1, except that App2 contains a subset of the data.

App1 uses a SQL Server 2000 database.

App2 uses a SQL Server 2005 database.

So, for example, if a user is using App1 and they update some data, that data needs to get saved to the App1 database and then sent to the App2 database, as realtime as possible.

Looking for some good ideas that won't bring either system to its knees.

Was it helpful?

Solution

Have you considered replication?

OTHER TIPS

Presumably you could state this as "When an event of interest occurs in System A, invoke Action B to asynchronously (i.e. decoupled) update System C."

Sounds like a message queue - either formally, or in a database table.

Some might think "trigger", but there's a deadly synchronous dependency there. But a trigger could feed the queue.

Are they in different physical locations? Why can't you use a single database and only allow app2 to access the subset of data that it is allowed to?

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top