Wow, great thinking sir! That does indeed appear to be the case.

It was an iso, but I extracted the files from it using 7-Zip and then did the install from the extracted...

cafescott (10/24/2014)

---

Well, if you keep all your querying logic in one place rather than splitting some of it off in SSIS, it makes it easier to find it later on....

cafescott (10/24/2014)

---

I've said this before, so hopefully I don't come off as a broken record. However, I would never use derived columns in SSIS. Instead, I would use...

Yes, line by line, write to a file indicating that the line has been processed.

Then I am running out of ideas. Problems like this are tough to debug.

You could try running the job in 32-bit mode (which is how it would have run in...

Then it sounds like a permissions issue. Does the SQL Agent user have sufficient rights?

stopd87 (10/24/2014)

---

Hi Everyone,

I got a problem with SQL Server Agent Job. My job can't finished and keep stuck. I suspected that the job is stop on script task.

When...

Koen Verbeeck (10/23/2014)

---

Or just...

Good point! I try to stop people doing that in production code, but a few get through the net.

Configure your flat file source connection with | as the column delimiter and let SSIS do the work for you. See here[/url] for an example.

Is the data coming from a flat file?

Are there always three items?

Are the columns always the same length?

Grant Fritchey (10/23/2014)

---

You could try SQL Search[/url] from Red Gate. It's a free tool that should find those references pretty easily.

Mandatory disclaimer (although I'm not sure why for a free...

If you have your databases scripted into...