09/15/2008 10:05 PM 123,392 Attunity.SSIS.Design.dll
09/15/2008 10:06 PM 242,688 AttunitySSISOraAdapters.dll
09/15/2008 10:05 PM 86,528 AttunitySSISOraConnections.dll

under BIDS.

How do I create an Attunity connector under ‘Connection Managers’ ?
Nothing with a name akin to ‘Attunity’ appears in the list or available when I rt-click ‘New Connection’
and see the ‘SSIS Connection Manager’.

or should I forget Attunity and install both Oracle 32-bit and 64-bit drivers ?

Thanks,
XPXJ
562-552-1284

The joke here is that I really learned how to use C# a lot better, because it was out of the question to waste time on that joke of SSIS to automate things. Using MS Studio – can learn on the job. Using SQL Management studio – can learn on the job. Using SSIS – take a few months off work and play around with a morbidly complex and buggy program. In my workplace there are a LOT of flat files that need to be parsed and imported into SQL tables on a regular basis, and I’m halfway through writing my OWN framework to do all that, because SSIS is so flippin awful.

>> Bad Errors:
Yeah, SSIS does report errors horribly badly at times. The most annoying seem to be
ones caused by deletion of a component that triggers an downstream problem in a data
flow.

>> Keeping track of what it shouldn’t:
>> Never had this happen. NEVER.
I have. SSIS sometimes seems to retain data about connection managers that have been
deleted from the package. They aren’t there, and can’t be removed, short or directly
editing the XML. Script components are another case. I find it truly ridiculous that
a defect in the cached compiled CDATA block can prevent a script component from being
edited; the obvious correct behavior, IMHO, is to offer the option to rebuild from the
cached source.

>> UI Formatting instructions:
>> At least you have an XML file that can be parsed.
Parsed with enormous difficulty. The worst problem caused by combining the UI formatting
with the executable content is that is is impossible to effectively diff versions. Every
attempt to do so results in thousands of changes that are effectively “this control moved
one pixel over.”

>> Hard to debug:
>> Within reason, yes, this is true. You now know about using the watch box.
In addition, it’s very difficult to profile preformance and find bottlenecks. Only after
adding LOTS of additional script components to log data were we able to uncover the
causes of some problems and work around them. In some cases this resulted in a 40-fold
speed increase over the defaults in SSIS.

Two more things I’d like to add to the defect list:

Compile doesn’t mean compile everything. There is apparently no way to force a recompile
on script components, other than open them all in the editor, save, and exit — really tedious.

Continuous validation! I understand why SSIS was coded to validated everything every time
at run time; I don’t agree with it, but I understand it. But why can’t developers set the
dev environment to validate only when I say to compile!

I take your point though. Cryptic erros are usually raised by “things” external to the package – all SSIS is doing is surfacing them for you.

So yes, this point about error messages can be argued either way and I am somewhere in the middle.

-Jamie