SQL Server 2019, in my opinion, is one of the greatest releases that has arisen from Microsoft in the last decade. It comes with a multitude of enhancements across the board in the data platform ecosystem. However, there are two features that significantly impact the day to day lives of data professionals everywhere, namely Accelerated Database Recovery (ADR) and Resumable Index Creation. How impressive would it be to have a rollback operation complete in seconds where previously it would be hours or days? Would you like to have the ability to manage how you create that index on your multi-billion row table? Now you can! In this session we will examine in detail these two new features and demonstrate how they can help to accomplish both of those goals and improve your life when dealing with rollbacks and managing index operations. The days of horror stories around these two activities are a thing of the past thanks to SQL Server 2019.
#URL that needs to be fetched | |
$url = "https://site.state.gov/default.aspx" | |
#get the server name in case the process jumps to another script | |
$serverName = $env:computername | |
#wrapped it into a try/catch for some type of error handling | |
TRY { | |
#use invoke-webrequest to fetch a session from the site | |
Invoke-WebRequest $url -SessionVariable session -UseBasicParsing |
DECLARE @date CHAR(8) | |
SET @date = (SELECT CONVERT(char(8), GETDATE(), 112)) | |
DECLARE @path VARCHAR(125) | |
SET @path = '\\UNCPath\Folder\' | |
;WITH MoveCmdCTE ( DatabaseName, MoveCmd ) | |
AS ( SELECT DISTINCT | |
DB_NAME(database_id) , |
Many think that moving to the cloud will not only help brighten your teeth but also solve all your bad coding practices that give you poorly performing queries. If it's done correctly, implementing Azure SQL Database can help with one of those two and while it can mask things well, the best solution is to fix the bad code. In this hour-long session, we'll examine several different methods that you can utilize to help fix bad query performance starting with the underlying service tier. Next, we'll investigate what options are available directly from the Azure portal to determine where the bottlenecks might reside along with possible ways to fix them. Lastly, we will interrogate which native SQL Server tools exist within Azure SQL Database that can really help solve performance issues you might be having. You'll leave this session with a solid understanding of how to trouble shoot performance issues in Azure SQL Database and what you might be able to
Many think that moving to the cloud will not only help brighten your teeth but also solve all your bad coding practices that give you poorly performing queries. If it's done correctly, implementing Azure SQL Database can help with one of those two and while it can mask things well, the best solution is to fix the bad code. In this hour-long session, we'll examine several different methods that you can utilize to help fix bad query performance starting with the underlying service tier. Next, we'll investigate what options are available directly from the Azure portal to determine where the bottlenecks might reside along with possible ways to fix them. Lastly, we will interrogate which native SQL Server tools exist within Azure SQL Database that can really help solve performance issues you might be having. You'll leave this session with a solid understanding of how to trouble shoot performance issues in Azure SQL Database and what you might be able to do to help fix them. |
########################################################################################## | |
#- Author: John Morehouse | |
# Date: August 2015 | |
# T: @SQLRUS | |
# E: john@jmorehouse.com | |
# B: http://sqlrus.com | |
# | |
# THIS CODE AND INFORMATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY | |
# AND/OR FITNESS FOR A PARTICULAR PURPOSE. | |
# |