2

I am running into an issue with SSDT and SQL Server Service Broker. When I run SSDT updates, it is finding one of the stored procedures that get created and dropped regularly (SqlQueryNotificationStoredProcedure-GUID).

Is there a way to ignore these stored procedures when I run my updates so that I will not get an error thrown that the stored procedure is missing (because it has already been dropped by the broker)?

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
twothreebrent
  • 221
  • 3
  • 14
  • The approach in [this answer](http://stackoverflow.com/q/17402904/#27735317) might be of help to specifically filter all drop steps of stored procedures matching this name. For inspiration from actual working code, it looks like [this](https://agilesqlclub.codeplex.com/) may be useful. – Jeroen Mostert May 05 '17 at 15:15

1 Answers1

3

I haven't seen that dependency thing before, looks pretty cool!

You can use my filter to exclude them from the deployment:

https://agilesqlclub.codeplex.com/

Probably:

/p:AdditionalDeploymentContributorArguments="SqlPackageFilter=IgnoreName(SqlQueryNotificationStoredProcedure.*)"

ed

Ed Elliott
  • 6,666
  • 17
  • 32