SIMULATION
Task 10
You need to ensure that indexes are created automatically for all the databases on sql60152867. You may need to use SQL Server Management Studio and the Azure portal.
Enable Automatic tuning at the server level and turn Create Index to On.
Microsoft states that Azure SQL Database automatic tuning can create indexes automatically, verify performance improvement, and roll back changes if performance regresses. Server-level automatic tuning settings are applied to all databases on the server by default, unless a database has its own override.
Azure Portal Method --- Recommended for Simulation
Step 1: Open the SQL logical server
Sign in to the Azure portal.
Search for SQL servers.
Open:
sql60152867
Do not open only db1. The task says all databases on sql60152867, so configure this at the server level.
Step 2: Open Automatic tuning
In the SQL server left menu:
Go to Intelligent Performance.
Select Automatic tuning.
Microsoft's documented path is to open the Azure SQL server in the portal and select Automatic tuning from the menu.
Step 3: Enable automatic index creation
On the Automatic tuning page, configure:
Setting
Value
Create index
On
Drop index
Leave unchanged unless required
Force last good plan
Leave unchanged unless required
The only required setting is:
Create index = On
Do not confuse this with Drop index. The task only asks to ensure indexes are created automatically.
Step 4: Apply the setting
Select Apply or Save.
Wait for the portal confirmation.
The setting is now configured at the SQL logical server level.
Important Database Inheritance Check
This is the part people miss.
Server-level automatic tuning applies to databases that inherit from the server. Microsoft states that individual databases can override server-level automatic tuning settings. Therefore, if the simulation shows any database with custom automatic tuning settings, set that database to Inherit from server or manually set Create index = On for that database.
For each database, the correct inherited state should be:
Automatic tuning = Inherit from server
Create index = Inherited / On
If a database is set to:
Custom
Create index = Off
then the server-level setting might not affect that database. Fix it.
Database-Level T-SQL Method
Use this only if the portal is unavailable or you need to correct a specific database override.
Connect to each database and run:
ALTER DATABASE CURRENT
SET AUTOMATIC_TUNING (
CREATE_INDEX = ON
);
Microsoft documents this exact syntax for enabling the CREATE_INDEX automatic tuning option by T-SQL on an individual Azure SQL Database.
To make an individual database inherit server settings, run:
ALTER DATABASE CURRENT
SET AUTOMATIC_TUNING = INHERIT;
But this must be executed inside each database, not from master as a single server-wide T-SQL command.
Verification with T-SQL
Connect to a database and run:
SELECT
name,
desired_state_desc,
actual_state_desc
FROM sys.database_automatic_tuning_options
WHERE name = 'CREATE_INDEX';
Expected result:
name CREATE_INDEX
desired_state_desc ON or DEFAULT
actual_state_desc ON
If desired_state_desc is DEFAULT, that usually means the database is inheriting the server-level setting. The key result is:
actual_state_desc = ON
SSMS Clarification
SSMS can be used to verify or configure the setting per database using T-SQL, but it is not the best tool for the requirement as written.
Because the task says:
all the databases on sql60152867
the correct primary method is:
Azure portal > SQL server > Automatic tuning > Create index = On
Final Exam-Lab Action
Configure this:
SQL server: sql60152867
Automatic tuning
Create index: On
Apply
Then verify databases are inheriting the server setting or have CREATE_INDEX = ON.
That completes the task.
You have an on-premises Microsoft SQL Server 2022 instance named SQL1. You have an Azure subscription that contains an Azure SQL managed instance named SQLMI1. You need to configure a bidirectional disaster recovery solution between SQL1 and SQLMH. What should you include in the solution?
You have five on-premises servers that have Microsoft SQL Server 2022 Enterprise installed Each server contains multiple database that store data for web apps and are backed up by using a third-party backup solution.
You plan to migrate the databases to Azure.
You need to recommend a solution to host the databases. The solution must meet the following requirements:
* Compute and storage resources must be shared across the databases.
* Costs must be minimized.
What should you include in the recommendation?
You have an Always On availability group deployed to Azure virtual machines. The availability group contains a database named DB1 and has two nodes named SQL1 and SQL2. SQL1 is the primary replica.
You need to initiate a full backup of DB1 on SQL2.
Which statement should you run?
BACKUP DATABASE supports only copy-only full backups of databases, files, or filegroups when it's executed on secondary replicas. Copy-only backups don't impact the log chain or clear the differential bitmap.
Incorrect Answers:
A: Differential backups are not supported on secondary replicas. The software displays this error because the secondary replicas support copy-only database backups.
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/active-secondaries-backup-on-secondary-replicas-always-on-availability-groups
You are designing a streaming data solution that will ingest variable volumes of data.
You need to ensure that you can change the partition count after creation.
Which service should you use to ingest the data?
The partition count for an event hub in a dedicated Event Hubs cluster can be increased after the event hub has been created.
https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-features#partitions
Daniel Perez
16 days agoCharles Lewis
22 days agoPatricia Walker
2 months agoSandra Clark
2 months agoHarold Thomas
3 months agoDennis White
3 months agoRichard Williams
4 months agoRonald Harris
4 months agoAdam Nguyen
4 months agoBrian Young
5 months agoBrenda Davis
5 months agoJennifer Morgan
5 months agoCharles Rivera
4 months agoMaria Carter
4 months agoRebecca Edwards
5 months agoKatina
5 months agoKarl
6 months agoOmer
6 months agoLisandra
6 months agoJosephine
6 months agoSunny
7 months agoAnnett
7 months agoVeronika
7 months agoAbel
8 months agoLeonida
8 months agoTracie
8 months agoJosphine
8 months agoGlory
8 months agoRana
9 months agoSabrina
9 months agoElza
9 months agoEliseo
9 months agoBrett
10 months agoAleisha
10 months agoJavier
10 months agoHassie
10 months agoSabrina
11 months agoBulah
11 months agoAmalia
11 months agoNelida
11 months agoMauricio
12 months agoArletta
12 months agoLouvenia
1 year agoJeannine
1 year agoKip
1 year agoDaniel
1 year agoLashaunda
1 year agoParis
1 year agoBeula
2 years agoElbert
2 years agoVi
2 years agoAshlee
2 years agoMerilyn
2 years agoWendell
2 years agoKayleigh
2 years agoHannah
2 years agoLeonora
2 years agoAshlee
2 years agoKenny
2 years agoCharlene
2 years agoGussie
2 years agoFelicidad
2 years agoGeorgeanna
2 years agoDierdre
2 years agoOdette
2 years agoDulce
2 years agoVernice
2 years agoArt
2 years agoGeraldo
2 years agoLindsey
2 years agoJannette
2 years ago