Wow, this is proving to be **nightmarish** project. I still can't get my package to run as a job. It runs from the package store just fine. ...

Your initial comment...

Phil Parkin (1/29/2013)

---

The job is probably running under the credentials of the SQL Agent user.

This user may not have permissions to the various files involved - I suggest that you...

How is this person trying to execute the package? Have you tried right-clicking on the...

Update: I am now using Isnull for all data of type numeric and money. I'm still getting garbled output, which begins when I add to my select list a...

The fields where BCP begins to fail are numeric, with null values. I have found if I change the view to use "IsNull", that BCP works fine with it....

Update: I can add additional, non-null fields after the point where the data is garbled. This indicates that it isn't a field number limit problem.

BCP just doesn't...

Thanks, John Mitchell-245523. I use package configurations for a lot of purposes. However, in this utility package, it appears to be preferable to set the customer id in...

Thanks for the reply. I disabled all but two script tasks in the package. The top-most script task sets the value of the customer_id. The second script...

Martin, it worked like a charm. Thanks!!

If you are using SSIS, you can have a script task that dynamically adds the new columns that you need. It can determine what the current month and year...

You can establish check points in your package. This will enable you to restart the package and bypass the steps that have already been successfully done.

quasar_phoenicis, yes, I was trying to find a SSIS solution where the column definitions will change from table to table.

Too bad SSIS doesn't have a mechanism to handle this kind...

Hi Sumit,

Thanks for the reply. However, what you are doing is different than what I wish to do.

You know in advance the fields that you are selecting from the...

I've just encountered this thread:

http://www.sqlservercentral.com/Forums/Topic457155-148-1.aspx

This mirrors my question. Apparently, SSIS's need to have columns defined in advance precludes using it to dump many tables from a single...