Alternatives to Query Notifications using .NET 3.5 and MS SQL 2005 Server

[TamusJRoyce]

I'm looking for some alternative methods to replace Query Notifications in a current application I am working on. I have so far been searching for Alternatives to Query Notifications, but I can't seem to find the results I need.

The reason is that my Application has grown to over 15 users while still needing to keep each clients synchronized with changes made to the server. I currently have a custom data layer performing caching and dealing with QN, but if I am also able to push some of this caching onto the server, it would be extremely helpful.

Memcache is one approach I have thought of, but I am unsure if this notifies the clients when items are changed. Another idea is to have a separate project that runs on the server and notifies all the clients that attach to it, but I'm not sure what to search to find information on how to implement this.

I guess I'm not asking for specific code (or links to documentation outside of bytes.com), but rather some specific tools and maybe modeling ideas that would help guide me where I need to look.

Hopefully Helpful,

TamusJRoyce

[TamusJRoyce]

I guess this is a specific question psuedo-related mssql and not sql itself. It would be helpful if someone could mention that questions like this may be off-topic (even something like a thumbs up/down to the effect of it being so--but just a quick idea/not necessary).

I didn't think about this when I first sent it, but I agree it isn't really relevant to be answered here. Even if it is a question regarding finding an alternative to using a broker (which is not mssql specific--Open Source QN). Any ideas would still be appreciated.

Thanks to those who view this,

TamusJRoyce