3

There is legacy solution where 2 applications communicate with each other via SQL Server 2008 R2 database table.

Application "A" inserts information to database table from time to time Application "B" polls database once per second to find out new records

I guess there may be more sophisicated approach how application "B" finds out when new records appear.

user149691
  • 587
  • 1
  • 5
  • 19

1 Answers1

1

It depends on many things that are not explicitly stated in your question. Is that for one table only? For a limited set of tables? For all tables? Do you have full control on both applications?

Let's suppose this is for one table only and you can't modify A application because you don't control its sources. One way would be to use a message queue like described here combined to a trigger on that table.

If you control both applications, don't use the database as a singleton an go for message queues directly ...

David Brabant
  • 41,623
  • 16
  • 83
  • 111