Download Administering Relational Databases on Microsoft Azure.examtorrent.DP-300.vV12-35.2021-02-05.1e.57q.vcex

Azure Private Link enables you to access Azure PaaS Services (for example, Azure Storage and SQL Database) and Azure hosted customer-owned/partner services over a private endpoint in your virtual network. 
Traffic between your virtual network and the service travels the Microsoft backbone network. 
Exposing your service to the public internet is no longer necessary. 
Reference:
https://docs.microsoft.com/en-us/azure/private-link/private-link-overview

Box 1: sys.resource_stats
sys.resource_stats returns CPU usage and storage data for an Azure SQL Database. It has database_name and start_time columns. 
Box 2: DateAdd
The following example returns all databases that are averaging at least 80% of compute utilization over the last one week. 
DECLARE @s datetime; 
DECLARE @e datetime; 
SET @s= DateAdd(d,-7,GetUTCDate()); 
SET @e= GETUTCDATE(); 
SELECT database_name, AVG(avg_cpu_percent) AS Average_Compute_Utilization FROM sys.resource_stats WHERE start_time BETWEEN @s AND @e GROUP BY database_name HAVING AVG(avg_cpu_percent) >= 80 Incorrect Answers: 
sys.dm_exec_requests:
sys.dm_exec_requests returns information about each request that is executing in SQL Server. It does not have a column named database_name. 
sys.dm_db_resource_stats:
sys.dm_db_resource_stats does not have any start_time column. 
Note: sys.dm_db_resource_stats returns CPU, I/O, and memory consumption for an Azure SQL Database database. One row exists for every 15 seconds, even if there is no activity in the database. 
Historical data is maintained for approximately one hour. 
Sys.dm_user_db_resource_governance returns actual configuration and capacity settings used by resource governance mechanisms in the current database or elastic pool. It does not have any start_time column. 
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-resource-stats-azure-sql-database

Follow these same steps to create striped virtual disk:
Create Log Storage Pool. 
Create Virtual Disk 
Create Volume 
Box 1: a storage pool
Box 2: a virtual disk that uses stripe layout
Disk Striping: Use multiple disks and stripe them together to get a combined higher IOPS and Throughput limit. The combined limit per VM should be higher than the combined limits of attached premium disks. 
Box 3: a volume
Reference:
https://hanu.com/hanu-how-to-striping-of-disks-for-azure-sql-server/

Box 1: SINGLE_USER
The specified database must be in single-user mode to use one of the following repair options. 
Box 2: REPAIR_ALLOW_DATA_LOSS
REPAIR_ALLOW_DATA_LOSS tries to repair all reported errors. These repairs can cause some data loss.  
Note: The REPAIR_ALLOW_DATA_LOSS option is a supported feature but it may not always be the best option for bringing a database to a physically consistent state. If successful, the REPAIR_ALLOW_DATA_LOSS option may result in some data loss. In fact, it may result in more data lost than if a user were to restore the database from the last known good backup. 
Incorrect Answers:
REPAIR_FAST 
Maintains syntax for backward compatibility only. No repair actions are performed. 
Box 3: MULTI_USER
MULTI_USER 
All users that have the appropriate permissions to connect to the database are allowed. 
Reference:
https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-checkdb-transact-sql

Instead restore Database1 from Server1 to the Server2 by using the RESTORE Transact-SQL command and the REPLACE option. 
Note: REPLACE should be used rarely and only after careful consideration. Restore normally prevents accidentally overwriting a database with a different database. If the database specified in a RESTORE statement already exists on the current server and the specified database family GUID differs from the database family GUID recorded in the backup set, the database is not restored. This is an important safeguard. 
Reference:
https://docs.microsoft.com/en-us/sql/t-sql/statements/restore-statements-transact-sql

Columnstore tables and indexes are always stored with columnstore compression. You can further reduce the size of columnstore data by configuring an additional compression called archival compression. 
Note: Columnstore - The columnstore index is also logically organized as a table with rows and columns, but the data is physically stored in a column-wise data format. 
Incorrect Answers:
B: Rowstore - The rowstore index is the traditional style that has been around since the initial release of SQL Server. 
For rowstore tables and indexes, use the data compression feature to help reduce the size of the database. 
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/data-compression/data-compression

The Data Migration Assistant (DMA) helps you upgrade to a modern data platform by detecting compatibility issues that can impact database functionality in your new version of SQL Server or Azure SQL Database. DMA recommends performance and reliability improvements for your target environment and allows you to move your schema, data, and uncontained objects from your source server to your target server. 
Note: SQL Managed Instance supports the following database migration options (currently these are the only supported migration methods):
Azure Database Migration Service - migration with near-zero downtime. 
Native RESTORE DATABASE FROM URL - uses native backups from SQL Server and requires some downtime. 
Reference:
https://docs.microsoft.com/en-us/sql/dma/dma-overview

Step 1: Set up the Active Directory Admin for AzSQL1.
Step 2: Connect to DB1 by using the server administrator.
Sign into your managed instance with an Azure AD login granted with the sysadmin role. 
Step 3: Create a user by using the FROM EXTERNAL PROVIDER clause.
FROM EXTERNAL PROVIDER is available for creating server-level Azure AD logins in SQL Database managed instance. Azure AD logins allow database-level Azure AD principals to be mapped to server-level Azure AD logins. To create an Azure AD user from an Azure AD login use the following syntax:
CREATE USER [AAD_principal] FROM LOGIN [Azure AD login] 
Reference:
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-user-transact-sql

To include an execution plan for a query during execution 
On the SQL Server Management Studio toolbar, click Database Engine Query. You can also open an existing query and display the estimated execution plan by clicking the Open File toolbar button and locating the existing query. 
Enter the query for which you would like to display the actual execution plan. 
On the Query menu, click Include Actual Execution Plan or click the Include Actual Execution Plan toolbar button. 

    

Note: Actual execution plans are generated after the Transact-SQL queries or batches execute.
Because of this, an actual execution plan contains runtime information, such as actual resource usage metrics and runtime warnings (if any). The execution plan that is generated displays the actual query execution plan that the SQL Server Database Engine used to execute the queries. 
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/performance/display-an-actual-execution-plan