In some cases, the columns to be indexed disregarded the column names. For exampe, I have columns named with an underscore....these were parsed as separate column names. And,...

The create index syntax appears flawed as well. There are several occurrences where the column names are not parsed correctly. It does create a good result set to...

Thanks for the revised code. I've added the following to proc_FilltblIndexUsageInfo:

where

so.type = 'u'

and...

Agreed. Also, index reorgs can somtimes wreak havoc with TL shipping. I haven't had the chance to completely finish these scripts due to time constraints. Is anybody...

I was just trying to figure this out and I came across your post. Here's the solution that worked for me:

DTSRun /S"Server" /N"Package Name" /E

The tilde (~)...

No, they're all named UP_ I actually have a total of three. All start with the prefix UP_. One of the three gets categorized correctly. Basically,...

paul.ibison (3/6/2008)

---

Brandon,

all due respect but I think you're missing the point.

Judging by some of the questions, some others (Jeff apart) have also never really tried to solve this problem...

admin (3/5/2008)

---

Definitely an ingenious solution; however, it can quickly become a poor approach when having to deal with larger import file -think telephone call records for instance.

I've found that the...

paul.ibison (3/5/2008)

---

I looked at the conditional split, but if you have >50 columns (as I have), you'll need to manually define each column - that means define the name and...

Laura Meyerovich (3/5/2008)

---

If the goal is to skip the "incorrect" rows, the simplest way is to set a DTS package for data import, and set error number to 10 (assuming...

I think a combination of omitting the first row and doing a conditional split would do just fine. This the method I use since I receive a number of...

For future reference, you may want to consider doing what I do when deleting a considerable amount of archived data.  I create a temporary table where I store the values...

That was the issue.  The n' prefixes on the second line were also not necessary, I realized this after I posted.

Problem appears solved.  The developer is using JBDC and another person in our department researched that angle and came up with this solution link:   

Thanks, Steve, I'll try both.