This might help.

http://www.bidn.com/articles/integration-services/234/handling-complex-text-files-in-ssis

You are probably timing out because the rendering engine is not designed to build that many pages.

I have to agree with Lowell, this needs to be broken down...

SQLRNNR (1/3/2013)

---

opc.three (1/3/2013)

---

SQLRNNR (1/3/2013)

---

JAZZ Master (1/3/2013)

---

SGT_squeequal (1/2/2013)

---

crookj (1/2/2013)

---

Daniel Bowlin (1/2/2013)

---

In the immortal words of Uniblab

"Back to work (click), back to work (click). Everybody ( click) work, work, work, work (click),...

As Phil suggests package configurations are the way to go here.

In the immortal words of Uniblab

"Back to work (click), back to work (click). Everybody ( click) work, work, work, work (click), work, work (click)."

Revenant (12/27/2012)

---

Could you make a copy and send it my way?

We...

burr

Daniel Bowlin (12/24/2012)

---

This is pretty straight forward in SSIS

In a dataflow,

-create a source from your prod server.

-Lookup records on your dev server. In SQL Server 2005 I believe...

This is pretty straight forward in SSIS

In a dataflow,

-create a source from your prod server.

-Lookup records on your dev server. In SQL Server 2005 I believe you have...

wrapping

Klingon

Not so unorthodox, I would do pretty much the same thing.

Start by adding the generic vendor record, or specific vendor records to your table. If you can't...

I use "Don't save sensitive" and Package configurations for user names and passwords. Works like a charm.

Phew....I was thinking Falon, so I guess I can leave my aluminum foil hat in the closet....for now.

I assumed you were using start and stop dates for your report. In other words 2 sets of parameters. If you are just using one set of parameters,...