In that case I recommend you begin by going through the Stairway to Integration Services series[/url] on this site.

Also SQLShare has some SSIS videos you may find helpful to get...

Have you created an SSIS package in BIDS?

You need to right-click on the OLE DB Source in SSIS (BIDS) NOT the folder on the OS.

Usually you use the folder the DBF resides in as the source.

Stefan Krzywicki (5/21/2012)

---

Grant Fritchey (5/21/2012)

---

How did it go? I had a great, if...

Steve Jones - SSC Editor (5/14/2012)

---

Whaaa? No backups of your laptop? None of...

RBarryYoung (5/14/2012)

---

Jack Corbett (5/14/2012)

---

RBarryYoung (5/10/2012)

---

Koen Verbeeck (5/10/2012)

---

Stefan Krzywicki (5/10/2012)

---

Yeah, I created the import package manually. I ended up getting the table structures by using an openquery in a...

dwain.c (5/13/2012)

---

Sean Lange (5/11/2012)

---

Sometime in the somewhat recent past somebody shared a story about a company that went belly up due to their triggers not supporting multiple rows. I brought...

RBarryYoung (5/10/2012)

---

Koen Verbeeck (5/10/2012)

---

Stefan Krzywicki (5/10/2012)

---

Yeah, I created the import package manually. I ended up getting the table structures by using an openquery in a cursor loop through a list...

Welsh Corgi (4/26/2012)

---

Franky Leeuwerck (4/9/2008)

---

My colleague found the solution.

It was actually the BIDSHelper tool that caused the BIDS SSIS solution to respond so slow on a large SSIS package.

After ...

Grant Fritchey (4/25/2012)

---

Another topic shift:

WHOOP! I'm getting to publish my article on catastrophic data loss wherein I get to call companies out by name! Yippee! Includes one link to...

L' Eomot Inversé (4/25/2012)

---

jcrawf02 (4/25/2012)

---

Jack Corbett (4/25/2012)

---

love seeing what y'all are reading. Because I'm cheap I'm going through the classics on my kindle. Currently reading my...

GilaMonster (4/25/2012)

---

Yet another topic shift...

If anyone's willing to offer suggestions, I'm looking for examples of two things:

Query optimisation/query execution myths (for a blog post series). Things like implicit conversions always...

You can also use @@ROWCOUNT as the FIRST statement in the trigger to determine the # of rows affected by the calling action.

You could do it if you designed the package to have 2 paths where 1 just executes that single task based on a configuration that sets a value in variable...