SQL Server: Building Multi-instance Asynchronous Applications

Course Overview
Hello! My name is Jonathan Kehayias, and welcome to my course, SQL Server: Building Multi-instance Asynchronous Applications. I'm a consultant and trainer with SQL skills, as well as a Microsoft data platform MVP. The Service Broker feature is one of the best-kept secrets in SQL Server. And I find that many companies don't leverage Service Broker because of the lack of information available and the lack of UI support for the feature. This course builds on the SQL Server: Building Simple Asynchronous Application course and expands the configuration from a single database to multiple databases, as well as to multiple instances of SQL Server. In the first few modules, you'll learn about the additional objects involved with Service Broker applications that involve multiple databases in the same instance of SQL Server, as well as how to send Service Broker messages to another instance of SQL Server. Along the way, we'll discuss and demonstrate security best practices so you understand the different security considerations and any risks associated with them. You'll then learn how to support and maintain a Service Broker implementation and, finally, how to troubleshoot any problems that occur. By the end of this course, you'll understand how to build asynchronous solutions on top of Service Broker using multiple databases and multiple instances of SQL Server, the considerations for transport and dialog security, and what to do when something isn't working the way you expect it to. You only need a basic understanding of SQL Server and development to be able to follow the information in this course. I hope you will join me to go deeper with Service Broker in this course, SQL Server: Building Multi-instance Asynchronous Applications here on Pluralsight.

Intra-instance Service Broker Configurations
Hi! This is Jonathan Kehayias with sqlskills. com, and I'm recording this SQL Server: Building Multi-instance Asynchronous Applications course for Pluralsight. In this module, we're going to take a look at the configuration of Service Broker components within a single instance of SQL Server where messages need to be sent between services that exist within different databases. In this module, we're going to talk about what's different when you have multiple database configurations for Service Broker within SQL Server. We're also going to cover the different security configurations that exist and the considerations that need to be reviewed as a part of the design of a multi-database deployment for Service Broker. When multiple databases are a part of a Service Broker application, even within the same instance of SQL Server, there are differences from the single database design that was demonstrated in the SQL Server: Building Simple Asynchronous Applications course. One of the biggest differences is around the security requirements for crossing the database boundary between services, and there are multiple methods of allowing cross-database access for Service Broker applications that we'll discuss in this module. Another difference with multiple databases is that the common components for message types and contracts need to be deployed into each of the databases that will participate within the Service Broker application. And, finally, troubleshooting issues with multiple databases in the same instance require reviewing the sys. transmission_queue of each of the databases used by the application whenever there are problems within the Service Broker implementation.

Maintaining Service Broker Configurations
Hi. This is Jonathan Kehayias with sqlskills. com, and I'm recording this SQL Server: Building Multi-Instance Asynchronous Applications course for Pluralsight. In this module we're going to take a look at maintaining Service Broker applications once they've been deployed. In this module we're going to take a look at how you start and stop Service Broker applications to allow configuration changes to the application to be made in a safe manner. Then we're going to look at how to modify existing Service Broker components to accommodate any changes that might happen to your business application requirements where you may need to introduce new message types that may need to be implemented, and that will require changes to the contracts that are already being used by services within Service Broker. Then we're going to talk about considerations when restoring a Service Broker enabled database, and the options that are available to prevent any problems from happening with what are known as misdirected messages, and finally, we'll wrap up with handling expired or expiring certificates for endpoint or dialog security, and how to rotate the certificates into an existing configuration for dialog and transport security certificate use.