Is SQLXML Bulkload 64-bit compatible?

I'd like to use SQLXML Bulkload on a 64-bit Win2K3 and SQL Enterprise
64-bit setup. Has anyone tried this yet? I'm assuming it won't work.
Here's some background...
The production servers were upgraded to 64-bit a year ago and are
working great. End user analysts approve and submit their updates via
an Excel file. The old 32-bit process used OPENROWSET's Jet provider
to read the Excel file into a SQL table. I think we could get the end
users to save-as XML from Excel, but the resulting file is much larger
than 8000 characters and needs to be loaded into 64-bit SQL.
Our current workaround is to use an old 32-bit server to read the xls
file into SQL, then BCP it out, then transfer the text file to the
64-bit server, then BCP it in to SQL 64-bit. It's a manual process
that we could automate, but it would still involve a 32-bit server
which is not part of our production farm.
Rather than add a 32-bit server to simply import from a Excel or XML
file, we'd like to find a full 64-bit solution.
Thanks,
Ray MetzYou could try and use 32-bit SQLXML Bulkload in a 64 bit machine through the
WOW option.
SQLXML 4.0 that will be shipping with Yukon is supported on 64bit.
Chandra
---
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"RayMetz100" <RayMetz100@.yahoo.com> wrote in message
news:1118427405.028187.37410@.g47g2000cwa.googlegroups.com...
> I'd like to use SQLXML Bulkload on a 64-bit Win2K3 and SQL Enterprise
> 64-bit setup. Has anyone tried this yet? I'm assuming it won't work.
> Here's some background...
> The production servers were upgraded to 64-bit a year ago and are
> working great. End user analysts approve and submit their updates via
> an Excel file. The old 32-bit process used OPENROWSET's Jet provider
> to read the Excel file into a SQL table. I think we could get the end
> users to save-as XML from Excel, but the resulting file is much larger
> than 8000 characters and needs to be loaded into 64-bit SQL.
> Our current workaround is to use an old 32-bit server to read the xls
> file into SQL, then BCP it out, then transfer the text file to the
> 64-bit server, then BCP it in to SQL 64-bit. It's a manual process
> that we could automate, but it would still involve a 32-bit server
> which is not part of our production farm.
> Rather than add a 32-bit server to simply import from a Excel or XML
> file, we'd like to find a full 64-bit solution.
>
> Thanks,
> Ray Metz
>