SQL file renaming

Author: HeidiSteen

articles/search/index.yml

@@ -89,7 +89,7 @@ landingContent:
           - text: Index from Azure Blob Storage
             url: search-blob-storage-integration.md
           - text: Index from Azure SQL Database
-            url: search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md
+            url: search-how-to-index-sql-database.md
           - text: Index from Azure Cosmos DB
             url: search-howto-index-cosmosdb.md
           - text: Index any data

articles/search/media/search-howto-connecting-azure-sql-mi-to-azure-search-using-indexers/enable-public-endpoint.png renamed to articles/search/media/search-how-to-index-sql-managed-instance/enable-public-endpoint.png

@@ -72,7 +72,7 @@ By [Azure AI Search](search-what-is-azure-search.md)
 
 Extract field values from a single table or view, serialized into JSON documents, and imported into a search index as search documents. Configure change tracking to refresh the search index with the latest changes in your database.
 
-[More details](search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md)
+[More details](search-how-to-index-sql-database.md)
 
 :::image type="icon" source="media/search-data-sources-gallery/azuresqlconnectorlogo_medium.png":::
 

articles/search/media/search-howto-connecting-azure-sql-mi-to-azure-search-using-indexers/mi-connection-string.png renamed to articles/search/media/search-how-to-index-sql-managed-instance/mi-connection-string.png

@@ -26,7 +26,7 @@ There's feature parity in all Azure public, private, and sovereign clouds, but s
 
 | Category                             | Features |
 |-------------------|----------|
-| Data sources | Search indexes can accept text from any source, provided it's submitted as a JSON document. <br/><br/> [**Indexers**](search-indexer-overview.md) are a feature that automates data import from supported data sources to extract searchable content in primary data stores. Indexers handle JSON serialization for you and most support some form of change and deletion detection. You can connect to a [variety of data sources](search-data-sources-gallery.md), including [OneLake](search-how-to-index-onelake-files.md), [Azure SQL Database](search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md), [Azure Cosmos DB](search-howto-index-cosmosdb.md), or [Azure Blob storage](search-howto-indexing-azure-blob-storage.md). |
+| Data sources | Search indexes can accept text from any source, provided it's submitted as a JSON document. <br/><br/> [**Indexers**](search-indexer-overview.md) are a feature that automates data import from supported data sources to extract searchable content in primary data stores. Indexers handle JSON serialization for you and most support some form of change and deletion detection. You can connect to a [variety of data sources](search-data-sources-gallery.md), including [OneLake](search-how-to-index-onelake-files.md), [Azure SQL Database](search-how-to-index-sql-database.md), [Azure Cosmos DB](search-howto-index-cosmosdb.md), or [Azure Blob storage](search-howto-indexing-azure-blob-storage.md). |
 | Hierarchical and nested data structures | [**Complex types**](search-howto-complex-data-types.md) and collections allow you to model virtually any type of JSON structure within a search index. One-to-many and many-to-many cardinality can be expressed natively through collections, complex types, and collections of complex types.|
 | Linguistic analysis | Analyzers are components used for text processing during indexing and search operations. By default, you can use the general-purpose Standard Lucene analyzer, or override the default with a language analyzer, a custom analyzer that you configure, or another predefined analyzer that produces tokens in the format you require. <br/><br/>[**Language analyzers**](index-add-language-analyzers.md) from Lucene or Microsoft are used to intelligently handle language-specific linguistics including verb tenses, gender, irregular plural nouns (for example, 'mouse' vs. 'mice'), word decompounding, word-breaking (for languages with no spaces), and more. <br/><br/>[**Custom lexical analyzers**](index-add-custom-analyzers.md) are used for complex query forms such as phonetic matching and regular expressions.<br/><br/> |
 

articles/search/media/search-howto-connecting-azure-sql-mi-to-azure-search-using-indexers/mi-vnet.png renamed to articles/search/media/search-how-to-index-sql-managed-instance/mi-vnet.png

@@ -137,7 +137,7 @@ Indexers require a data source that specifies the type, container, and connectio
 
    + [Azure Blob Storage](search-howto-indexing-azure-blob-storage.md)
    + [Azure Cosmos DB](search-howto-index-cosmosdb.md)
-   + [Azure SQL Database](search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md)
+   + [Azure SQL Database](search-how-to-index-sql-database.md)
 
 1. If the data source is a database, such as Azure SQL or Cosmos DB, enable change tracking. Azure Storage has built-in change tracking through the `LastModified` property on every blob, file, and table. The links for the various data sources explain which change tracking methods are supported by indexers.
 
