|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Friday, February 22, 2013 9:30 PM
Points: 912,
Visits: 198
|
|
Comments posted to this topic are about the item SSIS and Excel 2007
My Blog: http://dineshasanka.spaces.live.com/
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Thursday, March 14, 2013 8:33 AM
Points: 50,
Visits: 126
|
|
We have IA-64 servers........other than using a CSV converted version......will Microsoft ever release excel (Jet) drivers so we can use the excel Tasks?
Do you have any methods for bringing in Excel files as is on an IA64 platform?
|
|
|
|
|
SSCarpal Tunnel
       
Group: General Forum Members
Last Login: 2 days ago @ 2:50 AM
Points: 4,785,
Visits: 1,334
|
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, September 12, 2012 5:17 AM
Points: 329,
Visits: 461
|
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Thursday, March 14, 2013 8:33 AM
Points: 50,
Visits: 126
|
|
Unfortunately "Microsoft.Jet.OLEDB.4.0" does not exist for IA-64..........unless you have heard otherwise.....
If you have we would be very pleased indeed!! if so please provide MS link to the IA-64 OLEDB jet driver.
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Yesterday @ 10:29 AM
Points: 889,
Visits: 931
|
|
From what I've seen, importing data from excel can be very hazardous so I avoid it whenever possible. The import process will interpret your data type by sampling the data irregardless of how you define the data type in SSIS or on your destination table. So if the first part of your file contains numbers and the last contains characters... the import process will simply throw out the data with characters and load NULL's without any warnings or errors. I know there is a reg key you can set to determine the number of records that are sampled, but the fact that the Excel driver does this is bad enough for me. 
David
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 4:05 AM
Points: 193,
Visits: 1,248
|
|
"From what I've seen, importing data from excel can be very hazardous etc" I agree on that.
But I have no experience with Excel2007 yet. Does it work as 2003 in this sence ? Dinesh what do you say?
For me I will still save the sheets as TAB sep textfiles and import them so.
//Gosta
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 4:05 AM
Points: 193,
Visits: 1,248
|
|
"Unfortunately "Microsoft.Jet.OLEDB.4.0" does not exist for IA-64..........unless you have heard otherwise"
If you keep to textfiles you don't need the Jet driver if you use bulk insert instead.//
//Gosta
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, October 30, 2008 6:13 PM
Points: 2,
Visits: 8
|
|
Awesome. Thank you. I could have used this last week... but I got through it.
I had to do a comparison of an excel 2007 file to an sql table and follow that with a report on the findings in SSRS.
I found that I had to export to an earlier version of excel for the reporting services piece. I couldn't find how to use a driver for excel 97 in reporting services. Did I miss something there?
Thank you
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, January 23, 2013 11:08 AM
Points: 223,
Visits: 82
|
|
David (10/24/2008) From what I've seen, importing data from excel can be very hazardous so I avoid it whenever possible. The import process will interpret your data type by sampling the data irregardless of how you define the data type in SSIS or on your destination table. So if the first part of your file contains numbers and the last contains characters...
I have found this to be true as well. I haven't started experimenting with SSIS in 2008 yet, but hopefully there's a setting that addresses this. From what I remember, SSIS only looks at the first 200 rows to try to analyze the data type. It would obviously be better if it tried to find every possible data type in a column and then chose the lowest common denominator.
However, I'd make the argument that one should be familiar with the data that's being imported, and should therefore be able to anticipate any data types for each column, and handle any deviation with row redirects to text files so that the package execution doesn't come to a dead stop because of a few bad apples in a source.
Cheers,
-m
|
|
|
|