Security must be managed on the RSDS file, not on Analysis Services. Default impersonation settings used. Row security is not supported. Excel or clients other than Reporting Services cannot be used to query the model. Dynamic security or row security is All users must be Windows Choosing a DirectQuery mode required users. Creating a DirectQuery only The data warehouse must be partition configured for read access for each Power View user, with Setting the DirectQuery security defined on the data impersonation settings warehouse. Securing the data warehouse Analysis Services must impersonate the current user Managing the xVelocity engine when it connects to the data cache in SQL Server Data source. Tools The model must be a Connecting to a DirectQuery DirectQuery enabled model, enabled model using a BISM with all partitions configured to file be DirectQuery only partition, to avoid storing data in the xVelocity engine cache. Use BISM files to connect to the model, not RSDS files. The workspace database cache must be emptied. Excel or other MDX clients cannot be used to query the model. Connections from Power View to If using BISM files for Connecting to a DirectQuery Analysis Services must cross connections, configure enabled model using a BISM SharePoint farm boundaries Kerberos or make the file Reporting Services application execution account an Connecting to a DirectQuery administrator on Analysis enabled model using a RSDS Services. file
Security must be managed on the RSDS file, not on Analysis Services. Default impersonation settings used. Row security is not supported. Excel or clients other than Reporting Services cannot be used to query the model. Dynamic security or row security is required All users must be Windows users. The data warehouse must be configured for read access for each Power View user, with security defined on the data warehouse. Analysis Services must impersonate the current user when it connects to the data source. The model must be a DirectQuery enabled model, with all partitions configured to be DirectQuery only partition, to avoid storing data in the xVelocity engine cache. Use BISM files to connect to the model, not RSDS files. The workspace database cache must be emptied. Excel or other MDX clients cannot be used to query the model. Choosing a DirectQuery mode Creating a DirectQuery only partition Setting the DirectQuery impersonation settings Securing the data warehouse Managing the xVelocity engine cache in SQL Server Data Tools Connecting to a DirectQuery enabled model using a BISM file Connections from Power View to Analysis Services must cross SharePoint farm boundaries If using BISM files for connections, configure Kerberos or make the Reporting Services application execution account an administrator on Analysis Services. Connecting to a DirectQuery enabled model using a BISM file Connecting to a DirectQuery enabled model using a RSDS file