2006-08-23
906 reads
2006-08-23
906 reads
2006-08-16
896 reads
2006-08-07
906 reads
After agreeing on our design goals we began looking for technologies to support them. It turned out that SQL Server™ Service Broker offered the asynchronous messaging support we needed and, since the message-queuing infrastructure is tightly integrated with the SQL Server database engine, our existing database backup, administration, and failover procedures could cover our messaging solution as well.
2006-07-26
1,736 reads
2006-07-17
909 reads
2006-07-13
931 reads
2006-07-10
981 reads
2006-07-04
936 reads
One way to understand Service Broker is to think of it as a postal service. New author Sachin Dedhia brings us a fantastic introduction to the Service Broker including the code to setup and begin working with queues, conversations and contracts. If that doesn't make sense, you need to read this article.
2006-05-08
9,806 reads
One of the less exciting, but perhaps very powerful new features in SQL Server 2005, the Service Broker is an asynchronous communications method. MVP Srinivas Sampath brings us the second part of his series looking at what you can accomplish with a practical example.
2005-08-30
13,136 reads
By Steve Jones
I don’t have SQL Server installed on my laptop. In an effort to keep...
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
Hi all Can I get some perspective from the community please on performing in-place...
Comments posted to this topic are about the item How Long is a Long...
Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers