Here's the last one I posted, I'll give you an idea of what needs to be done / posted.

https://connect.microsoft.com/SQLServer/feedback/details/684806/rollback-causes-db-to-go-suspect-only-repairable-with-repair-allow-data-loss

Thanks for the feedback. Did you post a connect item on this so that we may test & vote on it?

SQLRNNR (10/3/2011)

Awesome - a couple years late on that one -unless it is the same person with a name...

What???

So you don't mind extending the amount of time the prod db is...

What's the error returned by checkdb?

GilaMonster (10/3/2011)

And a QA environment...

Answer this, what is the table that only has a PK <and possibly no fk>.

This is where you do the first insert.

Then you can insert in the child tables.

You need to use left (col, patindex(find the space))

Replace won't work here.

P.S. What I have is for "normal" t-sql, never tried it with SSIS

Nope.

And it doesn't really get easier than copy / paste the select statement and simply add

where not exists (SELECT * FROM dbo.fk where fk.a = base.a)

The error should tell you what Fk is violated.

With that you can do a select from (what you insert) where not exists (match to fk table)

All the more reasons to put it in place.

This is a super easy...

If I were in the ops shoes, change management procedure / code reviews would be on top of my list in the currently hapenning meeting.

Happy was in quotation for a reason. I don't have anything else to offer at this point.

Maybe now is the time to have that little meeting.

Actually performance wise you're better off using a temp table with Clustered PK which drastically helps on the plan generation.

Nope, but this time you need to let it run to completion (with the correct switches).

Once it's done post the error messages and we'll see what's the best fix. ...