2006-08-23
909 reads
2006-08-23
909 reads
2006-08-16
898 reads
2006-08-07
910 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
914 reads
2006-07-13
933 reads
2006-07-10
982 reads
2006-07-04
938 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,810 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,143 reads
By Brian Kelley
Here is a short emotional intelligence (EI) post for today, courtesy of Seth Godin....
By Steve Jones
I was recently trying to handle a simple task with a few AI tools...
A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...
hi , our business partner is asking s4 sap api's for receivable info and...
I have a really stupid question... Is there an easy way to search for...
Comments posted to this topic are about the item How to Work with On-Premises...
The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?
See possible answers