Merge pull request #184 from Microsoft/amitmsft-patch-3

Amitmsft patch 3

samples/demos/LQS/Live Query Stats - Activity Monitor.sql

@@ -59,4 +59,4 @@ GO
 	INNER JOIN Person.Person AS p ON h.CustomerID = p.BusinessEntityID 
 	INNER JOIN Production.Product AS pr ON d.ProductID = pr.ProductID 
 	) SELECT * FROM Prices; 
-GO
+GO

samples/demos/LQS/Live Query Stats - Own Session.sql

@@ -58,4 +58,4 @@ GO
 	INNER JOIN Person.Person AS p ON h.CustomerID = p.BusinessEntityID 
 	INNER JOIN Production.Product AS pr ON d.ProductID = pr.ProductID 
 	) SELECT * FROM Prices; 
-GO
+GO

samples/demos/Showplan/HashWarning.sql

@@ -30,7 +30,7 @@ GO
 
 -- Get Actual Execution Plan
  
--- Execute the stored procedure first with parameter value ‘WA’ – which will select 1% of data. 
+-- Execute the stored procedure first with parameter value ‘WA’ – which will select 1% of data. 
 DBCC FREEPROCCACHE
 GO
 EXEC CustomersByState 'WA'
@@ -49,4 +49,4 @@ it is split into sub-partitions, which are also processed separately.
 This splitting process continues until each partition fits into available memory 
 or until the maximum recursion level is reached.
 In this case it stopped at level 1.
-*/
+*/

samples/demos/Showplan/MemoryGrant_Warning.sql

@@ -18,4 +18,4 @@ GO
 In SELECT node properties:
 MaxQueryMemory for maximum query memory grant under RG MAX_MEMORY_PERCENT hint
 MaxCompileMemory for maximum query optimizer memory in KB during compile under RG
-*/
+*/

samples/demos/Showplan/SortWarning.sql

@@ -18,4 +18,4 @@ GO
 /*
 Observe the type of Spill = 1
 Means one pass over the data was enough to complete the sort in the Worktable
-*/
+*/

samples/demos/mssqltiger/README.md

@@ -1,2 +0,0 @@
-<h1>MSSQLTIGER Demos</h1>
-This is a repository of the scripts used during demos that are delivered by the SQL Server Tiger team. 

samples/demos/xEvents/HashWarning.sql

@@ -42,7 +42,7 @@ ADD TARGET package0.event_file(SET filename=N'C:\IP\Tiger\TR23\Demos\Demo 1.1 -
 WITH (MAX_MEMORY=4096 KB,EVENT_RETENTION_MODE=ALLOW_SINGLE_EVENT_LOSS,MAX_DISPATCH_LATENCY=30 SECONDS,MAX_EVENT_SIZE=0 KB,MEMORY_PARTITION_MODE=NONE,TRACK_CAUSALITY=OFF,STARTUP_STATE=OFF)
 GO
  
---Execute the stored procedure first with parameter value ‘WA’ – which will select 1% of data. 
+--Execute the stored procedure first with parameter value ‘WA’ – which will select 1% of data. 
 DBCC FREEPROCCACHE
 GO
 ALTER EVENT SESSION [HashSpills] ON SERVER STATE = START
@@ -65,4 +65,4 @@ it is split into sub-partitions, which are also processed separately.
 This splitting process continues until each partition fits into available memory 
 or until the maximum recursion level is reached.
 In this case it stopped at level 1.
-*/
+*/

samples/demos/xEvents/PerfStats_XE_Demo.sql

@@ -39,4 +39,4 @@ GO
 -- After running query, get new signed query or query plan hash and run below to see new columns in DMV
 SELECT * FROM sys.dm_exec_query_stats
 WHERE CAST(query_hash AS BIGINT) = -5396503127623128976;
---WHERE CAST(query_plan_hash AS BIGINT) = 3230654061787450360
+--WHERE CAST(query_plan_hash AS BIGINT) = 3230654061787450360

samples/demos/xEvents/SortWarning.sql

@@ -30,4 +30,4 @@ GO
 /*
 Observe the type of Spill = 1
 Means one pass over the data was enough to complete the sort in the Worktable
-*/
+*/