I cannot imagine any method that will not be a massive hit on your server.

Perhaps if you explained why you need to create such a massive amount data, some of...

This piece of code will not work for @NumberOfRows > 31.

urbanromio2 (11/27/2016)

---

Declare @NumberOfRows int;

Declare @Numbers Table(Number int);

;With cte As

(Select 1 As Number

Union All

Select Number + 1

From cte

Where Number < Power(2,...

You want to look into the PIVOT relational operator

https://msdn.microsoft.com/en-us/library/ms177410.aspx

With a few nested queries, you could also sue the following code to generate the JSON

SELECT '['

+ STUFF((

...

DesNorton (11/24/2016)

---

I have managed to recreate the above JSON output using TSQL, but it is ugly and relies on lots of hard-coding and replace statements. If nobody can come...

SQL...

bineet.dungdung (11/23/2016)

---

there is no defined set of formulas used here , it may vary for every row. So writing formulas into a case would ask of hardcoding , aim is...

Thank you Michael, but this did not solve my issue. In my case the installation runs through to the end, but...

The date filters between these 2 queries are not the same.

... STARTTIME > '2016-12-06T16:00:00' AND a.EndTime < '2016-12-11T10:00:00'

... starttime > '2016/12/10' and endtime < '2016/12/18'

You need to join the table back to itself to get the previous record, and then do the math

SELECT cur.*

, ISNULL(DATEDIFF(MINUTE, prev.TimeOutRoom, cur.TimeInRoom), 0) AS TurnaroundMinutes

FROM #Test...

The MERGE statement will take all of the data that you provide it.

However,...

OK. So it seems that your TEMP_SUPPLIER has duplicate values for SUPPLIER_CODE.

To prove this, let's create a simple data set that will cause the PK error

CREATE TABLE #M_SUPPLIER (

...

Please supply table structures for M_SUPPLIER and TEMP_SUPPLIER, as well as sample data that will consistantly cause the error that you are getting.

MERGE M_SUPPLIER A --- TARGET

USING TEMP_SUPPLIER B --- SOURCE DUMMY

ON A.SUPPLIER_CODE = B.SUPPLIER_CODE

-- You are matching on A.SUPPLIER_CODE = B.SUPPLIER_CODE

-- Then you say WHEN A.SUPPLIER_CODE <> B.SUPPLIER_CODE

WHEN MATCHED --AND A.SUPPLIER_CODE...

Dynamic cross-tab queries are dealt with expertly and in great detail in these two Jeff Moden articles:

http://www.sqlservercentral.com/articles/T-SQL/63681/

http://www.sqlservercentral.com/articles/Crosstab/65048/