No, would that make a difference? There are about twenty auxilliary tables, each with single one-to-many relationship to the main records table. The...

Sorry, my screw-up - I had a typo in the SQL. But the results are the same. It does drop the constraint now, but the INSERT INTO still works only...

stewartc-708166 (12/17/2010)

---

Have you tried disabling the foreign key constraints before begining the insert, then re-enabling them thereafter?

e.g.

-- Disable the constraint.

ALTER TABLE mySampleTable NOCHECK CONSTRAINT FK_SampleTableDetail_SampleTable;

-- Reenable the constraint.

ALTER TABLE mySampleTable...

I have such indexes now. My question was whether...

'Fraid not,:-) I've experienced enough horror shows to know full well just how good I have it here. They buy good equipment, ask for sensible things, listen to me and...

'Fraid not,:-) I've experienced enough horror shows to know full well just how good I have it here. They buy good equipment, ask for sensible things, listen to me and...

> I think you also need to consider the expense of

> maintaining all of those indexes. Every

> insert/delete will have multiple indexes to update.

> Updates can affect multiple also.

Thank you,...

> Create targeted indexes for the combinations that

> you know are in use. Once you've done that, consider

> additional indexes for columns that may be used in

> the search but...

> The point is that SQL won't always chose index

> intersection, it's expensive, it'll only do it if

> there's a fairly large row count.

I would call it medium-sized, around 80,000...

Hm, thank you, but I'm not sure that I follow this fully. There is discussion of how a properly constructed multi-column index is a better choice than separate column indexes,...

No parameters, selecting from the 80,000 records in the SQL table is done by joining to a local table. This project started life as an Access database, so there is...