Merge pull request #26518 from rwestMSFT/rw-0323-typo-ad-hoc

[BULK] Fix common typos (ad-hoc)

Author: Stacyrch140

azure-sql/database/connect-query-ssms.md

@@ -44,7 +44,7 @@ Completing this quickstart requires the following items:
   > [!IMPORTANT]
   > The scripts in this article are written to use the Adventure Works database. With a managed instance, you must either import the Adventure Works database into an instance database or modify the scripts in this article to use the Wide World Importers database.
 
-If you simply want to run some ad-hoc queries without installing SSMS, use [the Azure portal's query editor to query a database in Azure SQL Database](query-editor.md).
+If you simply want to run some ad hoc queries without installing SSMS, use [the Azure portal's query editor to query a database in Azure SQL Database](query-editor.md).
 
 ## Get server connection information
 

azure-sql/database/security-best-practice.md

@@ -374,7 +374,7 @@ Separation of Duties is not limited to the data in a database, but includes appl
 
 - Make sure the person conducting the review is an individual other than the originating code author and knowledgeable in code-reviews and secure coding.
 
-- Be sure to know all sources of code-changes. Code can be in T-SQL Scripts. It can be ad-hoc commands to be executed or be deployed in forms of Views, Functions, Triggers, and Stored Procedures. It can be part of SQL Agent Job definitions (Steps). It can also be executed from within SSIS packages, Azure Data Factory, and other services.
+- Be sure to know all sources of code-changes. Code can be in T-SQL Scripts. It can be ad hoc commands to be executed or be deployed in forms of Views, Functions, Triggers, and Stored Procedures. It can be part of SQL Agent Job definitions (Steps). It can also be executed from within SSIS packages, Azure Data Factory, and other services.
 
 ## Data protection
 
@@ -487,7 +487,7 @@ Another technique for preventing unauthorized users from viewing data is to obfu
 > [!NOTE]  
 > Dynamic Data Masking cannot be used to protect data from high-privilege users. Masking policies do not apply to users with administrative access like db_owner.
 
-- Don't permit app users to run ad-hoc queries (as they may be able to work around Dynamic Data Masking).  
+- Don't permit app users to run ad hoc queries (as they may be able to work around Dynamic Data Masking).  
   - See the article, [Bypassing masking using inference or brute-force techniques](/sql/relational-databases/security/dynamic-data-masking#security-note-bypassing-masking-using-inference-or-brute-force-techniques) for details.
 
 - Use a proper access control policy (via SQL permissions, roles, RLS) to limit user permissions to make updates in the masked columns. Creating a mask on a column doesn't prevent updates to that column. Users that receive masked data when querying the masked column, can update the data if they have write-permissions.

azure-sql/managed-instance/data-virtualization-overview.md

@@ -21,7 +21,7 @@ The data virtualization feature of Azure SQL Managed Instance allows you to exec
 
 Data virtualization provides two ways of querying files intended for different sets of scenarios:
 
-- [OPENROWSET syntax](#query-data-sources-using-openrowset) – optimized for ad-hoc querying of files. Typically used to quickly explore the content and the structure of a new set of files.
+- [OPENROWSET syntax](#query-data-sources-using-openrowset) – optimized for ad hoc querying of files. Typically used to quickly explore the content and the structure of a new set of files.
 - [CREATE EXTERNAL TABLE syntax](#external-tables) – optimized for repetitive querying of files using identical syntax as if data were stored locally in the database. External tables require several preparation steps compared to the OPENROWSET syntax, but allow for more control over data access. External tables are typically used for analytical workloads and reporting.
 
 In either case, an [external data source](#external-data-source) must be created using the [CREATE EXTERNAL DATA SOURCE](/sql/t-sql/statements/create-external-data-source-transact-sql?view=azuresqldb-mi-current&preserve-view=true) T-SQL syntax, as demonstrated below.
@@ -144,7 +144,7 @@ WITH (
 
 ## Query data sources using OPENROWSET
 
-The [OPENROWSET](/sql/t-sql/functions/openrowset-transact-sql) syntax enables instant ad-hoc querying while only creating the minimal number of database objects necessary.
+The [OPENROWSET](/sql/t-sql/functions/openrowset-transact-sql) syntax enables instant ad hoc querying while only creating the minimal number of database objects necessary.
 
 `OPENROWSET` only requires creating the external data source (and possibly the credential) as opposed to the external table approach, which requires an [external file format](/sql/t-sql/statements/create-external-file-format-transact-sql?view=azuresqldb-mi-current&preserve-view=true) and the [external table]](/sql/t-sql/statements/create-external-table-transact-sql?view=azuresqldb-mi-current&preserve-view=true) itself.
 

azure-sql/migration-guides/database/db2-to-sql-database-guide.md

@@ -74,7 +74,7 @@ Validate the default data type mappings, and change them based on requirements i
 
 To convert the schema, follow these steps:
 
-1. (Optional) Add dynamic or ad-hoc queries to statements. Right-click the node, and then choose **Add statements**. 
+1. (Optional) Add dynamic or ad hoc queries to statements. Right-click the node, and then choose **Add statements**. 
 1. Select **Connect to Azure SQL Database**. 
     1. Enter connection details to connect your database in Azure SQL Database.
     1. Choose your target SQL Database from the drop-down list, or provide a new name, in which case a database will be created on the target server. 

azure-sql/migration-guides/database/oracle-to-sql-database-guide.md

@@ -77,7 +77,7 @@ Validate the default data type mappings and change them based on requirements if
 
 To convert the schema:
 
-1. (Optional) Add dynamic or ad-hoc queries to statements. Right-click the node, and then select **Add statements**.
+1. (Optional) Add dynamic or ad hoc queries to statements. Right-click the node, and then select **Add statements**.
 1. Select the **Connect to Azure SQL Database** tab.
     1. In **SQL Database**, enter connection details to connect your database.
     1. Select your target SQL Database instance from the drop-down list, or enter a new name, in which case a database will be created on the target server.

azure-sql/migration-guides/managed-instance/db2-to-managed-instance-guide.md

@@ -74,7 +74,7 @@ Validate the default data type mappings, and change them based on requirements i
 
 To convert the schema, follow these steps:
 
-1. (Optional) Add dynamic or ad-hoc queries to statements. Right-click the node, and then choose **Add statements**. 
+1. (Optional) Add dynamic or ad hoc queries to statements. Right-click the node, and then choose **Add statements**. 
 1. Select **Connect to Azure SQL Managed Instance**. 
     1. Enter connection details to connect to Azure SQL Managed Instance. 
     1. Choose your target database from the drop-down list, or provide a new name, in which case a database will be created on the target server. 

azure-sql/migration-guides/managed-instance/oracle-to-managed-instance-guide.md

@@ -75,7 +75,7 @@ Validate the default data type mappings and change them based on requirements if
 
 To convert the schema:
 
-1. (Optional) Add dynamic or ad-hoc queries to statements. Right-click the node, and then select **Add statements**.
+1. (Optional) Add dynamic or ad hoc queries to statements. Right-click the node, and then select **Add statements**.
 1. Select the **Connect to Azure SQL Managed Instance** tab.
     1. Enter connection details to connect your database in **SQL Database Managed Instance**.
     1. Select your target database from the drop-down list, or enter a new name, in which case a database will be created on the target server.

azure-sql/migration-guides/modernization.md

@@ -90,7 +90,7 @@ Whenever a Platform-as-a-Service (PaaS) solution doesn't fit your workload, Azur
 
 #### Scenario 5: Meeting regulatory compliance: How does Azure SQL help meet regulatory compliance requirements?
 
-[Azure Policy](/azure/governance/policy/overview) has built-in policies that help organizations meet regulatory compliance. Ad-hoc and customized policies can also be created. For more information, see [Azure Policy Regulatory Compliance controls for Azure SQL Database and SQL Managed Instance](../database/security-controls-policy.md). For an overview of compliance offerings, you can consult [Azure compliance documentation](/azure/compliance/).
+[Azure Policy](/azure/governance/policy/overview) has built-in policies that help organizations meet regulatory compliance. Ad hoc and customized policies can also be created. For more information, see [Azure Policy Regulatory Compliance controls for Azure SQL Database and SQL Managed Instance](../database/security-controls-policy.md). For an overview of compliance offerings, you can consult [Azure compliance documentation](/azure/compliance/).
 
 ### Getting started, the holistic approach
 

azure-sql/migration-guides/virtual-machines/oracle-to-sql-on-azure-vm-guide.md

@@ -135,7 +135,7 @@ Validate the default data type mappings and change them based on requirements, i
 
 To convert the schema, follow these steps:
 
-1. (Optional) To convert dynamic or ad-hoc queries, right-click the node and select **Add statement**.
+1. (Optional) To convert dynamic or ad hoc queries, right-click the node and select **Add statement**.
 
 1. Select **Connect to SQL Server** in the top menu.
      1. Enter connection details for your SQL Server on Azure VM.

azure-sql/toc.yml

@@ -583,7 +583,7 @@
       href: database/cost-management.md      
     - name: Connect and query
       items:
-      - name: Connect and run ad-hoc queries
+      - name: Connect and run ad hoc queries
         items:
         - name: Azure Data Studio
           href: /sql/azure-data-studio/quickstart-sql-database
@@ -877,7 +877,7 @@
             href: database/saas-multitenantdb-provision-and-catalog.md
           - name: Monitor database performance
             href: database/saas-multitenantdb-performance-monitoring.md
-          - name: Run ad-hoc queries
+          - name: Run ad hoc queries
             href: database/saas-multitenantdb-adhoc-reporting.md
           - name: Manage tenant schema
             href: database/saas-multitenantdb-schema-management.md