To return a single "OR'd" row, I think you can just add MAX()es to the "standard" & conditions:

SELECT

STUFF(

MAX(CASE...

I think the overhead of XML is unwarranted here, if I understand the desired output correctly. needed[/i].]

But,...

Not 100% sure what output you want: the warranty date in a separate column based on its status or a status column itself, like below.

SELECT

machNameTab.machName

,warranty

,CASE WHEN warranty...

If you're saying all the tables already have the correct clustered indexes, as I noted in my previous post, I don't agree with that for at least:

dbo.DCSubRegionTran

This isn't something where...

First, as always, verify that you have the best clustered index on each table.

For example, just from a very quick look, table:

dbo.DCSubRegionTran

should have:

DCSRFiscYear

as its first clustering column, assuming you (nearly)...

I'd urge you to add a bit flag to the PROD table to indicate whether a given row has 7 consecutive valid flow values or not, rather than recomputing every...

SELECT

ISNULL(sales.ItemCode, returns.ItemCode) AS ItemCode,

ISNULL(sales.total_sales, 0) - ISNULL(returns.total_returns, 0) AS NetSales

FROM (

SELECT T0.ItemCode, SUM(T0.LineTotal) as total_sales

...

Then the error must be...

Just in general, if you (almost) always query table* "v0_AccountSecuritiesBASEL_III" by DataDate, then you should strongly consider clustering the table on that date first, rather than on -- my best...

Instead of changing the code like that, just remove the UPDATE STATS statement entirely. You shouldn't be doing that all throughout code anyway.

jmoorhead14 (5/22/2014)

DECLARE @spid int

SELECT

@spid = MIN(l.request_session_id)

FROM

sys.dm_tran_locks l

INNER JOIN sys.dm_tran_active_transactions t...

If you're on Enterprise Edition you can add "ONLINE = ON" and the table can still be used while the index is being built.

I prefer to always explicitly specify the...

Sample data in a consumable format would be most helpful.

I'm pretty sure my query gives you that. ...

Hmm, I expected my code to give you that.

Can the same guid appear more than once??

Instead of disabling the trigger, which would affect all row updates, of course, you might want to consider using CONTEXT_INFO() to selectively bypass trigger processing just for your updates.

For example:

CREATE...