Administering and Monitoring Analysis Services - SQL Server Analysis Services 2012 Cube Development - page 266

fault values are shown in the dialog box, which can provide guidance as to
which properties have been altered.
5. Some configuration settings require restarting the SSAS instance prior to be-
ing executed. If this is the case, the Restart column will have a value of Yes .
6. Once you're happy with your changes, click on OK and restart the instance if
necessary. You can restart SSAS using the Services.msc applet from the
command line using the NET STOP / NET START commands, or directly in
SSMS by choosing the Restart option after right-clicking on the instance.
How it works...
Discussing every SSAS property would make this chapter extremely lengthy; doing
so is well beyond the scope of the topic. Instead, in this section, I will summarize the
most frequently used properties.
Often, synchronization has to copy large partition datafiles and aggregation files.
If the timeout value is exceeded, synchronization fails. Increase the value of the
<Network><Listener><ServerSendTimeout> and <Network><Listener-
><ServerReceiveTimeout> properties to allow a longer time span for copying
each file.
By default, SSAS can use a lazy thread to rebuild missing indexes and aggregations
after you process partition data. If the <OLAP><LazyProcessing><Enabled>
property is set to 0 , the lazy thread is not used for building missing indexes—you
must use an explicit processing command instead. The <OLAP><LazyProcessin-
g><MaxCPUUsage> property throttles the maximum CPU that could be used by the
lazy thread. If efficient data delivery is your topmost priority, you can exploit the Pro-
cessData option instead of ProcessFull . To build aggregations after the data is
loaded, you must set the partition's ProcessingMode property to LazyAggrega-
tions . The SSAS formula engine is single threaded, so queries that perform heavy
calculations will only use one CPU core, even on a multiCPU computer. The storage
engine is multithreaded; hence, queries that read many partitions will require many
CPU cycles. If you expect storage engine heavy queries, you should lower the CPU
usage threshold for LazyAggregations .
By default, Analysis Services records subcubes requested for every 10th query in
the query log table. If you'd like to design aggregations based on query logs, you