Does service broker use MSDTC? What is sb's underlying technology

We are using MSDTC in our stored procedures. We use BEGIN DISTRIBUTED TRAN
in our code. We are passing data from one server.database to another
server.database. These servers are on windows 2003 sp2 and using sql server
2005 sp2 plus clustering. We have run into a couple of issues where the
MSDTC acts flaky. Log files and error messages from msdtc queries is
extremely poor. The only solutions that we have found in this situation is
to failover the cluster and/or restart the sql server services. I am
pondering if we should consider editing our code. I know that the service
broker is a new feature. We are not currently using it. In passing data
around from server to server what is the underlying technology? Does it use
MSDTC. If so, I think a re-write of our code to piggy back ontop of service
broker is not going to help us. Can someone elaborate on cross server query
messages using service broker?
Thanks,
TimNo, SB does not use DTC. As far as I understand, the re-try of message sending is built-in to SB
itself, which uses TCP sockets (defined when you create your endpoint). As I understand it, the data
format (the protocol between two SB instances) isn't public, and it is in binary format (no XML or
similar). I suggest you pick up Roger Wolter's book on SB, great reading, with lots of insight...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"timw86" <timw86@.discussions.microsoft.com> wrote in message
news:7508D9D5-A4ED-4993-89B1-4CFE079F0905@.microsoft.com...
> We are using MSDTC in our stored procedures. We use BEGIN DISTRIBUTED TRAN
> in our code. We are passing data from one server.database to another
> server.database. These servers are on windows 2003 sp2 and using sql server
> 2005 sp2 plus clustering. We have run into a couple of issues where the
> MSDTC acts flaky. Log files and error messages from msdtc queries is
> extremely poor. The only solutions that we have found in this situation is
> to failover the cluster and/or restart the sql server services. I am
> pondering if we should consider editing our code. I know that the service
> broker is a new feature. We are not currently using it. In passing data
> around from server to server what is the underlying technology? Does it use
> MSDTC. If so, I think a re-write of our code to piggy back ontop of service
> broker is not going to help us. Can someone elaborate on cross server query
> messages using service broker?
> Thanks,
> Tim

Does service broker use MSDTC? What is sb's underlying technology

We are using MSDTC in our stored procedures. We use BEGIN DISTRIBUTED TRAN
in our code. We are passing data from one server.database to another
server.database. These servers are on windows 2003 sp2 and using sql server
2005 sp2 plus clustering. We have run into a couple of issues where the
MSDTC acts flaky. Log files and error messages from msdtc queries is
extremely poor. The only solutions that we have found in this situation is
to failover the cluster and/or restart the sql server services. I am
pondering if we should consider editing our code. I know that the service
broker is a new feature. We are not currently using it. In passing data
around from server to server what is the underlying technology? Does it use
MSDTC. If so, I think a re-write of our code to piggy back ontop of service
broker is not going to help us. Can someone elaborate on cross server query
messages using service broker?
Thanks,
Tim
No, SB does not use DTC. As far as I understand, the re-try of message sending is built-in to SB
itself, which uses TCP sockets (defined when you create your endpoint). As I understand it, the data
format (the protocol between two SB instances) isn't public, and it is in binary format (no XML or
similar). I suggest you pick up Roger Wolter's book on SB, great reading, with lots of insight...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"timw86" <timw86@.discussions.microsoft.com> wrote in message
news:7508D9D5-A4ED-4993-89B1-4CFE079F0905@.microsoft.com...
> We are using MSDTC in our stored procedures. We use BEGIN DISTRIBUTED TRAN
> in our code. We are passing data from one server.database to another
> server.database. These servers are on windows 2003 sp2 and using sql server
> 2005 sp2 plus clustering. We have run into a couple of issues where the
> MSDTC acts flaky. Log files and error messages from msdtc queries is
> extremely poor. The only solutions that we have found in this situation is
> to failover the cluster and/or restart the sql server services. I am
> pondering if we should consider editing our code. I know that the service
> broker is a new feature. We are not currently using it. In passing data
> around from server to server what is the underlying technology? Does it use
> MSDTC. If so, I think a re-write of our code to piggy back ontop of service
> broker is not going to help us. Can someone elaborate on cross server query
> messages using service broker?
> Thanks,
> Tim

