It's not even guaranteed to be unique, which would be a bigger problem .

Use EXIST with OR between to check the other tables; check the most likely table...

Hmm, but if a user bulk inserts several rows at once, many of them could get the same datetime value (at least if we're talking about std datetime accuracy to...

I agree; one single, keyed INSERT should not take that long.

(As an aside, though, that is a fairly long row (in bytes). If you do not update rows after...

--CREATE VIEW viewname AS

SELECT

COALESCE(sel.id, defaults.id) AS Id,

COALESCE(sel.name, defaults.name) AS Name

FROM (

SELECT 10 AS id, 'NotAvail' AS Name

)...

I was reading the textual plan, not the graphical one, which at a quick look I thought was using IX_sysValidationList index.

I never said it was doing a seek, I said it...

Hmm, so a given item can't go to a different status *and back* on sequential weeks:

SELECT 'B100', 1, 'FFF', 1, '2009-04-04 00:00:00.000', '2009-04-10 00:00:00.000', 0 UNION ALL

SELECT 'B100', 1, 'FFF',...

In addition to the other suggestions, make sure that:

1) Join columns are indexed

2) Indexes have the proper freespace and are reorganized / rebuilt as often as needed to keep them...

It looks to me like SQL is using the non-clus index on the lookup table. It scans it once for each LOJ, building a hash table to match to...

I agree about avoiding the concatenation. And it's definitely not needed here anyway:

SELECT *

FROM @tbl1 tbl1

INNER...

Add this column:

IND_ACTIVO

as an INCLUDEd column to your existing index.

Otherwise, the query plan looks reasonable.

It would be better if you didn't convert for the sort, but you will get...

Yes, definitely increase the RAM for the SQL server if you can.

Also, if possible isolate the physical db files on their own drives, and increase the read part of the...

Is there enough available space in the filegroup in which you intend to place this index? If not, you should probably allocate more space to it yourself beforehand rather...

Look at this in the execution plan...

USE AdventureWorks

GO

SELECT *

FROM HumanResources.Employee

WHERE EmployeeID BETWEEN 100 AND 200

Notice how it rewrote the code? Is that what you're talking about?...