Greetings, I have the following senario: Database DB1 acts as the central security database and contains the user, gorup tables Database DB2 is my application database. Any number of other application databases can use DB1 for their user/group accounts. Problem: when application2 modifies/adds a new record in the user table in DB1, how can application1 be notified of this modification ???

OMAR

Not from the database, (Oracle has some notification system if I recall correctly, but I never looked into how it works/what's needed to make it work), or you have to go the nasty route of triggers calling extended stored procedures which call into a managed C++ assembly which notifies your .NET application.

I think it's perhaps ok to set up some sort of central messaging system which receives from application 2 a notification some record has changed and sends it to the subscribers, for example application1. As application 2 knows when it changes a userrecord, it can make the notification at the right time (i.e.: when the transaction has been completed).

I believe SQL 2005 has a notification feature...

jeffreygg wrote:

I believe SQL 2005 has a notification feature...

Yeah, I read some marketing about that too, though, it is my understanding the notification is implemented in .net in the ASP.NET layer. (please correct me if I'm wrong), to mark changed items in the cache so they're re-rendered.

SQL Server 2000 Notification Services

http://www.microsoft.com/sql/NS/default.asp

I hear good things, never tried it.

swallace wrote:

SQL Server 2000 Notification Services

http://www.microsoft.com/sql/NS/default.asp

I hear good things, never tried it.

Whoa, never knew their existence I'll have a look.

COM+ Loosely coupled events could be used OR WSE2 messaging & routing, OR MSMQ, or BizTalk (probably overkill)

Basically, it sounds like youre trying to implement the features of BizTalk Single Sign On (SSO) but without all of the complexities and cost associated with BizTalk. So, maybe you just need one way reliable messaging.

Basically, it sounds like youre trying to implement the features of BizTalk Single Sign On (SSO) but without all of the complexities and cost associated with BizTalk

Yes.. thats exactly what I am trying to do. Right now I have a trigger in the central SignOn database to cascadr changes to other databses on per application. So, If a new application requires this SSO database, I have to add code to the trigger to support data notifications for the new application's database.

SQL Server 2000 Notification Services

I have been trying to figure out what exactly this product do, especially because MS web sites promotes it in a different manner. I don't know if it will help in a senario like mine