Power BI Tutor

Informatica – PowerCenter IBM – Infosphere Information Server Oracle – Data Integrator Microsoft – SQL Server Integrated Services Talend – Talend Open Studio for Data Integration SAS – Data Integration studio SAP – BusinessObjects Data Integrator Clover ETL – CloverETL Pentaho – Pentaho Data Integration AB – Initio

Solution is to add the reports URL to local intranet. Open internet explorer as administrator and navigate to Tools –> Internet Options –> Security –> Local Intranet. Click Sites button. Add Reports URL (e.g. http://server/Reports or http://10.xx.xx.xx/Reports ) OK       OR Troubleshooting Steps: Below mentioned are the steps to resolve the above-mentioned error in SQL Server 2008 Reporting Services. 1. Click Start -> Right click Internet Explorer -> Select Run as Administrator from the drop-down list as shown in the snippet below. 2. In Internet Explorer -> Tools -> Internet Options . In the Internet Options dialog box; select Security Tab and then click on Sites button under Local Intranet as highlighted in the snippet below. 3. In Local Intranet dialog box; enter the Reports URL address as shown in the snippet below and then click Add button to add it to the websites. Click Close to exit and return to Internet Options dialog box an...

Ø   Avoid copying from remote server window to local machine, SSIS package can get corrupted. Copy the SSIS Package from shared path location to local machine.   Ø   Maintain documentation and keep it updated for Column Mapping including Data Length and Data Type for Source and Destination   Ø   Use of handshaking table between Upstream-> Datamart (MS BI) -> Downstream applications   Ø   Use of SEND MAIL NOTIFICATION TASK in SSIS Package to inform about the Data loading/ cube processing start and finish to all concerned parties   Ø   Optimize the Query/ SP run time before placing/calling it in SSIS Package to improve performance   Ø   Use of intermediary table in case of huge data loads will ensure faster load and unaffected performance of target table   Ø   Use Sequence Container with TransactionOption property set as required in order to rollback a series of task if one task fails. Also, in case you ...

CREATE TABLE #enum_job   (     Job_ID uniqueidentifier,     Last_Run_Date          INT,     Last_Run_Time          INT,     Next_Run_Date          INT,     Next_Run_Time          INT,     Next_Run_Schedule_ID   INT,     Requested_To_Run       INT,     Request_Source         INT,     Request_Source_ID      VARCHAR(100),     Running                INT,     Current_Step           INT,     Current_Retry_Attempt INT,  ...

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"