Database Reference
In-Depth Information
Using Utility dashboard from SQL Server Management studio, the SQL Server health policies
can be configured for data-tier applications and managed instances; the policies can be
defined globally or individually.
The default data collection interval is 15 minutes, which cannot be changed and the default
upper threshold processor utilization policy is 70 percent, which can be changed according
to the usage of the SQL Server instance. Also, the default evaluation period for processor
over-utilization is one hour, which can be configurable until one week based on the default
percentage of data points in violation before a CPU violation is reported as over-utilization,
which can be configurable between 0 percent and 100 percent.
In this recipe, as we set the four data points to be collected every hour, where the CPU utilization
policy threshold is 20 percent, this means in a one-hour collection period 25 percent of data
points are performed and report any violation of the CPU utilization policy threshold.
As a best practice, to reduce any noise generated by
a single or multiple violations, we can increase the
evaluation period by another increment to six hours and
the tolerance for percentage of violations by 30 percent.
Administrating multiple Analysis Services
using Tools
Administering and managing Analysis Services includes managing all instances by
maintaining optimal security, deployment, and data recovery that will process the data
warehouse objects. The SQL Server tools can help the users and help the DBAs in automating
tasks and monitoring activity within an Analysis Services instance. The service management
tools can configure the server properties using SQL Server Management Studio and MMC
snap-in makes it possible for users to configure Windows services. In this recipe, we will
go through the important aspects and processes in the administration of multiple analysis
services instances using the available tools.
Apart from sharing the same server hardware resources, every instance of SQL Server
Analysis Services is completely independent, with independent executables, properties,
security models, cubes, and so on.
How to do it...
The following are important points in administering and managing multiple instances of
Analysis Services using SQL server tools:
1.
Assume a scenario in a multiple instances of Analysis Services environment, such as:
Set up of a communication channel using own port for each instance
Search WWH ::
Custom Search