Topic: Service Broker versus httpEndpoints

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 5/16/2008 6:04:04 PM

By: Bill Ross

This is a multi-part message in MIME format.

------=_NextPart_000_0303_01C8B787.9BF01690
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

MS constantly impresses me with their ingenuity... but I am often =
overwhelmed. Especially when it comes to SQL Server and the myriad of =
data access choices and acronyms. The Help system is a jumble of =
choices.

For example, what is the relationship between HTTP Endpoints and Sql =
Service Broker? Or, to put it another way, would I ever NOT use Service =
Broker if I want to do Soap access to the data?

My current project would allow me to choose whatever database I would =
like as well as any access method (though it will be web based, and I =
have opted for SQL Server). I don't exactly NEED to approach this as a =
Web Service, but I love the idea of getting most of the data issues =
managed at the database level and having dumber clients consume them.

I'm assuming Crystal Reports can consume Service Broker web services?

Ok, so what I am envisioning is this:

* Sql Server, via stored procedures and Service Broker functions, etc, =
serves up the data, with the business rules enforced, to the clients via =
SOAP;
* Initially most of my clients will be asp.net/c# web pages and Crystal =
Reports that reside on the same server, but I can conveniently consume =
the same services with ad hoc consumption by Office, etc;

As I understand Service Broker, I can tap into the CLR by "Using System" =
and "Using System.Web" etc?

Thanks,

--=20
Bill Ross
http://billrosspolitics.blogspot.com
http://bibleshockers.blogspot.com
------=_NextPart_000_0303_01C8B787.9BF01690
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3Diso-8859-1>
<META content=3D"MSHTML 6.00.6001.18023" name=3DGENERATOR></HEAD>
<BODY id=3DMailContainerBody=20
style=3D"PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-TOP: 15px"=20
bgColor=3D#ffffff leftMargin=3D0 topMargin=3D0 CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>MS constantly impresses =
me with=20
their ingenuity... but I am often overwhelmed. Especially when it comes =
to SQL=20
Server and the myriad of data access choices and acronyms. The Help =
system is a=20
jumble of choices.</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>For example, what is the =

relationship between HTTP Endpoints and Sql Service Broker? Or, to put =
it=20
another way, would I ever NOT use Service Broker if I want to do Soap =
access to=20
the data?</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>My current project would =
allow me to=20
choose whatever database I would like as well as any access method =
(though it=20
will be web based, and I have opted for SQL Server). I don't =
exactly NEED=20
to approach this as a Web Service, but I love the idea of =
getting most of=20
the data issues managed at the database level and having dumber clients =
consume=20
them.</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>I'm assuming Crystal =
Reports can=20
consume Service Broker web services?</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>Ok, so what I am =
envisioning is=20
this:</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>* Sql Server, via stored =
procedures=20
and Service Broker functions, etc, serves up the data, with the business =
rules=20
enforced, to the clients via SOAP;</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>* Initially most of my =
clients will=20
be asp.net/c# web pages and Crystal Reports that reside on the =
same=20
server, but I can conveniently consume the same services with ad hoc =
consumption=20
by Office, etc;</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>As I understand Service =
Broker, I=20
can tap into the CLR by "Using System" and "Using System.Web" =
etc?</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>Thanks,</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4><BR>-- <BR>Bill =
Ross<BR><A=20
href=3D"http://billrosspolitics.blogspot.com">http://billrosspolitics.blo=
gspot.com</A><BR><A=20
href=3D"http://bibleshockers.blogspot.com">http://bibleshockers.blogspot.=
com</A></FONT></DIV></BODY></HTML>

------=_NextPart_000_0303_01C8B787.9BF01690--

Replies below ↓

Replies

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 5/16/2008 6:04:04 PM

By: Bill Ross

Service Broker versus httpEndpoints

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 5/16/2008 6:30:03 PM

By: Bill Ross

Re: Service Broker versus httpEndpoints

This is a multi-part message in MIME format.

------=_NextPart_000_032F_01C8B78B.3D3B1B00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

In fact, let me make this question even more explicit...

At this site:

http://www.developer.com/db/article.php/3547866

The author says this:

"...The FOR SOAP clause states that this endpoint will respond to SOAP =
messages. Other endpoints handle messages for Service Broker or database =
mirroring..."

Ok, so Service Broker is NOT necessary to access SQL Server via HTTP =
Endpoints? So would I ever do that in 2008?

"Service Broker versus HTTP Endpoints" has not brought up any hits that =
clear all this up for me.

Thanks,

Bill Ross
http://billrosspolitics.blogspot.com
------=_NextPart_000_032F_01C8B78B.3D3B1B00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3Diso-8859-1>
<META content=3D"MSHTML 6.00.6001.18023" name=3DGENERATOR></HEAD>
<BODY id=3DMailContainerBody=20
style=3D"PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-TOP: 15px"=20
bgColor=3D#ffffff leftMargin=3D0 topMargin=3D0 CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>In fact, let me make =
this question=20
even more explicit...</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>At this =
site:</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4><A=20
href=3D"http://www.developer.com/db/article.php/3547866">http://www.devel=
oper.com/db/article.php/3547866</A></FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>The author says =
this:</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV>"...The <CODE>FOR SOAP</CODE> clause states that this endpoint will =
respond=20
to SOAP messages. Other endpoints handle messages for Service Broker or =
database=20
mirroring..."</DIV>
<DIV> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>Ok, so Service Broker is =
NOT=20
necessary to access SQL Server via HTTP Endpoints? So would I ever do =
that in=20
2008?</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>"Service Broker versus =
HTTP=20
Endpoints" has not brought up any hits that clear all this up for=20
me.</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>Thanks,</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4></FONT> </DIV>
<DIV><FONT face=3D"Garamond Premr Pro" size=3D4>Bill Ross</FONT></DIV>
<DIV><FONT face=3D"Garamond Premr Pro"=20
size=3D4>http://billrosspolitics.blogspot.com</FONT></DIV></BODY></HTML>

------=_NextPart_000_032F_01C8B78B.3D3B1B00--

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 5/16/2008 6:30:03 PM

By: Bill Ross

Re: Service Broker versus httpEndpoints

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 5/17/2008 1:51:07 AM

By: Tibor Karaszi

Re: Service Broker versus httpEndpoints

IMO, SB and HTTP Endpoint are totally different things.

HTTP Endpoint allow you to expose a stored procedure or function as a web service method. It is as
simple as that. All needed is a CREATE ENDPOINT command (and security in place) and you are done.

Service broker allow you to post and read messages from queues. It include functionality to
guarantee delivery, read in order etc. And SB also allow you to communicate messages between two
databases and even instances. In the later case, you need to define SB endpoints so that SQL Server
on one instance has some way to reach into the other instance to deliver the message.

HTTP Endpoints are deprecated in 2008, so you don't want to go that route...

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

"Bill Ross" <billross@bibleshockers.com> wrote in message
news:369E1296-AAD3-4E9C-978B-CC1897342527@microsoft.com...
MS constantly impresses me with their ingenuity... but I am often overwhelmed. Especially when it
comes to SQL Server and the myriad of data access choices and acronyms. The Help system is a jumble
of choices.

For example, what is the relationship between HTTP Endpoints and Sql Service Broker? Or, to put it
another way, would I ever NOT use Service Broker if I want to do Soap access to the data?

My current project would allow me to choose whatever database I would like as well as any access
method (though it will be web based, and I have opted for SQL Server). I don't exactly NEED to
approach this as a Web Service, but I love the idea of getting most of the data issues managed at
the database level and having dumber clients consume them.

I'm assuming Crystal Reports can consume Service Broker web services?

Ok, so what I am envisioning is this:

* Sql Server, via stored procedures and Service Broker functions, etc, serves up the data, with the
business rules enforced, to the clients via SOAP;
* Initially most of my clients will be asp.net/c# web pages and Crystal Reports that reside on the
same server, but I can conveniently consume the same services with ad hoc consumption by Office,
etc;

As I understand Service Broker, I can tap into the CLR by "Using System" and "Using System.Web" etc?

Thanks,

--
Bill Ross
http://billrosspolitics.blogspot.com
http://bibleshockers.blogspot.com

Page 1 of 2 Pages