Does service broker use MSDTC? What is sb's underlying technology

We are using MSDTC in our stored procedures. We use BEGIN DISTRIBUTED TRAN
in our code. We are passing data from one server.database to another
server.database. These servers are on windows 2003 sp2 and using sql serve
r
2005 sp2 plus clustering. We have run into a couple of issues where the
MSDTC acts flaky. Log files and error messages from msdtc queries is
extremely poor. The only solutions that we have found in this situation is
to failover the cluster and/or restart the sql server services. I am
pondering if we should consider editing our code. I know that the service
broker is a new feature. We are not currently using it. In passing data
around from server to server what is the underlying technology? Does it use
MSDTC. If so, I think a re-write of our code to piggy back ontop of service
broker is not going to help us. Can someone elaborate on cross server query
messages using service broker?
Thanks,
TimNo, SB does not use DTC. As far as I understand, the re-try of message sendi
ng is built-in to SB
itself, which uses TCP sockets (defined when you create your endpoint). As I
understand it, the data
format (the protocol between two SB instances) isn't public, and it is in bi
nary format (no XML or
similar). I suggest you pick up Roger Wolter's book on SB, great reading, wi
th lots of insight...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"timw86" <timw86@.discussions.microsoft.com> wrote in message
news:7508D9D5-A4ED-4993-89B1-4CFE079F0905@.microsoft.com...
> We are using MSDTC in our stored procedures. We use BEGIN DISTRIBUTED TRA
N
> in our code. We are passing data from one server.database to another
> server.database. These servers are on windows 2003 sp2 and using sql ser
ver
> 2005 sp2 plus clustering. We have run into a couple of issues where the
> MSDTC acts flaky. Log files and error messages from msdtc queries is
> extremely poor. The only solutions that we have found in this situation i
s
> to failover the cluster and/or restart the sql server services. I am
> pondering if we should consider editing our code. I know that the servic
e
> broker is a new feature. We are not currently using it. In passing data
> around from server to server what is the underlying technology? Does it u
se
> MSDTC. If so, I think a re-write of our code to piggy back ontop of servi
ce
> broker is not going to help us. Can someone elaborate on cross server que
ry
> messages using service broker?
> Thanks,
> Tim

does service broker come with sql express?

we're a little confused, we understand that between instances of sql express that a licensed edition would be necessary for service broker to be used but what if there is just one sql express edition/instance in the picture, does service broker come with express and can most of service broker's features be used "intra" (inside) that instance?

SQL Server Service Broker does come with Express. And you do need another (paid) edition involved for messages that pass outside the instance.

From http://msdn2.microsoft.com/en-us/library/ms345154.aspx#sseover_topic10:

SQL Server Express can use Service Broker only in combination with other SQL Server 2005 editions. If SQL Server Express receives a Broker message from another Express instance, and if another SQL Server 2005 edition has not processed the message, then the message is dropped. So the message can originate from an Express instance and end up at one, but it must be routed through a non-Express instance if that is the case. You can check a Message Drop trace event that is accessible from the Profiler or use tracing stored procedures to track this type of occurrence. The error message associated with the dropped message includes verbiage to this effect: "This message has been dropped due to licensing restrictions."

Don

|||thanks, I've read that first sentence before and totally misinterpreted its meaning.

Documentation Tools for SSB?

Does anyone know if there are automated documentation tools around that will produce docs for Service Broker objects?

Thanks,

AndrewM

There is no tool for documentation, but there is one for retrieving a more formal specification (Called service listing). It's called Service Listings Manager and Remus has contributed that to the code gallery. You might want to use that as a starting point to build a doc generator.