By using input from real memory consumption during query execution, Memory Grant input Persistence in SQL Server 2022 is a potent feature that helps optimize query performance. In order to improve the accuracy of memory grant calculations for subsequent executions of the same or comparable queries, SQL Server gathers and stores this information.
2024-06-12
2,084 reads
An updatable view in SQL Server is a view that allows modifications such as INSERT, UPDATE, or DELETE operations on the underlying tables through the view.
2024-04-22
5,977 reads
Provisioning infrastructure in a timely and reliable manner is essential for agile development. One well-liked method that lets you use code to automate resource management and provisioning is infrastructure as code (IaC). Azure Resource Manager templates are one IaC solution for Azure (ARM templates).
2024-02-02
2,650 reads
This article shows how you can configure auditing on your Azure SQL Database.
2024-01-22
2,178 reads
One of the most effective ways to fully utilize your data is to create an Azure Hyperscale database. The principles of Azure Hyperscale databases have been discussed in this article, including their cost-effectiveness, worldwide accessibility, automatic scaling, and reliable performance.
2023-12-22
2,108 reads
Batch execution mode is a new optimization feature in SQL Server. In this Article, we'll explore how Batch execution mode works and how you can use it to get faster query results on Rowstore data.
2023-10-30
4,466 reads
SQL databases are crucial for businesses, so it's critical to back them up. A dependable and affordable option is offered by Azure Blob Storage. Let's examine the advantages, the steps involved in backing up to and restoring from a device, recommended practices, and more.
2023-09-15
11,443 reads
In this Article , We will delve into the world of Query Store and explore how to use Optimized Plan Forcing to improve performance in SQL Server 2022. We will discuss what it is, how it works, and how it can impact your system's performance.
2023-09-04
5,218 reads
PSPO (Parameter Sensitive Plan Optimization) is a SQL Server feature that improves query performance by accepting varied data sizes based on the runtime parameter value(s) specified by the customer. It deals with the situation in which a single cached plan for a parameterized query isn't the best option for all potential incoming parameter values. Non-uniform data distributions exhibit this phenomenon. When using PSPO, SQL Server keeps several execution plans for a single query, each one customized for a particular parameter value. With the help of this feature, numerous execution plans for a parameterized query are generated, each of which is tailored for a certain range of parameter values.
2023-07-21
4,435 reads
The ability to pause and then resume index rebuilds has been added to SQL Server. This is a fantastic feature, and with the release of SQL Server 2019, we can now replicate it on the actual create index process. Learn how to use this feature in this short article.
2023-06-26
12,509 reads
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
By John
If you’ve used Azure SQL Managed Instance General Purpose, you know the drill: to...
By DataOnWheels
Ramblings of a retired data architect Let me start by saying that I have...
Hello team Can anyone share popular azure SQL DBA certification exam code? and your...
Comments posted to this topic are about the item Faster Data Engineering with Python...
Comments posted to this topic are about the item Which Result II
I have this code in SQL Server 2022:
CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
exec('SELECT ProductName FROM product;')
END;
GO
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned? See possible answers