SQL Server 2000 had a great little thing and tool for configuring the SQL XML support in IIS, which allowed you to create XML query templates and execute them against the database, returning XML back. This was accessed via a URL, and returned XML to the client
making the request.
I am trying to find out how to configure this same thing in SQL 2005 and I can't seem to find it anywhere. I have seen many references that seem to suggest that it is still possible to configure SQL to allow the use of the XML query templates, however, I can't
seem to find anything that tells me how to configure the stupid thing. The problem I have is that the website I have been working on uses this functionality quite a lot, and therefore I need to make sure that we can still use this functionality in the same
way until I get my client to migrate to using .NET futher.
Any help would be appreciated and beers sent in the post
As far as I know, in SQL 2005, they removed IIS support for SQL XML.
The latest version that supports IIS is; SQLXML 3 SP 3. Actually I am using and loving IIS support of SQLXML on live systems. You can still use SQL XML 3.
Anyway, I needed the same features with authentication of SQLXML and I created a similiar application with .Net 2.0 which requires Enterprise Library January 2006 edition. Currently I am testing it with XP SP2 machine and it is working out pretty well.
You need Enterprise Library January 2006 and Edition Visual Studio 2005 also IIS 5 or 6 and some Database connection. The configuration design is handled through Enterprise Libraries, Configuration Tool, the source uses many of the Application Blocks in Ent
You have executors (Database SP executor, MSMQ Executor, Assembly Executor, IronPython Executor or .NetCode Executor), the results of the executors are returned to the clients through generators (WebService, RSS, JSON, Excel or Text).
If you want further discussion, you can contact me at firstname.lastname@example.org.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.