Viewing 15 posts - 16 through 30 (of 521 total)
I am sure what caused the error, maybe duplicated columns (headers) in the spreadsheet. Can you run the SP in debug mode and check the output?
February 19, 2010 at 6:45 am
If the file is too big, the OPENROWSET to bulkload the file may get time out so the xml is empty.
As for Excel not open the xml spreadsheet, can you...
February 19, 2010 at 6:08 am
I never tried this scenario.
One workaround is you donot precrete the table. Instead, you can pass the table name and identity column name to the SP and let the...
February 18, 2010 at 1:40 pm
The following is the answer to your questions:
1. Why create the GetColumnDataTypeName udf? Why do we need the data type name?
The stored procedure supports to import data to a...
February 18, 2010 at 6:50 am
The background of this article is that my customers use Excel spreadsheets to edit data since SQL 2000 and we have tools to load data from Excel to database....
February 18, 2010 at 6:27 am
You can post it here.
February 17, 2010 at 1:55 pm
Thanks for your kind words.
As the error message said, it is the security setting issue. The account you used (the Windows account if you used trust authentication or the...
February 17, 2010 at 1:53 pm
To import dbfile to SQL Server, a better way is to use SSIS. 64 bit sql server has both 32 bit and 64 bit SSIS command line. You can...
February 17, 2010 at 10:01 am
Did you save your spreadsheet as xml in Excel?
February 17, 2010 at 9:57 am
First, in Your scenario, the file needs to be in the C:\ drive of the SQL Server box;
Second, check the file security:
If you log on SQL Server by a SQL...
February 17, 2010 at 9:56 am
The link in the article does not work anymore. Please use the links in the "Resources" in the end of the article.
February 17, 2010 at 6:26 am
User defined data type is called alias type in sql 2005, and is based on a native sql data type, e.g. Name as varchar(100);
User defined type (UDT) means the data...
January 21, 2010 at 2:14 pm
Thanks everyone for your comments.
To david.hultin 15509:
Yes, it was a copy/paste problem. It was reported by, interestingly, another David (David Quéméré
) when it was...
January 15, 2010 at 9:30 am
By 64 bit windows 2003/sql 2005, the solution is installed 32 bit ole db provider for jet(should already be installed by windows or SQL server), use a 32bit executible to...
January 13, 2010 at 7:19 am
I am not sure windows 2008 R2, I know there is no 64 bit Jet ole db provider for 64 bit windows 2003/sql server 2005.
January 13, 2010 at 6:48 am