I have setup notifications, and have them working. The problem: I would like to reset the query watch without destroying and re-creating the queue\service pair. Currently I have to delete these and create a new one for every notification I want to receive. And setting up a notification (with different parameters) on the same queue doesn't work and it doesn't give me an error on the command. My main thread changes it's view, and sets the sql change up on the new thread. When the notificationmanager thread command timeout, it checks to see if it needs to reset the watch. If it does, currently it has to destroy and recreate the queue\service pair because: If I just set the notification command up with different parms, it doesn't trigger when that data changes on the server. So I would really like to cancel the current notification (sqlnotificationrequest) and reset the command so that I am not having to destroy and recreate the queue every time the user changes what he is looking at. Does this make sense?

You'll probably have more luck getting a response in another newsgroup or forum. This one is dedicated to Notification Services which despite the similar sounding name is not the same as Query Notifications.

I thought Query Notification uses notification services to facilitate the conversation or contract. It uses a sql server Queue and a service on that queue, which IS the same. the notification in the command object is used to submit a request. ???

Hi, Did you have any joy with finding a solution to your query with cancelling a SqlNotificationRequest? I have a similar situation where I want the user to be able to change their view and refresh the DataGridView data but it looks like I need to cancel the original request before creating the new one.