DEA 2.0: Telemetry and Local Audit for Database Experimentation Assistant

Database Experimentation Assistant contains an internet-enabled feature that can send telemetry information back to Microsoft. The same information is saved on your computer for Local Audit so that you can always see what information is being collected. All log files from DEA are saved in %temp%\DEA. In addition, you can decide which events get collected,…


DEA 2.0: How to Use Database Experimentation Assistant

The Database Experimentation Assistant (DEA) is a new A/B testing solution for changes in SQL Server environments (e.g. upgrade, new indexes, etc.). It assists in evaluating how the workload on your source server (current environment) will perform against your new environment. It guides you through performing an A/B test through three steps: capture, replay, and…


DEA 2.0: Analysis FAQ  

 What security permissions do I need to generate and view an analysis report on my server? The current logged in user in DEA should have sysadmin privilege to the analysis server.  If the user is part of a group permission, make sure the group has sysadmin privileges as well.   Possible Errors: Explanation / Solution: “Unable to…

0

DEA 2.0: Replay FAQ

For questions regarding configuration, following the instructions provided in Configure Replay Environment. 1. What security permissions do I need to start a replay capture on my target server? The Windows user performing the trace operation in the DEA Application should have sysadmin privileges in the target SQL Server. This is needed to start a trace. The service account, under…

0

DEA 2.0 – Capture Trace FAQ

What are the events captured while running trace on a production database? The following table provides the list of events and the corresponding column data that we collect for the traces Event Name Columns Text Data (1) Binary Data (2) Database ID (3) Host Name (8) Application Name (10) Login Name (11) SPID (12) Start…

0

DEA 2.0: Updating DB Schema for Analysis Report in the Database Experimentation Assistant

New release of the Database Experimentation Assistant comes with a completely revamped analysis report. Analysis report is saved on a SQL database, and as part of the change, we have introduced a new schema for the database. You can still view the old report in the new release, but only after updating the database to match…


DEA 2.0: Solution architecture to compare workloads in the Database Experimentation Assistant

Solution architecture for comparing workloads Consider a business scenario of upgrading from SQL 2008 to SQL 2016. Below diagram shows solution architecture to compare workloads between the different versions of SQL Server using DEA and distributed replay Where should I set up DEA? In the above environment architecture, if feasible it is recommended to install DEA…

0

DEA 2.0 – Configure Replay environment

Database Experimentation Assistant utilizes the Distributed Replay tools from the SQL Server installation. We recommend doing a test run with a small trace file before doing a full fledged replay to ensure proper replay of queries. Setup a virtual network or domain Distributed replay requires usage of common accounts between machines. For this and security reasons, we recommend…

0