MSXML vs SQLXML

Hi All,
I have Downloaded both MSXML 4.0 SP2 and SQLXML.
Are they are same. If not can any one please tell me what for that both are
used?
Thanks
PrabhatHi
MSXML 4.0 SDK is a development environment to create XML applications
http://msdn.microsoft.com/library/d...xmloverview.asp
SQLXML enables XML support for SQL Server 2000
http://msdn.microsoft.com/library/d...>
h_SQLXML.asp
SQLXML will use MSXML and you will need both to use SQLXML, for instance
SqlXml 3.0 SP2 has a dependency on MSXML version 4.0 SP2, so MSXML version
4.0 SP2 is included in it's download.
HTH
John
"Prabhat Nath" wrote:

> Hi All,
> I have Downloaded both MSXML 4.0 SP2 and SQLXML.
> Are they are same. If not can any one please tell me what for that both ar
e
> used?
> Thanks
> Prabhat
>
>|||Hi John, Thanks for your Information.
Prabhat
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:B40F325B-6C3A-4FE4-8FCE-4B65463CE8BE@.microsoft.com...
> Hi
> MSXML 4.0 SDK is a development environment to create XML applications
>
http://msdn.microsoft.com/library/d...-us/xmlsdk/html
/xmmscxmloverview.asp
> SQLXML enables XML support for SQL Server 2000
>
http://msdn.microsoft.com/library/d...-us/dnanchor/ht
ml/anch_SQLXML.asp
> SQLXML will use MSXML and you will need both to use SQLXML, for instance
> SqlXml 3.0 SP2 has a dependency on MSXML version 4.0 SP2, so MSXML version
> 4.0 SP2 is included in it's download.
> HTH
> John
>
> "Prabhat Nath" wrote:
>
are

MSXML parser & SQL Server Memory

The below snippet from SQL Server BOL under the topic "sp_xml_preparedocument" implies that the use of XML can be extremely memory intensive. Is is really the case that MSXML uses 1/8 total SQL Server memory? I find this astounding if true.
"Note A parsed document is stored in the internal cache of SQL Server 2000. The MSXML parser uses one-eighth the total memory available for SQL Server. To avoid running out of memory, run sp_xml_removedocument to free up the memory."
It means that it can use up to 1/8th of the memory. Unless you try to parse
a very large document or never release the allocated memory, you should
never use or reach this limit.
HTH
Michael
"glr" <glr@.discussions.microsoft.com> wrote in message
news:DE9CFF6C-B949-4318-9294-6B4EFB773AF2@.microsoft.com...
> The below snippet from SQL Server BOL under the topic
> "sp_xml_preparedocument" implies that the use of XML can be extremely
> memory intensive. Is is really the case that MSXML uses 1/8 total SQL
> Server memory? I find this astounding if true.
> "Note A parsed document is stored in the internal cache of SQL Server
> 2000. The MSXML parser uses one-eighth the total memory available for SQL
> Server. To avoid running out of memory, run sp_xml_removedocument to free
> up the memory."
>

MSXML in Win Server 2003

Hi,

I have been using 'MSXML2.ServerXMLHttp.4.0' to make web requests from SQL server with no problems for about 6 months now (on Win2K Servers).

Now trying to move the databases onto a new 2003 server and getting the well known 'Access denied' error message. I beleive I have sorted out the following:

- Execute permissions on the master database for sp_OACreate, sp_OAGetErrorInfo,....
- Allowed 'All unkown ISAPI Extensions' - not that I'm happy about that!!
- Uninstalled the 'Internet Explorer Enhanced Security Configuration'
- I have enabled 'Submit nonencrypted form data' for the relevant zones in IE Security Settings

But none of these seem to have had an effect. I have also tried using WinHTTP.WinHTTPRequest.5.1 as suggested in a MS KB article, but this is not suitable as I need to pass authenitication parameters with each request, and it seems as though the response size is limited.

If anyone has any tips/checklists for getting this going I would be very interested.

TIASolved it!

My inablility to read MS Info, for others here is a very stripped down version:

exec @.hr = sp_OACreate 'WinHTTP.WinHTTPRequest.5.1', @.obj OUT

IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END

exec @.hr = sp_OAMethod @.obj, 'open', NULL, "GET", @.sUr

IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END

exec @.hr = sp_OAMethod @.obj, 'SetCredentials', NULL, 'USERNAME', 'PASSWORD', '0'

exec @.hr = sp_OAMethod @.obj, 'send'
IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END

exec @.hr = sp_OAMethod @.obj, 'status', @.status OUT
IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END

IF @.status <> 200
BEGIN
SET @.desc = 'HTTP request failed. Server returned status of ' +cast(@.status as varchar) + '.'
goto eh
END

exec @.hr = sp_OAGetProperty @.obj, 'responseText', @.response OUT
IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END

exec @.hr = sp_OADestroy @.obj
return 0

eh:
exec @.hr = sp_OADestroy @.obj
Raiserror(@.desc, 16, 1)sql