Without test data, it's hard to say, but I believe that this query will give you the same results, while being MUCH, MUCH simpler. I'm guessing it will also...

Isn't this the same question that you asked before?

http://www.sqlservercentral.com/Forums/Topic1693743-3077-1.aspx

Drew

I'm guessing the problem is with the BETWEEN on your datetime field in the WHERE clause. There are a number of issues with using BETWEEN with datetime data. ...

You don't need any temporary tables at all. The temporary tables just add unnecessary overhead.

DECLARE @Row_Batch INT =...

j.grimanis (6/16/2015)

---

Hi all,

I do not want to confuse people, especially when they are trying o help me.

Below is a sample of how stored procedure seems :

PROC1

-----Procedure1 is calling...

Try moving your variable declarations/assignments outside of your TRY/CATCH blocks. I'm guessing that the behavior of variable assignments in TRY/CATCH blocks is different between the two versions of SQL...

I've actually wondered about this. I know this is true of left-to-right...

You simply have to join to the table twice with different aliases, which is essentially what you were doing by creating two CTEs.

select o.ID, o.OrderNumber, s.MarketCenterCity AS 'SourceMKT', d.MarketCenterCity AS...

The way to get around this is...

Yes, it is possible, but I have never done it. You'll need to use the built-in Dynamic Management Views (DMV), specifically sys.dm_exec_requests which gives you information about currently running...

ScottPletcher (6/11/2015)

---

You can't add Librarian id into the GROUP BY and accurately answer the query, since multiple librarians could have the same surname. You could pre-aggregate, but you must...

You're right, of course.

I can't give a conclusive statement even after some testing that shows that...

Luis Cazares (6/11/2015)

---

I can't assure that it's faster or better. The only way to ensure that is by...

Then you will need to add a CASE statement like so

;

WITH complaints_ordered AS

(

SELECT

Fiscal_Week,

Complaint_Num AS c1,

CASE WHEN LAG(Fiscal_Year) OVER(PARTITION BY Fiscal_Week ORDER BY Fiscal_Year) =...

This gives the expected results with the data supplied, but you haven't said what the expected behavior should be when 2012 and 2014 have data, but 2013 and 2015 don't....