Griffster (7/20/2012)

---

Oh lordee! That's a nightmare! Why would they do that?!

So, the best thing to do is, in BIDS, create an environment variable package configuration to point to an...

Griffster (7/20/2012)

---

OMG! That's worked! Is it best practice then to remove the configuration file when you're happy with the package? Really strange that. We've recently upgraded to SQL 2008 from...

Jup, that should be about it.

At which component is the rejection table linked?

My guess is that the package still references config2.

This is the order in which configs are applied:

1. Apply package configurations. (--> conf2)

2. Apply configurations specified in jobstep (--> conf3)

3. Re-apply...

Are you sure the package on the server is the same version as the one used in debug mode? Check the build numbers.

Well, you do work as a DBA, so the "How to get a DBA job" seems feasable 🙂

Since you are using a Lookup, are you sure the rejected rows are inserted in the second row, or are they discarded by the Lookup component?

Not really sure why DTEXEC gives a syntax violation on /Connection.

Alternative: don't select the data sources in the SQL Agent jobstep and use package configurations instead.

Just to understand the complete picture, you have 2 configuration files?

* one specified in the package (with a direct hardcoded package configuration)

* one specified in the deployment manifest that is...

Yes. Answer Phil's and herladygeekedness' questions. What is the peculiar error you were talking about?

Explain in...

Do you have a package configuration inside the package that tells the package where to load the XML config file?

Both.

Not sure it's your cup of tea:

* Introduction to DQS

* New features of SSIS

* Optimizing DWH with columnstore index, CDC adaptors in SSIS and star-join optimization.

Did you turn on logging and see if there are configuration warnings?