Browse Source

Adding SQLIntersection

pmasl 6 years ago
parent
commit
a1f8e8ab1e

+ 2 - 0
AdaptiveIndexDefrag/README.md

@@ -11,6 +11,8 @@ Yes, but it is used as a part of a full maintenance solution that also handles d
 **On what version of SQL can I use it?**
 **On what version of SQL can I use it?**
 This procedure can be used from SQL Server 2005 SP2 onwards, because of the DMVs and DMFs involved.
 This procedure can be used from SQL Server 2005 SP2 onwards, because of the DMVs and DMFs involved.
 
 
+NOTE: no longer garanteed to work with SQL Server 2005. Use at your own volution.
+
 **How to deploy it?**
 **How to deploy it?**
 Starting with v1.3.7, on any database context you choose to create the usp_AdaptiveIndexDefrag and its supporting objects, open the attached script, and either keep the @deploymode variable at the top to upgrade mode (preserving all historic data), or change for new deployments or overwrite old versions and objects (disregarding historic data).
 Starting with v1.3.7, on any database context you choose to create the usp_AdaptiveIndexDefrag and its supporting objects, open the attached script, and either keep the @deploymode variable at the top to upgrade mode (preserving all historic data), or change for new deployments or overwrite old versions and objects (disregarding historic data).
 
 

BIN
Sessions/SQLDay-2017/Enhancements-that-will-make-your-SQL-database-engine-roar---SP1.pdf


BIN
Sessions/SQLDay-2017/Enhancements-that-will-make-your-SQL-database-engine-roar-Demos.zip


BIN
Sessions/SQLDay-2017/Gems-to-help-you-troubleshoot-query-performance-Demos.zip


BIN
Sessions/SQLDay-2017/Gems-to-help-you-troubleshoot-query-performance.pdf


BIN
Sessions/SQLIntersection-2018/SQL-Server-Upgrades-Done-the-Right-Way/SQL-Server-Upgrades-Done-the-Right-Way.pptx


+ 23 - 0
Sessions/SQLIntersection-2018/SQL-Server-Upgrades-Done-the-Right-Way/query-tuning-assistant/README.md

@@ -0,0 +1,23 @@
+This is a repro package to demonstrate how to upgrade a database compatibility level using Query Tuning Assistant. 
+This feature is using telemtry from the Query Store feature we launched with Azure SQL Database and SQL Server 2016 to detect upgrade-related regressions.
+
+This repro assumes the following:
+
+- SQL Server 2016+ installed (pick at minimum Database Engine) on Windows.
+- You have installed SQL Server Management Studio v18
+- You have downloaded the RML Utilities from https://www.microsoft.com/en-us/download/details.aspx?id=4511.
+- These demos use a named instance called SQL2017. You will need to edit the .cmd scripts which connect to SQL Server to change to a default instance or whatever named instance you have installed.
+
+0. Install ostress from the package RML_Setup_AMD64.msi. Add C:\Program Files\Microsoft Corporation\RMLUtils to your path.
+
+1. Attach the AdventureWorksDW2012 database to your SQL Server 2016+ instance. The adventure-works-2012-dw-data-file.mdf is provided in https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks2012
+
+3. Start QTA following instructions in https://docs.microsoft.com/en-us/sql/relational-databases/performance/upgrade-dbcompat-using-qta.
+
+4. When requested to run a baseline collection, run PreUpgrade.cmd to customize the AdventureWorksDW2012 database and start the demo. Run it to completion...
+
+5. After its completed, continue QTA workflow. 
+
+6. When requested to re-run the same workload, run PostUpgrade.cmd. Run it to completion...
+
+7. After its completed, continue QTA workflow.

BIN
Sessions/SQLIntersection-2018/SQL-Server-Upgrades-Done-the-Right-Way/query-tuning-assistant/qta-demo.zip