Service Broker is one of the more interesting and useful new enhancements in SQL Server 2005, however many DBAs are not familiar with this subsystem. New author Santhi Indukuri brings us a practical example of how you can build a distributed application using Service Broker.
2007-01-25
19,036 reads
2007-01-17
973 reads
2007-01-12
833 reads
2007-01-04
833 reads
Utilizing design patterns with SQL Server 2005 Service Broker enables you to assess and select appropriate solutions for all of your SQL Server 2005 asynchronous messaging needs.
2006-12-27
2,224 reads
You can leverage SQL Server 2005 Service Broker with existing technologies such as SQL Server 2000 and MSMQ. BizTalk and SSB external activation are viable options, but a simple polling solution is easier.
2006-12-20
2,465 reads
SQL Server Management Studio just doesn't cut it for complicated configuration and monitoring implementations. Learn how to implement your own SQL Service Broker (SSB) control bus solution to serve the needs of complex SQL Server-based messaging solutions.
2006-12-06
3,926 reads
2006-11-29
831 reads
Service Broker is a new feature in SQL Server 2005 that brings queuing and reliable messaging to SQL Server. Service Broker provides the “plumbing” to let you pass messages between applications, using SQL Server as the transport mechanism. Applications can use a single shared SQL Server database for this purpose or distribute their work across multiple databases.
2006-11-29
2,774 reads
2006-11-21
857 reads
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
By Arun Sirpal
“What exactly did it do on my server?” is the first question a DBA...
By James Serra
Microsoft shared a broad set of Fabric, Power BI, and SQL updates at FabCon...
Comments posted to this topic are about the item Let's Talk Certifications
Comments posted to this topic are about the item The Hidden Security Risks of...
Comments posted to this topic are about the item The Empty Aggregate
I have this table in a SQL Server 2025 database:
CREATE TABLE [dbo].[CustomerOrder] ( [OrderID] [int] NULL, [CustomerID] [int] NULL, [total] [money] NULL ) ON [PRIMARY] GOWhat is returned from this code? (answers are for the sum and then the count)
SELECT SUM(total) AS sum,
COUNT(total) AS count
FROM dbo.CustomerOrder;
See possible answers