@@ -246,7 +246,7 @@ Change detection logic is built into the data platforms. How an indexer supports
 
 + Cloud database technologies provide optional change detection features in their platforms. For these data sources, change detection isn't automatic. You need to specify in the data source definition which policy is used:
 
-  + [Azure SQL (change detection)](search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md#indexing-new-changed-and-deleted-rows)
+  + [Azure SQL (change detection)](search-how-to-index-sql-database.md#indexing-new-changed-and-deleted-rows)
   + [Azure DB for MySQL (change detection)](search-howto-index-mysql.md#indexing-new-and-changed-rows)
   + [Azure Cosmos DB for NoSQL (change detection)](search-howto-index-cosmosdb.md#indexing-new-and-changed-documents)
   + [Azure Cosmos DB for MongoDB (change detection)](search-howto-index-cosmosdb-mongodb.md#indexing-new-and-changed-documents)
@@ -259,7 +259,7 @@ If you need to clear the high water mark to reindex in full, you can use [Reset
 ## Related content
 
 + [Index data from Azure Blob Storage](search-howto-indexing-azure-blob-storage.md)
-+ [Index data from Azure SQL database](search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md)
++ [Index data from Azure SQL database](search-how-to-index-sql-database.md)
 + [Index data from Azure Data Lake Storage Gen2](search-howto-index-azure-data-lake-storage.md)
 + [Index data from Azure Table Storage](search-howto-indexing-azure-tables.md)
 + [Index data from Azure Cosmos DB](search-howto-index-cosmosdb.md)

articles/search/media/search-howto-connecting-azure-sql-mi-to-azure-search-using-indexers/nsg-rule.png renamed to articles/search/media/search-how-to-index-sql-managed-instance/nsg-rule.png

@@ -295,7 +295,7 @@ If you add new content to your data source, new chunks or child documents are ad
 If you modify existing content in the data source, chunks are updated incrementally in the search index if the data source you're using supports change tracking and deletion detection. For exammple, if a word or sentence changes in a document, the chunk in the target index that contains that word or sentence is updated on the next indexer run. Other types of updates, such as changing a field type and some attributions, aren't supported for existing fields. For more information about allowed updates, see [
 Change an index schema](search-howto-reindex.md#change-an-index-schema).
 
-Some data sources like [Azure Storage](search-howto-index-changed-deleted-blobs.md) support change and deletion tracking by default, based on the timestamp. Other data sources such as [OneLake](search-how-to-index-onelake-files.md), [Azure SQL](search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md), or [Azure Cosmos DB](search-howto-index-cosmosdb.md) must be configured for change tracking.
+Some data sources like [Azure Storage](search-howto-index-changed-deleted-blobs.md) support change and deletion tracking by default, based on the timestamp. Other data sources such as [OneLake](search-how-to-index-onelake-files.md), [Azure SQL](search-how-to-index-sql-database.md), or [Azure Cosmos DB](search-howto-index-cosmosdb.md) must be configured for change tracking.
 
 ### Deleted content
 

articles/search/search-data-sources-gallery.md

@@ -30,7 +30,7 @@ This article also provides:
 
 ## Prerequisites
 
-+ An [Azure SQL database](/azure/azure-sql/database/sql-database-paas-overview) with data in a single table or view, or a [SQL Managed Instance with a public endpoint](search-howto-connecting-azure-sql-mi-to-azure-search-using-indexers.md).
++ An [Azure SQL database](/azure/azure-sql/database/sql-database-paas-overview) with data in a single table or view, or a [SQL Managed Instance with a public endpoint](search-how-to-index-sql-managed-instance.md).
 
   Use a table if your data is large or if you need [incremental indexing](#CaptureChangedRows) using SQL's native change detection capabilities.
 
@@ -501,7 +501,7 @@ No, [Always Encrypted](/sql/relational-databases/security/encryption/always-encr
 
 **Q: Can I use Azure SQL indexer with SQL databases running on IaaS VMs in Azure?**
 
-Yes. However, you need to allow your search service to connect to your database. For more information, see [Configure a connection from an Azure AI Search indexer to SQL Server on an Azure VM](search-howto-connecting-azure-sql-iaas-to-azure-search-using-indexers.md).
+Yes. However, you need to allow your search service to connect to your database. For more information, see [Configure a connection from an Azure AI Search indexer to SQL Server on an Azure VM](search-how-to-index-sql-server.md).
 
 **Q: Can I use Azure SQL indexer with SQL databases running on-premises?**