Database Reference
In-Depth Information
a better name in my opinion). One of the biggest advantages of this shared
engine across the tools is that a model can be designed in PowerPivot, shared
across a team by saving to a SharePoint library, and then imported and opti-
mized by importing into Visual Studio.
Table 3-2 summarizes the toolsets available for databases with SQL 2012.
TABle 3-2 Toolset for databases as of SQL 2012
QuEry
LANGuAGE
TooL
ENGINE
NoTES
Analysis Services—
Multi-dimensions
OLAP
MDX
(DAX now
supported)
Still has capabilities such
as writeback, actions, and
parent-child hierarchies that
have yet to make it into tab-
ular mode. In addition, the
memory requirements are
much lower.
Analysis
Services—Tabular
xVelocity
DAX, MDX
Standalone xVelocity engine.
Performance is great as long
as workload fits in RAM, but
massive degradation when
paging starts to happen
Distinct counts are much
improved over SSAS-MD
Quicker development time
PowerPivot
Services
xVelocity
DAX, MDX
A tabular Analysis Services
instance that is also con-
nected to SharePoint
PowerPivot
xVelocity
DAX, MDX
An instance of the xVeloc-
ity engine inside Excel, with
a backup of the database
stored inside Excel. This
backup can be extracted and
restored to an SSAS tabular
instance
Column Store
Indexes
xVelocity
SQL
An instance of the xVeloc-
ity engine running as a
non-clustered index on SQL
Server. As of SQL 2012 SP1,
these are non-updateable
(they need to be rebuilt for
any changes) and can't be
clustered.
Search WWH ::




Custom Search