Virtual network rules are one firewall security feature that controls whether the database server for your single databases and elastic pool in Azure SQL Database or for your databases in SQL Data Warehouse accepts communications that are sent from particular subnets in virtual networks.

Server-level, not database-level: Each virtual network rule applies to your whole Azure SQL Database server, not just to one particular database on the server. In other words, virtual network rule applies at the serverlevel, not at the database-level.

Box 1: partitionBy

We should overwrite at the partition level.

Example:

df.write.partitionBy("y","m","d")

mode(SaveMode.Append)

parquet("/data/hive/warehouse/db_name.db/" + tableName)

Box 2: ("StoreID", "Year", "Month", "Day", "Hour", "StoreID")

Box 3: parquet("/Purchases")

SynapseSqlPoolExecRequests:

This log contains detailed information about queries executed in a dedicated SQL pool in Azure Synapse Analytics.

It provides metrics such as query duration, CPU time, I/O, and the status of the queries, making it the best choice for monitoring query performance.

Other options:

A. SynapseSqlPoolSqlRequests:

Logs high-level requests, such as login attempts or connection establishment. It doesn’t give detailed query execution information.

C. SynapseSqlPoolWaits:

Contains information about waits in the SQL pool, useful for troubleshooting resource contention but not suitable for directly monitoring query performance.

D. SynapseSqlPoolRequestSteps:

Provides information about the individual steps within a query plan, which is more granular and not typically used for general query performance monitoring.