Power BI Tutor

You can accelerate SQL Server Analysis Services cube processing by adjusting two setting, without changing data architecture or other costly approaches . 1. Use Shared Memory protocol to optimize source data retrieval >1.5 times It’s applicable when your data warehouse database is on the same machine as Analysis Services , which is almost always the case. (There are definite reasons for adhering to this architecture: this keeps production cube intact during processing; cube refreshing is done afterwards by synchronizing or backing-and-restoring.) Go to Sql Server Configuration Manager à SQL Server Network Configuration à Protocol For MSSQLSERVER à Shared Memory protocol is enabled Force shared memory use. Change data source connection string in OLAP data source properties: add lpc:. The connection string will look like this: Data Source= lpc: ; Integrated Security=SSPI; Initial Catalog= 2.Disable Flight Recorder on machine which does data processing Go to Analaysis Service proper

Right Click in "Cube" => "Process" => "Change Settings" => "Dimension Key Errors" Active "User Custom Error Configuration" Set "Ignore Errors" for this four drop down list "Key Not Found" "Duplicated Key" "Null key converted to unknown" "Null key not allowed" The problem with keys will be ignored.

This document describes that one of the workarounds is to add ";SSPI=NTLM" or ";Integrated Security=SSPI" to the connection string. I found that doing that really helped. Here are steps how to add additional parameter to the connection string for the BIDS environment: ·          In the BIDS environment select menu item "Project" and then "Properties" ·          Select "Deployment" tab ·          Change Target/Server property value from "YourServerName" to "YourServerName;SSPI=NTLM"

Msg 10054, Level 20, State 0, Line 0 A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) Some possible causes are as below The server has been restarted, this will close the existing connections. Someone has killed the SPID that is being used. Network Failure SQL Services restarted RESOLUTION: Just hit F5 or (ALT + X) to re-run your query. SSMS will determine it is no longer connected and then prompt you to reconnect it will put you back into the same database. Otherwise reconnect to SSMS and re execute the query.

1. go to Report Manager( http://<servername>/reports/pages/Folder.aspx ) 2. Click on the Folder in which u have reports 3. U will be directed into contents tab where u will find Show Details at the right top corner 4. Click on Show Details 5. Check in the particular report and click the edit button corresponding to it 6. Go to the properties tab and click on it 7. U will find a menu on left hand side, click on Data Sources link 8. There u will find radio button selected for A share data source (by default) and a browse button. 9. Click on the browse button u will find the tree structure of the data source and the reports folder. 10. select the data source in the data source folder and select OK. by this way u will be able to point the report to the data source.

If the mixed mode authentication is enabled in SQL Server, you can log into SQL Server Management Studio with Windows Authentication, and then unlock any SQL Server user account easily. Step 1: Open SQL Server Management Studio and select Windows Authentication to login. Step 2: Go to Security -> Logins -> sa , and double click on sa account. Step 3: After sa Login Properties dialog opens, select the General page, uncheck the box besides Enforce password policy , and click OK . Step 4: Select the Status page, make sure the box besides Login is locked out is unchecked. Then the SA account can be unlocked and you can successfully connect to SQL Server with SA login.