1. Ensure we are on the latest the latest version of SQL server.

2. If the issue persists,

• Download the Attunity dlls from the following site based on your SQL Server/SSIS version.
  • SQLServer 2012
  • SQLServer 2014
  • SQLServer 2016 
• Place the dlls in the right location and GAC
  • We can find 4 dll in $\bin on the downloaded folder:
    • Attunity.SqlServer.CDCControlTask.dll
    • Attunity.SqlServer.CDCDesign.dll
    • Attunity.SqlServer.CDCSplit.dll
    • Attunity.SqlServer.CDCSrc.dll
• You need to replace each of them to:
  • X86 folder
  • X64 folder

• Further GAC them so that they appear on the GAC_MSIL folder

 

• After Deploying the model to SSAS 2016 instance and making changes within SQL server ([FactSalesQuota]), we could see this notification from the SSAS profiler trace :” A notification was received from an instance of SQL Server for the '[dbo].[ FactSalesQuota]' table”

• The data was changed on the SSAS as well:

• We converted the FactSalesQuota table to an in-memory table and tested the behavior. This time, we didn’t see any notification triggered from the analysis services profiler trace

• Took a profiler on the SQL and SSAS simultaneously and we see the below query getting triggered whenever there is a change in the table on SQL side profiler:

• But when we convert the table to an in-memory table. The query was not getting triggered and we are not seeing any notification back on SSAS as well.

• After more research it seems this query keeps running in suspended state all this while.

• For normal [FactSalesQuota] table (not in-memory)  we see the below:

SQL Profiler : I could see the notification query is getting triggered:

SSAS Profiler: SSAS is receiving a notification:

• Once we convert the FactSalesQuota tables as in-memory table, I still see the notification query running in suspended state.

• But after we make the change to the table, the notification query is not triggered.

No notification seen in SSAS:

• We verified this behavior with our PG Team and understood that we rely on the SQL server notification to know if and when any changes have been made to the SQL table and only then do we initiate a refresh cache.

• As per the in-memory tables in SQL server supported features documentation, event notifications are not supported: https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/unsupported-sql-server-features-for-in-memory-oltp

Conclusion:

Proactive caching with SQL server set for notification doesn't will not work for in-memory tables in SQL server. This is a limitation from the SQL side itself.

1. Open an Excel sheet, go to the Data section-> Get Data and choose from Analysis Services.
2. Enter the server name, credentials and choose the database and cube that you want and click on Next.
3. In the next page note down the File Name where the model will be saved (it will be in .odc extension) and click on Finish then Import the data.
4. Now close the Excel and go to the folder where the model is saved.
5. Open the .odc file in a notepad.
6. In the Connection String section, you will have to add a parameter called “Locale Identifier”
7. The default is 1033 which is English default (e.g.: Locale Identifier=1033)
8. You need to add the value as per your translation language in SSAS. Please the link below to know the Locale Identifier code for each language.

9. Once the Locale Identifier is set, save the file.
10. Now a new Excel file and go to the Data section.
11. Click on Existing Connection and choose the connection which you have create recently.
12. Once done import the data and you will see that the Language will show as per the SSAS translation language.

1. Go to create Data Source section.
2. You can either choose to write the connection string or you can also choose to Build the connection string.
3. You can do this for both shared Data source and embedded data source.
4. While writing a connection string, apart from data source and Initial catalog, add the parameter “Locale Identifier=1034” (For my case I have used Spanish(Spain)).
5. If you choose to build the connection string, then click on Advanced button and look for Locale Identifier parameter.
6. Set the Locale Identifier value as per your translation language in SSAS by referring the link above.
7. Once done, save the data source.
8. Now while creating the data set you will see that the Language will show as per the SSAS translation language.
9. Please note that the report must be created based on the SSAS translation and the translation cannot be changed while viewing the report.

1. We would be using a single system to develop the report using SQL Server Data Tools (SSDT) and host the report in Report Server. It means SSDT and SSRS both are installed in the same system.
2. SSDT version – Visual Studio 2017
3. SSRS – SQL Server Reporting Services 2014.

<ServerName> =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = ##.###.##.###)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = orcl)
    )
  )

E:\app\client\xxxx\product\12.2.0\client_2\odp.net\bin\2.x>oraprovcfg /action:gac /providerpath:E:\app\client\xxxx\product\12.2.0\client_2\odp.net\bin\2.x\Oracle.DataAccess.dll
E:\app\client\xxxx\product\12.2.0\client_2\odp.net\bin\4>oraprovcfg /action:gac /providerpath:E:\app\client\xxxx\product\12.2.0\client_2\odp.net\bin\4\Oracle.DataAccess.dll

The Power BI Desktop shows below error while publishing to service:

Error message:

We enabled the Power BI Desktop Tracing :

   ->     Screenshot for the enabling the Tracing in PBI Desktop :

The Error message in the Trace file found :

Look for the error stating the below :

\"httpStatusCode\":\"500\",\"exceptionType\":\"Microsoft.PowerBI.Client.Windows.PowerBIService.PowerBIServiceException\",\"errorCode\":\"ResourceLimitsPackageCountExceeded\",\"errorDetails\":\"{\\\"code\\\":\\\"ResourceLimitsPackageCountExceeded\\\",\\\"pbi.error\\\":{\\\"code\\\":\\\"ResourceLimitsPackageCountExceeded

If you see the same error in the trace, then it concludes that the workspace in which we are trying to publish the datasets has exceeded the its default limit.

The reason for the error:

The workspace allows only maximum of 200 datasets to be published with in it. This limit of 200 includes the combination of datasets and reports together. So, if you try to publish beyond this limit then you would get the above error in Power BI desktop.

We have a few workarounds to resolve this issue:

** Workaround  1:

-------------------------

-> Flush out the unwanted/unused dataset from the workspace.

** Workaround  2:

-------------------------

-> Create another workspace and use it particularly for large datasets.

** Workaround 3 :

-------------------------

-> You can also use the Get Data method to import local files into Power BI Service by keeping the PBIX files into OneDrive or any local folder or any other Power BI supportable data source locations.

Note: The Product team is aware of this limitation with in Power BI service UI and they are working to provide a resolution soon.

1. Edition: Power BI Report Server - SQL Server Enterprise with Software Assurance
2. Product Build:0.600.434
3. SSAS Version: SQL Server 2017
4. PBIRS Version: Power BI Report Server 2017 Microsoft 1.1.6514.9163 (October 2017)

1. Connect to Power Pivot instance of SSAS from SSMS.
2. Right click on it and then click on properties.

3. Select the security tab and then click on Add.

4. Provide the NT AUTHORITY\NETWORK SERVICE account and then ok.

5. Verify that, Network account is added successfully as shown below.

• To create a system DSN entry

    

• Click on Get Data from the Power BI Desktop console. Then click on Other and further click on ODBC.

• Click on Settings icon and choose the Manage gateways

• Once you have configured the data source add the gateway to your dataset and you are ready to go.

1. Install Microsoft .NET 4.6 and above on your computer (https://technet.microsoft.com/en-us/library/security/2960358.aspx).
2. Enforce TLS 1.2 on your machine through registry settings. In an elevated command prompt run the following commands:

• reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:64
• reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:32