LOLĭon't get me wrong.I'm all for powerful tools. But I must say that if that is the case.then where is the money being spent in Redmond? They are starting to look more and more like Government efficiency. Well I suppose if I must go back to basics and create format files for 15 CSV files with up to 70 columns each, then so be it. Please somebody tell me that I won't have to create format files to explain to the mighty SQL Server that ',' is the end of the 1st column and ',' the end of the 2nd and maybe ', is the end of the 3rd if the following column contains a number. It drives me crazy that Excel and Access by default handles this quite well while SSIS chokes. Also it should be obvious that '' within a text string is an escaped double-quotation mark pair. But the wise and powerful SSIS decides to create a column break there. It is clear to Excel and Access, simple minded desktop applications, that the comma between 'Courier New, Courier' is part of a text string. 'This is the first column','2nd column','3rd column',143. There are cases where a comma is included within a text or character column (not to be confused with the TEXT datatype). I have specified that columns are comma (,) delimited and the text is delimited with double-quote ('). Here is an example of where the import fails. I had a similar project a couple years ago when I ended up using Bulk Insert with Format files that I created. I have tried using just the defaults and then setting ' as a text delimiter, but the import fails. I need to automate this for nightly updates. But for some reason a simple import into SQL Server table using SSIS Import/Export Wizard and flat-file source doesn't place the data in the correct columns. These files open cleanly in Excel 2007 and import cleanly into Access 2007. I have received some CSV files that I need to simply import into SQL 2005 tables.

Having problems wiht using sql on mac