Remove secondary references to Database Experimentation Assistant

rwestMSFT · rwestMSFT · commit 405243af7324 · 2025-03-07T15:48:48.000-07:00
diff --git a/azure-sql/managed-instance/quickstart-content-reference-guide.md b/azure-sql/managed-instance/quickstart-content-reference-guide.md
@@ -43,7 +43,7 @@ As an alternative to manual creation of SQL Managed Instance, you can use [Power
 
 ### Migrate your databases
 
-After you create a SQL Managed Instance and configure access, you can start migrating your SQL Server databases. Migration can fail if you have some unsupported features in the source database that you want to migrate. To avoid failures and check compatibility, you can use [Data Migration Assistant (DMA)](https://www.microsoft.com/download/details.aspx?id=53595) to analyze your databases on SQL Server and find any issue that could block migration to a SQL Managed Instance, such as existence of [FileStream](/sql/relational-databases/blob/filestream-sql-server) or multiple log files. If you resolve these issues, your databases are ready to migrate to SQL Managed Instance. [Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview) is another useful tool that can record your workload on SQL Server and replay it on a SQL Managed Instance so you can determine are there going to be any performance issues if you migrate to a SQL Managed Instance.
+After you create a SQL Managed Instance and configure access, you can start migrating your SQL Server databases. Migration can fail if you have some unsupported features in the source database that you want to migrate. To avoid failures and check compatibility, you can use [Data Migration Assistant (DMA)](https://www.microsoft.com/download/details.aspx?id=53595) to analyze your databases on SQL Server and find any issue that could block migration to a SQL Managed Instance, such as existence of [FileStream](/sql/relational-databases/blob/filestream-sql-server) or multiple log files. If you resolve these issues, your databases are ready to migrate to SQL Managed Instance.
 
 Once you are sure that you can migrate your database to a SQL Managed Instance, you can use the native SQL Server restore capabilities to restore a database into a SQL Managed Instance from a `.bak` file. You can use this method to migrate databases from SQL Server database engine installed on-premises or Azure Virtual Machines. For a quickstart, see [Restore from backup to a SQL Managed Instance](restore-sample-database-quickstart.md). In this quickstart, you restore from a `.bak` file stored in Azure Blob storage using the `RESTORE` Transact-SQL command.
 
diff --git a/azure-sql/migration-guides/database/access-to-sql-database-guide.md b/azure-sql/migration-guides/database/access-to-sql-database-guide.md
@@ -182,6 +182,3 @@ The Data SQL Engineering team developed these resources. This team's core charte
    -  [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
    -  [Best practices for costing and sizing workloads for migration to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs) 
    -  [Cloud Migration Resources](https://azure.microsoft.com/migration/resources)
-
-
-- For information about how to perform Data Access Layer A/B testing, see [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview).
diff --git a/azure-sql/migration-guides/database/db2-to-sql-database-guide.md b/azure-sql/migration-guides/database/db2-to-sql-database-guide.md
@@ -170,5 +170,3 @@ The Data SQL Engineering team developed these resources. This team's core charte
    -  [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
    -  [Best practices for costing and sizing workloads migrated to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
    -  [Cloud Migration Resources](https://azure.microsoft.com/migration/resources) 
-
-- For details on how to perform data access layer A/B testing, see [Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview).
diff --git a/azure-sql/migration-guides/database/sap-ase-to-sql-database.md b/azure-sql/migration-guides/database/sap-ase-to-sql-database.md
@@ -120,5 +120,3 @@ For more information about these issues and the steps to mitigate them, see the
    -  [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
    -  [Best practices for costing and sizing workloads for migration to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs) 
    -  [Cloud Migration Resources](https://azure.microsoft.com/migration/resources)
-
-- For details on how to perform Data Access Layer A/B testing see [Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview).
diff --git a/azure-sql/migration-guides/managed-instance/db2-to-managed-instance-guide.md b/azure-sql/migration-guides/managed-instance/db2-to-managed-instance-guide.md
@@ -169,5 +169,3 @@ The Data SQL Engineering team developed these resources. This team's core charte
 - To learn more about the framework and adoption cycle for cloud migrations, see:
    -  [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
    -  [Best practices for costing and sizing workloads migrated to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs) 
-
-- For details on how to perform data access layer A/B testing, see [Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview).
diff --git a/azure-sql/migration-guides/virtual-machines/oracle-to-sql-on-azure-vm-guide.md b/azure-sql/migration-guides/virtual-machines/oracle-to-sql-on-azure-vm-guide.md
@@ -348,4 +348,3 @@ The Data SQL Engineering team developed these resources. This team's core charte
   - [Get free extended support for SQL Server](../../virtual-machines/windows/sql-server-extend-end-of-support.md)
 
 - To assess the application access layer, use [Data Access Migration Toolkit Preview](https://marketplace.visualstudio.com/items?itemName=ms-databasemigration.data-access-migration-toolkit).
-- For details on how to do data access layer A/B testing, see [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview).
diff --git a/azure-sql/virtual-machines/windows/change-sql-server-version.md b/azure-sql/virtual-machines/windows/change-sql-server-version.md
@@ -31,7 +31,6 @@ Consider the following prerequisites before upgrading your version of SQL Server
 1. You can review the following articles to help ensure a successful outcome:
 
    - [Video: Modernizing SQL Server | Pam Lahoud & Pedro Lopes | 20 Years of PASS](https://www.youtube.com/watch?v=5RPkuQHcxxs&feature=youtu.be)
-   - [Database Experimentation Assistant for AB testing](/sql/dea/database-experimentation-assistant-overview)
    - [Upgrading Databases by using the Query Tuning Assistant](/sql/relational-databases/performance/upgrade-dbcompat-using-qta)
    - [Change the Database Compatibility Level and use the Query Store](/sql/database-engine/install-windows/change-the-database-compatibility-mode-and-use-the-query-store)
 
diff --git a/data-migration/sql-server/database/assessment-rules.md b/data-migration/sql-server/database/assessment-rules.md
@@ -472,4 +472,3 @@ Review affected objects section in Azure Migrate to see all objects using `xp_cm
 - [Azure total Cost of Ownership Calculator](https://azure.microsoft.com/pricing/tco/calculator/)
 - [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
 - [Best practices for costing and sizing workloads migrate to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
-- [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview)
diff --git a/data-migration/sql-server/database/overview.md b/data-migration/sql-server/database/overview.md
@@ -186,4 +186,3 @@ The Data SQL Engineering team developed these resources. This team's core charte
 - [Azure Total Cost of Ownership Calculator](https://azure.microsoft.com/pricing/tco/calculator/)
 - [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
 - [Best practices for costing and sizing workloads migrated to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
-- [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview)
diff --git a/data-migration/sql-server/managed-instance/assessment-rules.md b/data-migration/sql-server/managed-instance/assessment-rules.md
@@ -545,4 +545,3 @@ More information: [Stored Procedure differences in Azure SQL Managed Instance](/
 - [Azure total Cost of Ownership Calculator](https://azure.microsoft.com/pricing/tco/calculator/)
 - [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
 - [Best practices for costing and sizing workloads migrate to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
-- [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview)
diff --git a/data-migration/sql-server/managed-instance/guide.md b/data-migration/sql-server/managed-instance/guide.md
@@ -191,4 +191,3 @@ Some SQL Server features are only available once the [database compatibility lev
 - [Tutorial: Migrate SQL Server to Azure SQL Managed Instance with DMS](database-migration-service.md)
 - [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
 - [Best practices for costing and sizing workloads migrate to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
-- [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview)
diff --git a/data-migration/sql-server/managed-instance/overview.md b/data-migration/sql-server/managed-instance/overview.md
@@ -231,4 +231,3 @@ The Data SQL Engineering team developed these resources. This team's core charte
 - [Azure Total Cost of Ownership Calculator](https://azure.microsoft.com/pricing/tco/calculator/)
 - [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
 - [Best practices for costing and sizing workloads migrated to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
-- [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview)
diff --git a/data-migration/sql-server/pre-migration.md b/data-migration/sql-server/pre-migration.md
@@ -199,7 +199,7 @@ For summary reporting across large estates, Data Migration Assistant assessments
 
 Typically, an application layer accesses user databases to persist and modify data. Data Migration Assistant can assess the data access layer of an application in two ways:
 
-- By using captured [extended events](/sql/relational-databases/extended-events/extended-events) or [SQL Server Profiler traces](/sql/tools/sql-server-profiler/create-a-trace-sql-server-profiler) of your user databases. You can also use the [Capture a trace in Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-capture-trace) to create a trace log that can also be used for A/B testing.
+- By using captured [extended events](/sql/relational-databases/extended-events/extended-events) or [SQL Server Profiler traces](/sql/tools/sql-server-profiler/create-a-trace-sql-server-profiler) of your user databases.
 
 During the assessment of user databases, use Data Migration Assistant to [import](/sql/dma/dma-assesssqlonprem#add-databases-and-extended-events-trace-to-assess) captured trace files.
 
diff --git a/data-migration/sql-server/virtual-machines/guide.md b/data-migration/sql-server/virtual-machines/guide.md
@@ -139,9 +139,6 @@ The test approach to database migration consists of the following activities:
 1. **Run validation tests**: Run validation tests against the source and the target, and then analyze the results.
 1. **Run performance tests**: Run performance tests against the source and target, and then analyze and compare the results.
 
-> [!TIP]  
-> Use the [Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview) to assist with evaluating the target SQL Server performance.
-
 ### Optimize
 
 The post-migration phase is crucial for reconciling any data accuracy issues, verifying completeness, and addressing potential performance issues with the workload.
@@ -163,4 +160,3 @@ For more information about these issues and the steps to mitigate them, see:
 - [Best practices for costing and sizing workloads for migration to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
 - [Change the license model for a SQL virtual machine in Azure](/azure/azure-sql/virtual-machines/windows/licensing-model-azure-hybrid-benefit-ahb-change)
 - [Extend support for SQL Server with Azure](/azure/azure-sql/virtual-machines/windows/sql-server-extend-end-of-support)
-- [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview)
diff --git a/data-migration/sql-server/virtual-machines/overview.md b/data-migration/sql-server/virtual-machines/overview.md
@@ -184,4 +184,3 @@ The Data SQL Engineering team developed these resources. This team's core charte
 - [Best practices for costing and sizing workloads migrate to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
 - [Change the license model for a SQL virtual machine in Azure](/azure/azure-sql/virtual-machines/windows/licensing-model-azure-hybrid-benefit-ahb-change)
 - [Extend support for SQL Server with Azure](/azure/azure-sql/virtual-machines/windows/sql-server-extend-end-of-support)
-- [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview)
diff --git a/docs/index.yml b/docs/index.yml
@@ -144,9 +144,6 @@ conceptualContent:
         - text: Database Migration Assistant (DMA)
           url: dma/dma-overview.md
           itemType: overview
-        - text: Database Experimentation Assistant (DEA)
-          url: dea/database-experimentation-assistant-overview.md
-          itemType: overview
         - text: SQL Server Migration Assistant (SSMA)
           url: ssma/sql-server-migration-assistant.md
           itemType: overview
diff --git a/docs/relational-databases/performance/performance-monitoring-and-tuning-tools.md b/docs/relational-databases/performance/performance-monitoring-and-tuning-tools.md
@@ -29,7 +29,6 @@ helpviewer_keywords:
 |[Built-in Functions](../../t-sql/functions/functions.md)|Built-in functions display snapshot statistics about [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] activity since the server was started; these statistics are stored in predefined [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] counters. For example, `@@CPU_BUSY` contains the amount of time the CPU has been executing [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] code; `@@CONNECTIONS` contains the number of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] connections or attempted connections; and `@@PACKET_ERRORS` contains the number of network packets occurring on [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] connections.|  
 |[DBCC statements](../../t-sql/database-console-commands/dbcc-transact-sql.md)|DBCC (Database Console Command) statements enable you to check performance statistics and the logical and physical consistency of a database.|  
 |[Database Engine Tuning Advisor (DTA)](../../relational-databases/performance/database-engine-tuning-advisor.md)|Database Engine Tuning Advisor analyzes the performance effects of [!INCLUDE [tsql](../../includes/tsql-md.md)] statements executed against databases you want to tune. Database Engine Tuning Advisor provides recommendations to add, remove, or modify indexes, indexed views, and partitioning.|  
-|[Database Experimentation Assistant (DEA)](https://www.microsoft.com/download/details.aspx?id=54090)|Database Experimentation Assistant (DEA) is a new A/B testing solution for SQL Server. You can compare two versions of the [!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)] for a given workload. When upgrading from a previous [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] versions (Starting with [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)]) to any newer version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], DEA will be able to provide comparative analysis metrics.|
 |Error Logs|The Windows Application event log provides an overall picture of events occurring on the Windows Server and Windows operating systems as a whole, as well as events in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Agent, and full-text search. It contains information about events in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] that is not available elsewhere. You can use the information in the error log to troubleshoot [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]-related problems.|  
 |[Extended Events](../../relational-databases/extended-events/extended-events.md)|Extended Events is a lightweight performance monitoring system that uses very few performance resources. Extended Events provides three graphical user interfaces (New Session Wizard, New Session and the XE Profiler) to create, modify, display, and analyze your session data.|  
 |[Execution Related Dynamic Management Views and Functions (Transact-SQL)](../../relational-databases/system-dynamic-management-views/execution-related-dynamic-management-views-and-functions-transact-sql.md)|Execution related DMVs enable you to check execution related information.|
diff --git a/docs/sql-server/end-of-support/sql-server-end-of-support-overview.md b/docs/sql-server/end-of-support/sql-server-end-of-support-overview.md
@@ -107,7 +107,6 @@ Supported version and edition upgrades:
 
 Tools:
 
-- [Database Experimentation Assistant](../../dea/database-experimentation-assistant-overview.md) can help evaluate the target version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] for a specific workload.
 - [Data Migration Assistant](../../dma/dma-overview.md) can help detect compatibility issues that can affect database functionality in your new version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)].
 - [Query Tuning Assistant](../../relational-databases/performance/upgrade-dbcompat-using-qta.md) can help to tune workloads that can experience adverse effects when upgrading the database compatibility.
 
diff --git a/docs/sql-server/migrate/guides/sql-server-to-sql-server-upgrade-guide.md b/docs/sql-server/migrate/guides/sql-server-to-sql-server-upgrade-guide.md
@@ -24,7 +24,6 @@ Learn about the supported versions and considerations for [upgrading SQL Server]
 To prepare for the migration, download and install the following items:
 
 - [Data Migration Assistant](https://www.microsoft.com/download/details.aspx?id=53595) v5.3 or later.
-- [Database Experimentation Assistant](https://www.microsoft.com/download/details.aspx?id=54090).
 
 ## Premigration
 
diff --git a/docs/sql-server/migrate/index.yml b/docs/sql-server/migrate/index.yml
@@ -21,14 +21,10 @@ landingContent:
       links:
       - text: Data Migration Assistant (DMA)
         url: ../../dma/dma-overview.md
-      - text: Database Experimentation Assistant
-        url: ../../dea/database-experimentation-assistant-overview.md
     - linkListType: download
       links:
       - text: Data Migration Assistant (DMA)
         url: https://www.microsoft.com/download/details.aspx?id=53595
-      - text: Database Experimentation Assistant
-        url: https://www.microsoft.com/download/details.aspx?id=54090
 
   - title: Non-SQL to SQL & Azure
     linkLists:
diff --git a/docs/tools/overview-sql-tools.md b/docs/tools/overview-sql-tools.md
@@ -51,7 +51,6 @@ These tools are used to migrate, configure, and provide other features for SQL d
 | Tool | Description |
 | :-- | :-- |
 | **[Configuration Manager](../tools/configuration-manager/sql-server-configuration-manager-help.md)** | Use SQL Server Configuration Manager to configure SQL Server services and configure network connectivity. Configuration Manager runs on Windows |
-| **[Database Experimentation Assistant](../dea/database-experimentation-assistant-overview.md)** | Use Database Experimentation Assistant to evaluate a targeted version of SQL for a given workload. |
 | **[Data Migration Assistant](../dma/dma-overview.md)** | The Data Migration Assistant tool helps you upgrade to a modern data platform by detecting compatibility issues that can affect database functionality in your new version of SQL Server or Azure SQL Database. |
 | **[Distributed Replay](distributed-replay/install-distributed-replay.md)** | Use the Distributed Replay feature to help you assess the impact of future SQL Server upgrades. Also use Distributed Replay to help assess the impact of hardware and operating system upgrades, and SQL Server tuning. |
 | **[ssbdiagnose](../tools/ssbdiagnose/ssbdiagnose-utility-service-broker.md)** | The ssbdiagnose utility reports issues in Service Broker conversations or the configuration of Service Broker services. |

Original file line number	Diff line number	Diff line change
`@@ -348,4 +348,3 @@ The Data SQL Engineering team developed these resources. This team's core charte`
`348`	`348`	`- [Get free extended support for SQL Server](../../virtual-machines/windows/sql-server-extend-end-of-support.md)`
`349`	`349`
`350`	`350`	`- To assess the application access layer, use [Data Access Migration Toolkit Preview](https://marketplace.visualstudio.com/items?itemName=ms-databasemigration.data-access-migration-toolkit).`
`351`		`-- For details on how to do data access layer A/B testing, see [Overview of Database Experimentation Assistant](/sql/dea/database-experimentation-assistant-overview).`