using a solution gives you a container for all the projects. Now in your case is sounds like you have 1 project within the solution.

I have ETL's with 15...

you should wire up the error output to the OLE Destination, I think that is what you meant, and you are not getting errors but your fields are still being...

when you create a config that will be reused you must have exactly the same items in both packages. whether they are variables, connection managers, etc.....

build the config in one...

To improve performance of a data flow it is recommended not to carry extra columns through the data flow, but I don't know how to remove these, is there a...

we have done something similar. Not sure what your goal is but ours was to have a set of configs for each environment (DEV / QA / PROD) with no...

got it working on another server.

The things I mentioned worked on this server.

I like the idea of persisting variables to a SQL table. You could use the event handlers. I can't remember the specific events but setup a routine to write the...

Use an Execute SQL Task (in the control flow) to delete the rows before you start the Data Flow Task.

Using the OLE command deletes 1 row at a time that...

use this for your ole query

SELECT C1, C2, C3 from T1 where C3 >= ?

then click the parameters button and map your [User::MyVar] to the parameter.

any time you use a...

We resolved this issue. The impersonation account needed to be an AD account and we had it setup as a SQL account.

Makes sense after thinking about it because SSAS would...

You could setup a second data source that would issue an SQL statement such as:

select 'ColumnName1' as Col1,'ColumnName2' as col2,'ColumnName3' as col3,... (no from clause is needed)

Just set it...

It is different hardware.

I agree developers should not have access to prod, but we're a very small shop and that is good in theory but doesn't work out so well....

Tim,

Thanks for the input, I have used the config files in the past and set them up for the test environment then when deploying I can update the server names...

In addition to the above issue the other is having our production SQL config data accidentally changed.

the winking emoticon is supposed to be a right parenthesis - stupid things...