https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/point-in-time- restore?view=azuresql-mi&tabs=azure-portal You can use point-in-time restore to restore a database in these scenarios:
From an existing database
From a deleted database
To the same managed instance or to a different managed instance
To a managed instance in the same subscription or to a managed instance in a different subscription

Create a CPU status alert for a SQL Server on Azure
Create a metric alert with dynamic thresholds (Create an alert when a CPU exceeds an average) Step 1: In the search bar at the top of the Azure portal, type SQL, and select SQL databases.
Select the AdventureWorksLT database name listed.[Here db1]

Step 2: On the main blade for the database, navigate down to the monitoring section. Select Alerts.

Step 3: Select Create alert rule.

Step 4: In the Select a signal slide out, select CPU percentage.

Step 5: In the Configure signal slide out, select Dynamic for the Threshold property

Step 6: Then check that the Operator property is Greater than, the Aggregation type is Average.
Select Done.
(There is no Threshold value)
Step 7: Select the Actions tab.

Step 8: In the Actions tab, select Create action group.

Step 9: On the Action Group screen, type emailgroup in the Action group name field, and then select Next: Notifications.

Step 10: On the Notifications tab, enter the following information:
Notification type: Email/SMS message/Push/Voice
Note: When you select this option, a Email/SMS message/Push/Voice flyout will appear. Check the Email property and type: [[email protected]]

Step 11: Select Review + create, then select Create.

Note: Dynamic thresholds apply advanced machine learning and use a set of algorithms and methods to:
Learn the historical behavior of metrics
Analyze metrics over time and identify patterns such as hourly, daily or weekly patterns Recognize anomalies that indicate possible service issues Calculate the most appropriate threshold for the metric When you use dynamic thresholds, you don't have to know the "right" threshold for each metric, because dynamic thresholds calculate the most appropriate thresholds for you.
Reference:
https://microsoftlearning.github.io/dp-300-database-administrator/Instructions/Labs/12-create- cpu-status-alert.html
https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-dynamic-thresholds

Explanation:
https://learn.microsoft.com/en-us/sql/relational-databases/partitions/partitioned-tables-and- indexes?view=sql-server-ver16

Explanation:
Box 1: DimEvent
Box 2: DimChannel
Dimension tables describe business entities - the things you model. Entities can include products, people, places, and concepts including time itself. The most consistent table you'll find in a star schema is a date dimension table. A dimension table contains a key column (or columns) that acts as a unique identifier, and descriptive columns.
Box 3: FactEvents
Fact tables store observations or events, and can be sales orders, stock balances, exchange rates, temperatures, etc.
Reference:
https://docs.microsoft.com/en-us/power-bi/guidance/star-schema

Explanation:
Box 1: INTERVAL_LENGTH_MINUTES
INTERVAL_LENGTH_MINUTES defines size of time window during which collected runtime statistics for query plans are aggregated and persisted. Every active query plan has at most one row for a period of time defined with this configuration.
Default: 60
Box 2: 1
Statistics Collection Interval (INTERVAL_LENGTH_MINUTES): Defines the level of granularity for the collected runtime statistic, expressed in minutes. The default is 60 minutes. Consider using a lower value if you require finer granularity or less time to detect and mitigate issues.
Use SQL Server Management Studio or Transact-SQL to set a different value for Statistics Collection Interval:
ALTER DATABASE [QueryStoreDB]
SET QUERY_STORE (INTERVAL_LENGTH_MINUTES = 60);
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/performance/best-practice-with-the- query-store