Contoso has an Azure subscription in North Europe that contains the corporate infrastructure. The current infrastructure contains a Microsoft SQL Server 2017 database. The database contains the following tables.
The FeedbackJson column has a full-text index and stores JSON documents in the following format.
The support staff at Contoso never has the unmask permission.
Requirements
Contoso is deploying a new Azure SQL database that will become the authoritative data store for the following;
Sometimesthe ingestion pipeline fails due to malformed JSON and duplicate payloads.
The engineers at Contoso report that the following dashboard query runs slowly.
SELECT VehicleTd, Lastupdatedutc, EngineStatus, BatteryHealth FROM dbo.VehicleHealthSumary where fleetld- gFleetld ORDER BV LastUpdatedUtc DESC;
You review the execution plan and discover that the plan shows a clustered index scan.
vehicleincidentReports often contains details about the weather, traffic conditions, and location. Analysts report that it is difficult to find similar incidents based on these details
Planned Changes
Contoso wants to modernize Fleet Intelligence Platform to support Al-powered semantic search over
incident reports.
Security Requirements
Contoso identifies the following telemetry requirements:
• Telemetry data must be stored in a partitioned table.
• Telemetry data must provide predictable performance for ingestion and retention operations.
• latitude, longitude, and accuracy JSON properties must be filtered by using an index seek.
Contoso identifies the following maintenance data requirements:
• Ensure that any changes to a row in the MaintenanceEvents table updates the corresponding
value in the LastModif reduce column to the time of the change.
• Avoidrecursive updates.
AI Search, Embedding’s, and Vector indexing
The development learn at Contoso will use Microsoft Visual Studio Code and GitHub Copilot and will
retrieve live metadata from the databases. Contoso identifies the following requirements for
querying data in the FeedbackJson column of the customer-Feedback table:
• Extract the customer feedback text from the JSON document.
• Filter rows where the JSON text contains a keyword.
• Calculate a fuzzy similarity score between the feedback text and a known issue description.
• Orderthe results by similarity score, with the highest score first
View Mode
Q: 2
You have a SQL database in Microsoft Fabric that contains a table named dbo.Orders, dbo.Orders has
a clustered index, contains three years of data, and is partitioned by a column named OrderDate by
month.
You need to remove all the rows for the oldest month. The solution must minimize the impact on
other queries that access the data in dbo.orders.
Solution: Run the following Transact-SQL statement.
DELETE FROM dbo.Orders
WHERE OrderDate < DATEADD(nonth, -36, SYSUTCDATETIME());
Does this meet the goal?
Options
Discussion
No comments yet. Be the first to comment.
Be respectful. No spam.
Correct Answer:
B
Explanation
The DELETE statement is a fully logged operation that removes rows one by one, recording each deletion in the transaction log. For a large number of rows (an entire month's data), this will be slow, consume significant transaction log space, and hold extensive locks on the data pages. This high level of locking and resource consumption will negatively impact the performance of other queries accessing the table, failing the requirement to minimize impact. A partition-level TRUNCATE operation would be far more efficient.
Why Incorrect
A. The solution is incorrect because a row-by-row DELETE operation is resource-intensive and does not meet the goal of minimizing impact on other queries, especially when compared to a minimally logged partition TRUNCATE.
References
1. Microsoft. (2024, February 27). TRUNCATE TABLE (Transact-SQL). SQL Server. Microsoft Learn. In the section "Comparing TRUNCATE TABLE and DELETE," it explicitly states, "TRUNCATE TABLE uses fewer transaction log resources than DELETE."
2. Microsoft. (2024, February 27). DELETE (Transact-SQL). SQL Server. Microsoft Learn. This document describes the row-removal process and locking behavior, which confirms it is a more intensive operation than a partition truncate.
