Re: 2000 = SQLXML 2005 = ??? (what is SQLXML replaced with in 2005)
- From: "Mike C#" <xyz@xxxxxxx>
- Date: Mon, 11 Aug 2008 16:55:05 -0400
You can use SQL 2005 HTTP Endpoints (although they are deprecated effective
with 2008). Project Astoria (ADO.NET Data Services) looks like a potential
replacement for both HTTP Endpoints and SQLXML, although last time I checked
it was still in Beta. Alternatively you can use ASP.NET and create either a
web service or a web page that returns your XML directly over HTTP (as is
common with AJAX-style applications). I think the general idea is that MS
tried implementing HTTP Endpoints directly from SQL Server but then decided
against it. Now the move is toward keeping the HTTP communication in the
middle-tier, away from SQL Server itself.
"clickfindT" <taco.fleur@xxxxxxxxxxxxxxxx> wrote in message
news:5e31f8ab-8f83-41f1-8092-ca4e0ee2fb10@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Does anyone know what to use now instead of SQLXML to simply output
XML over HTTP?
I don't need any WSDL at this stage although it would be nice, just
after outputting XML directly from the server over HTTP.
Any suggestions and or tutorials would be much appreciated.
Cheers
.
- References:
- 2000 = SQLXML 2005 = ??? (what is SQLXML replaced with in 2005)
- From: clickfind™
- 2000 = SQLXML 2005 = ??? (what is SQLXML replaced with in 2005)
- Prev by Date: Re: Wanted: Simple query->DOM example
- Next by Date: fieldname and field value in a table
- Previous by thread: 2000 = SQLXML 2005 = ??? (what is SQLXML replaced with in 2005)
- Next by thread: Shaping this query
- Index(es):
Relevant Pages
|
