In the DTU Purchase Model with "Standard". Business Critical is with General Purpose in vCore Purchase Model.
Migrating a database from the DTU-based purchasing model to the vCore-based purchasing model is similar to scaling between service objectives in the Basic, Standard, and Premium service tiers, with similar duration and a minimal downtime at the end of the migration process. A database migrated to the vCore-based purchasing model can be migrated back to the DTU- based purchasing model at any time in the same fashion, with the exception of databases migrated to the Hyperscale service tier.
https://docs.microsoft.com/en-us/azure/azure-sql/database/migrate-dtu-to-vcore?view=azuresql

Explanation:
https://learn.microsoft.com/en-us/sql/relational-databases/track-changes/about-change-tracking-sql-server?view=sql-server-ver16 To track changes, change tracking must first be enabled for the database and then enabled for the tables that you want to track within that database. The table definition does not have to be changed in any way, and no triggers are created.

Azure Synapse Analytics does not support R script.
Correct solution: You use an Azure Data Factory schedule trigger to execute a pipeline that executes an Azure Databricks notebook, and then inserts the data into the data warehouse.
Reference:
https://docs.microsoft.com/en-us/azure/architecture/data-guide/technology-choices/r-developers-guide

To classify your SQL Server database:
Step 1: In SQL Server Management Studio (SSMS), connect to the SQL Server.
Step 2: In the SSMS Object Explorer, select the database [Here db1] that you would like to classify and choose Tasks > Data Discovery and Classification > Classify Data....

Step 3: The classification engine scans your database for columns containing potentially sensitive data and provides a list of recommended column classifications:


Step 4: You can change the recommended Information Type and Sensitivity Label using the drop- down boxes.

Step 5: Select columns StandardCost and ListPrice. Unselect other columns if necessary. For StandardCost and ListPrice columns select information type of Financial, and sensitivity label of Confidential.
Step 6: To apply the selected recommendations, select the Save selected recommendations button.

Step 7: To display the classified columns, select appropriate schema and corresponding table from the drop-down, then select Load Columns.

Step 8: You can also manually classify columns as an alternative, or in addition, to the recommendation-based classification:
Select Add classification in the top menu of the window.

Step 9: If you want to add classification for all the unclassified columns for a specific table in a single attempt, then select All Unclassified in the Column drop down of Add Classification page.

Step 10: To complete your classification and persistently label (tag) the database columns with the new classification metadata, select the Save button on the top menu of the window.

Reference:
https://learn.microsoft.com/en-us/sql/relational-databases/security/sql-data-discovery-and- classification