0

I am working on a proof-of-concept for my company using SQL Server and Service Broker External Activation to send messages from a database to a console application (both .NET and .NET Framework). I successfully created the working POC on my local machine after downloading the activator and configuring the EAService file with my application's executable. However, in production, the application and the SQL Server will be hosted on different instances. Is there anything else I can add to the EAService file, or is there another way for this POC to work? Thank you.

2
  • 1
    You can always point EAService to a dummy program which only purpose is to start your external application in whatever way you need it to be started Commented Apr 14 at 13:42
  • Adding to what @siggemannen said, the External Activator hasn't been available for download since SQL 2017 so it's future is uncertain. I suggest you implement the functionality with your own code since it's fairly trivial. Commented Apr 14 at 21:50

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.