If you deploy a DAC to a managed instance of the Database Engine, information about the deployed DAC is incorporated into The SQL Server Utility the next time the Utility collection set is sent from the instance to the Utility control point. You can then view basic health information about the DACS by using the Management Studio Utility Explorer.
The SSMS Object Explorer displays basic configuration information about each DAC deployed to an instance of the Databa Se Engine, regardless of whether the instance is managed in the SQL Server Utility. Also, the database associated with a deployed DAC can is monitored using the same procedures for monitoring any database.< /c3>
There are two ways to monitor
1,Using the SQL Server Utility
the Deployed data-tier Applications Detail page in the Management Studio Utility Explorer displays a dash Board that reports the resource utilization of all DACs that has been deployed to managed instances of the Database Engin E. The top pane of the Details page lists each deployed DAC with visual indicators showing whether their utilization of CP U and file resources is outside the policies defined for the SQL Server Utility. If you select any DAC in the list view, further details is displayed in tabs in the bottom pane of the page.
after using the deployed data-tier Applications Detail page to Quickly identify any DACs that is either under-utilizing or stressing their hardware resource, you can make plans to addr ESS any problems. Multiple DACs that is not fully utilizing their current hardware resources could is consolidated to a single server, free ing some of the servers for other uses. If A DAC is stressing the resources on the IT current server, the DAC can moved to a larger server, or additional resource S can is added to the current server.
The minimum and maximum limits for resource usage is defined by application monitoring policies defined in the utilit Y Administration Details page. Database administrators can tailor the policies to match the limits established by their organizations. For example, one company might set 75% as the maximum CPU utilization for a DACS, while another company might set the maxim Um at 80%.
2,Using the DAC System views and Tables
The following views display information about Data-tier application (DAC) instances. These views is in the msdb database and is owned by the DBO schema.
- DBO.SYSDAC_INSTANCES (Transact-SQL)
- DBO.SYSDAC_INSTANCES_INTERNAL (Transact-SQL)
Reference Documentation:
Monitor Data-tier Applications
DAC Usage3:monitor Data-tier Applications