Problem with scripting of event notification
peter eh
Posts: 17 Bronze 2
We created the following Service Broker code in one of our systems:
CREATE EVENT NOTIFICATION [PoisonMessageNotification]
ON QUEUE [dbo].[QueuePoisonMessageNotification]
FOR BROKER_QUEUE_DISABLED
TO SERVICE '//Firm/Project/PoisonMessageNotifyService', 'current database'
SQL Compare scripts this as:
CREATE EVENT NOTIFICATION [PoisonMessageNotification]
ON QUEUE [dbo].[QueuePoisonMessageNotification]
FOR BROKER_QUEUE_DISABLED
TO SERVICE '//Firm/Project/PoisonMessageNotifyService', 'C3761938-AA47-462B-BF02-6EBEE03FC4B6'
The problem is, that 'current database' is now transfered into the ServiceBrokerGuid of the database (in this example: 'C3761938-AA47-462B-BF02-6EBEE03FC4B6'). But this ServiceBrokerGuid is different on every database and every system. Every time I compare development with test, production or source control I get a difference, that needs special attention and can't be solved.
CREATE EVENT NOTIFICATION [PoisonMessageNotification]
ON QUEUE [dbo].[QueuePoisonMessageNotification]
FOR BROKER_QUEUE_DISABLED
TO SERVICE '//Firm/Project/PoisonMessageNotifyService', 'current database'
SQL Compare scripts this as:
CREATE EVENT NOTIFICATION [PoisonMessageNotification]
ON QUEUE [dbo].[QueuePoisonMessageNotification]
FOR BROKER_QUEUE_DISABLED
TO SERVICE '//Firm/Project/PoisonMessageNotifyService', 'C3761938-AA47-462B-BF02-6EBEE03FC4B6'
The problem is, that 'current database' is now transfered into the ServiceBrokerGuid of the database (in this example: 'C3761938-AA47-462B-BF02-6EBEE03FC4B6'). But this ServiceBrokerGuid is different on every database and every system. Every time I compare development with test, production or source control I get a difference, that needs special attention and can't be solved.
