What might be an option for you though, is to wrap your function call into a stored procedure. Have the stored procedure run the function, and have the stored proc...

Damn. Well, tried creating a single index with all foreign keys in it, and that didn't work. Although in retrospect, I suppose that makes sense - if I do a...

Ninja's_RGR'us (7/11/2011)

---

GilaMonster (7/11/2011)

---

Can be. Not as simple as that, but it's about giving the optimiser the option and seeing what it thinks.

Back to the original question though, short of better...

I'd like to dig your head a bit more on this topic if possible GilaMonster,

The basic query which I'm using against this table structure is always set up as follows:

SELECT

t1.ID,

t1.Field,

t2.Field,

t3.Field,

t4.Field

FROM...

Oh! Of course. Hadn't really thought about it at all like that, but it makes much more sense. It hadn't really clicked because in this situation we're looking at JOIN...

Backups are currently being made to an off-machine drive - that was one of the first things that I did. The transaction logs use SIMPLE as their type.

Unfortunately it doesn't really help, GilaMonster.

I understand that in a situation in which I had a query that did a WHERE clause against all 10 columns, having a single index...

I'm curious, why is it that using UNION instead of OR makes for performance increases? For most situations like this, the query optimiser is usually smart enough to do the...

Well, the individual indexes on the 10 columns in question are all required, as any query against this table can be made with any one of the columns as the...

IMO your best bet would be to just try researching your particular solution's needs, instead of trying to find a book on the topic.

Though you should probably try to avoid...

your best bet is to write a stored procedure from SQL Server, and then execute that stored procedure in VB.NET. It is *much* better to have all your SQL code...

you basically thinking something along the lines of

INSERT INTO TABLE1 (Columns)

OUTPUT INSERTED.ID INTO #TempTable

SELECT FROM InputRecordSet

INSERT INTO TABLE2 (Columns)

SELECT ID FROM...

That is true. Didn't think of that. A better solution would probably be to just encase the entire thing in a stored procedure, and then have the stored procedure contain...

The XML solution is the better of the choices, if you're going to be dealing with a large string. I remember one application I was developing was to build sitemaps...

IDENT_CURRENT could have the same problem - if another record is inserted into that same table from another process, you could end up with the wrong ID value.