Wanderer,

The reason you get more info with the command-line is that SSIS job step is just...well...crap! Under the covers it uses dtexec.exe anyway in exactly the same way - it just...

Yep. Don't use the "Execute SSIS Package" job step. Use the command-line job step and use dtexec.exe to fire the package. You get much more information in your job output...

Why crazy? 

These will be your best bets:

http://www.amazon.com/gp/product/0764584359/sr=8-1/qid=1150273317/ref=pd_bbs_1/102-1412231-0916156?%5Fencoding=UTF8

http://www.amazon.com/gp/product/0672327813/sr=8-2/qid=1150273356/ref=pd_bbs_2/102-1412231-0916156?%5Fencoding=UTF8

-Jamie

Correct, Fast parse works only under certain circumstances.

-Jamie

If a "number" (I use the word through clenched teeth) has periods or commas in it then it isn't an integer. An integer is a combination of the digits {1,2,3,4,5,6,7,8,9,0}. Nothing else.

Try importing...

Note that you can still use FastParse on files that have textual data in them - they don't have to have only integer/datetime values. This is because fastParse is a...

This is a really useful article: http://support.microsoft.com/kb/918760/en-us

-Jamie

Another question....what's the error?

-Jamie

I find it a little annoying that it isn't consistent with Excel - ALT-Enter!

-Jamie

The Excel Provider supplies fields as unicode. SSIS has no control over this. As David says, use a data conversion component to correct the problem.

-Jamie

This should just "work". It sounds as though the defaults aren't getting fired which is probably a problem in SQL. Mind you, you can supply table hints on the OLE...

Terry,

That's why I like the expression approach. It means those issues won't appear!

-Jamie

Teegee,

Fear not. This is very easy in SSIS once you know how. All explained here: http://blogs.conchango.com/jamiethomson/archive/2005/12/09/2480.aspx

-Jamie

Try the multifile connection manager. It lets you point at multiple files at once (e.g. "*.*")

-Jamie