Sure, you can use it just like a table...with INSERT INTO, or even as a SELECT INTO.

Well put Steve. Love field involved in a minor (in the grand scheme) mishap, and then your reaction, how appropriate 🙂

forsqlserver (4/20/2011)

---

OPC.Three when applying your setting it is giving error below while I have login as sa:

Msg 15406, Level 16, State 1, Line 1

Cannot execute as the server principal because...

Not sure if it matters but I...

Here is what worked for me...

1. Install the latest ACE provider then restart the SQL Server service: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en

2. Then modify some setting on the provider in SQL Server:

USE [master]

GO...

You posted in a SQL 2008 forum. Not that you won't receive help, but you may have better luck posting your question in one of the SQL 2000 forums.

http://www.sqlservercentral.com/Forums/Group406.aspx

Double post. Please reply here: http://www.sqlservercentral.com/Forums/Topic1096678-391-1.aspx

I'm wondering if OPENROWSET would do the trick. Does the spreadsheet contain sensitive info? Could you attach it to this thread?

See if this article is relevant to your situation:

http://support.microsoft.com/kb/918040

That's a good question...I do not have much experience using with UNSAFE assemblies. I am wondering whether SQL Server treats them different somehow.

I just got around to trying the new Office 2010 drivers, albeit the 32-bit ones. I don't have a 64-bit sandbox available to me at the moment.

I was able to...

Craig Farrell (4/20/2011)

---

2008 can do this natively with CONVERT options.

The trick is to convert to VARBINARY in the middle with the style: 1

Here's some sample code:

DECLARE @hexStr VARCHAR(20),

@hexBin varBINARY(20)

SET @hexStr...

You can do it using OPENROWSET BULK instead of BULK INSERT and still use the same format file you already created. Here is a proof of concept that works on...

With a UDF such as the one in this article...

http://sqlblog.com/blogs/peter_debetta/archive/2007/03/09/t-sql-convert-hex-string-to-varbinary.aspx **

...you can then do stuff like this:

SELECT CAST(dbo.HexStrToVarBin('0x80074e21') AS BIGINT) ;

** Note that I am not vouching for this...

HowardW (4/19/2011)

---

No, it really is 8TB. VAS != available memory on the server.

64 bit systems can address 2^64 bytes of memory, but as this is hugely above any likely...