How to Troubleshoot a Slow Running Query in SQL Server & Azure SQL

-

About this event

Title: How to Troubleshoot a Slow Running Query in SQL Server & Azure SQL

Abstract:

You always wanted to troubleshoot a slow running query. But you just don’t know where to begin. In this demo-heavy session, I will show you how to troubleshoot a slow running query. You will see an end-to-end query tuning example with a slow running workload. We will capture important metrics while the workload is running and then use the captured data to troubleshoot query performance issues. The technique you will learn can be applied to production straight away. This will be a 100% demo session. 

 

Register : how-to-troubleshoot-a-slow-running-query-in-sql-server-azure-sql

Comments

Post a Comment

Hi User,
Thanks for visiting My Blog and please provide your valuable feedback and subscribe for more updates. Please don't post any spam content or comments.
Thank You

Popular Posts

Failed to execute the package or element. Build errors were encountered

-
Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package
Read more

Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)

-
TITLE: Microsoft SQL Server Management Studio ------------------------------ Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks) ------------------------------ ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.SmoExtended) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=12.0.2000.8+((SQL14_RTM).140220-1752)&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Procedure 1: 1. Right click Databases 2. Restore Database... 3. [General] Source from Device, select the bak file 4. [General] Change the Destination database name to a new name 5. [Files] Change mdf and ldf Restore As paths to a different, new path 6. [Options] (unnecessary on the other computer) Check Overwrite the existing database (WITH_REPLACE) 7. [Options] (unnecessary on the other computer) ...
Read more

Cannot convert "Column" between a unicode and a non-unicode string data types in SSIS

-
Error: Cannot convert "Column" between a unicode and a non-unicode string data types in SSIS Solution 1: 1. Right click on source task. 2. click on "Show Advanced editor". -- advanced edit option for source task in ssis 3. Go to "Input and Output Properties" tab. 4. select the output column for which you are getting the error. 5. Its data type will be "String[DT_STR]". 6. Change that data type to "Unicode String[DT_WSTR]". --Changing the data type to unicode string 7. save and close. Solution 2: Add Data Conversion transformations to convert string columns from non-Unicode (DT_STR) to Unicode (DT_WSTR) strings. You need to do this for all the string columns
Read more