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
workloadcomparesolutionarchitecture

Where should I set up DEA?

In the above environment architecture, if feasible it is recommended to install DEA on the same machine as Distributed Replay controller. This will avoid cross machine calls and simplify configuration.

Configuration requirement for workload comparison using DEA

DEA connects to database servers using Windows authentication. Ensure that user running DEA can connect to database servers (source/target/analysis) using Windows authentication.

Capture: Learn More

  • User running DEA can connect to source database server using Windows authentication.
  • User running DEA has sysadmin privilege on the source database server.
  • Service account running source database server has write access to the trace folder path.

Replay: Learn More

  • User running DEA can connect to target database server using Windows authentication.
  • User running DEA has sysadmin privilege on the target database server.
  • Service account running target database servers has write access to the trace folder path.
  • Service account running Distributed Replay clients can connect to target database server using Windows authentication.
  • DEA communicates with Distributed Replay controller using COM interfaces. Ensure that TCP ports are opened for incoming requests on the distributed replay controller.

Analysis: Learn More

  • User running DEA can connect to analysis database server using Windows authentication.
  • User running DEA has sysadmin privilege on the source database server.
Comments (0)

Skip to main content