SQL Server 2005 comes with lot of additional functionality, one of the notable ones is "Service Broker". Service broker enables a new class of asynchronous, distributed database application by offering unprecedented level of reliability, performance, and fault tolerance to messaging applications. The core of the Service Broker architecture is the dialog. A dialog is a reliable, bidirectional, persistent, ordered exchange of messages between two endpoints. An endpoint is a SQL Server 2005 database configured for Service Broker messaging. Because the dialogue is persistent, it can ensure the messages are processed in the order they were sent, even if the dialog lasts for weeks or months. The dialog messages are stored in database queues to provide asynchronous delivery. Because the queues are part of the database, Service Broker messages enjoy all the reliability and fault tolerance that SQL Server supplies for all databasee data. Service Broker also includes an efficient TCP/IP based protocol for reliably and securely transfering messages between SQL Server instances.

Microsoft SQL Server 2005 is lacking with an administration tool to support the Service Broker functionality, which makes developers and administrators to depend on SQL scripts to perform any kind of operation. This results in lack of productivity to some extend and makes life harder for developers and administrators to do routine tasks. Also, the loosely coupled Service broker objects like Message Types, Contracts, Queues, Services etc has some kind of relationship between each other in a Service Broker Application, the current version of Microsoft SQL Server 2005 doesn’t provide any view on object relationships.

In order to address the above issues and to make life easier for Service Broker application developers and administrators this GUI tool SQL Service Broker Management Studio 2005 is designed and build.