Dear all

I experienced a problem wit a SQL Server Datawarehouse I want to report to
the community. I have a table with a unique unclustered index. A SSIS package
fills this table during load time. In this package I use a OleDB Destination
Data Flow item to fill the table, this with the option fast load.

This worked fine until I installed SQL Server 2005 SP2. A couple days after
the installation (and a couple of runs of the package mentioned above) I
experienced insert failures with the error code -1071607685, meaning
DTS_E_OLEDBDESTINATIONADAPTERSTATIC_UNAVAILABLE or No status is available.
After doing some research I found out that this error happens if you insert
double rows where an unique index exists.

The odd thing was that there were no double rows in this table! And worse, I
couldn’t process my measure group anymore that depended on this table.

So I made a restore of the database before this insert errors happened and
switched all oledb destinations dataflow item from fast load to normal. It
looks like this resolved my problem.

Hope this is a help for others experiencing this issue.

Kind regards,

Marc

Thanks, Peter!

Hello Marc,

Thank you for sharing the experience and this shall defenitely benefit the
community!

Also, if you do not use Fast Load option, the error might be more specific.
With Fast Load option you are using Maximum Insert batch size parameter.
Any time there is a bad row in a batch, the whole batch is redirected to
Error table with Error Redirection defined on the package. The workaround
is to re-process the good rows back from the Error table without the Fast
Load option.

Thanks & Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.