Note: If you only wish to clear the cached permissions, it doesn't matter which server (azure or on-prem) you are connecting to, independent of the connection you will be able to see all cached permissions.

Note: if it uses a cached user for this step, still continue and finish the import, after which, you will be able to change the user and empty the cache as shown in the next step

Please go to Internet Explorer, choose Internet options, choose General tab, click on Delete button

Check Cookies and website data, then choose Delete

Launch  Power BI desktop, and choose Get Data, choose server type SQL Server Analysis Services, can choose the Live Connection. Power BI will ask your to login again.

If you want to choose Power BI Desktop Import Data option, then there is an option to clear the credential in the tool.

There is an option in Power BI to change the user and clear the cached users. But it is not available with live connection, only with the import option:

Note: If you only wish to clear the cached permissions, it doesn't matter which server (azure or on-prem) you are connecting to, independent of the connection you will be able to see all cached permissions.

When you chose the "Import" option, it will give you a login window:

Note: if it uses a cached user for this step, still continue and finish the import, after which, you will be able to change the user and empty the cache as shown in the next step

After this you will be able to go to "Data source settings":

Here you will be able to see the Data sources for the current file or the Global permissions (everything that is cached).

With "clear the permissions" delete the cached permissions or With Edit permission you can change the user

Visit this web page Data providers for connecting to Azure Analysis Services, URL is https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-data-providers

At the bottom of the web page, download then install AMO.

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

using Microsoft.AnalysisServices;

using Microsoft.AnalysisServices.Tabular;

namespace AMOAzureASProcess

{

class Program

{

static void Main(string[] args)

{

try

{

Microsoft.AnalysisServices.Server s = new Microsoft.AnalysisServices.Server();

s.Connect(@"Password=something;Persist Security Info=True;User ID=someone@microsoft.com;Initial Catalog= MyDatabase;Data Source=asazure://southcentralus.asazure.windows.net/someserver");

Microsoft.AnalysisServices.Database db = s.Databases["MyDatabase"];

//process a table

Model m = db.Model;

m.Tables["DimDate"].RequestRefresh(Microsoft.AnalysisServices.Tabular.RefreshType.Full);

//process a partition

m.Tables["FactInternetSales"].Partitions["FactInternetSales"].RequestRefresh(Microsoft.AnalysisServices.Tabular.RefreshType.Full);

db.Update(UpdateOptions.ExpandFull);

m.RequestRefresh(Microsoft.AnalysisServices.Tabular.RefreshType.Calculate);

db.Update(UpdateOptions.ExpandFull);

s.Disconnect();

}

catch (Exception ex)

{

Console.WriteLine(ex.ToString());

}

Console.WriteLine("Process is successful");

Console.ReadLine();

}

}

}

Cause: Oracle .NET provider may not support the property you want to set

Solution: Switch to user the Oracle OLE DB Provider. It may support additional properties that are not available in the Oracle .NET provider

Using a native provider has performance advantage over a .NET provider.

From performance's standpoint, a native/OLE DB provider is more efficient than a .NET provider. We recommend to use an OLE DB Provider over an equivalent .NET provider.

In a support case, we find process times in SSAS went from 22 hours down to 2.5 hours using a remote cloud hosted Oracle data source simply by changing from the .NET Oracle provider to OLE DB Provider for Oracle

1. Whenever possible, use the integrated workspace. This provides the best user experience, but the limitation is that you need to have enough memory and CPU power on your development machine to host the workspace database

1. Only AAD security groups with an email address can be added
2. An email distribution list (DL) cannot be used as a security group
3. You cannot add a security group using the domain\group name format. It needs to be an email address.

When you inadvertently set SQL Server’s ‘max server memory’ to a very low value, you may experience one or more of the following symptoms:

• SQL Server cannot be started (from a tool like configuration manager) and the following message is logged in the SQL error log:
  ”An internal query can’t be executed due to inefficient memory…
• SQL instance is started, but connections would fail with an error message that reads:
  Cannot connect to <Servername>
  Additional information:
  The client was unable to establish connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server, the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider : Shared Memory Provider: Error :0 – No process is on the other end of the pipe.) (Microsoft SQL Server, Error:233)
  
  No process on the other end of the pipe.

As noted in this blog, we can try to workaround this issue by starting SQL Server with minimal configuration by adding–f  to SQL startup parameters, but in most cases this causes SQL to start in single user mode and the connection is typically grabbed by some other process other than a tool like SSMS that can be used to correct the memory setting. The solution to this scenario is to specify the app that will be allowed to connect to SQL Server by using the –m parameter as noted below:

NET START MSSQLSERVER /f /m" Microsoft SQL Server Management Studio - Query"

OR

NET START MSSQLSERVER /f /m"SQLCMD"

Additional References:

• Server memory server configuration options: https://msdn.microsoft.com/en-us/library/ms178067(v=sql.110).aspx.
• How to: Start an instance of SQL Server: https://msdn.microsoft.com/en-us/library/ms180965(v=sql.105).aspx
• Database Engine Service Startup Options https://msdn.microsoft.com/en-us/library/ms190737.aspx

Contributed by: Idit Izak (Senior Support engineer in SQL team)

This is an interesting problem. I found after installing 4 SSAS tabular instances, the 5^th instance cannot start until I lower all the instances setting of VeritipaqMemoryLimit to 5. The other configurations do not matter for instances 5 to 8, until the 9^th instance.

I am not able to start the 9^th instance with all the instances having VertiPaqMemoryLimit=5 LowMemoryLimit=5 MinimumAllocatedMemory=5. So there must be another setting that I need to tweak. As best practice, it is also necessary to change the other memory limits, so I change the HardMemoryLimit, TotalMemoryLimit, and VirtualMemoryLimit as following, then I can start the 9^th instance.

    <Memory>

        <MemoryHeapType>-1</MemoryHeapType>

        <HeapTypeForObjects>0</HeapTypeForObjects>

        <HardMemoryLimit>10</HardMemoryLimit>

        <TotalMemoryLimit>8</TotalMemoryLimit>

        <LowMemoryLimit>5</LowMemoryLimit>

        <VertiPaqMemoryLimit>5</VertiPaqMemoryLimit>

        <MidMemoryPrice>10</MidMemoryPrice>

        <HighMemoryPrice>1000</HighMemoryPrice>

        <VirtualMemoryLimit>8</VirtualMemoryLimit>

        <SessionMemoryLimit>1</SessionMemoryLimit>

        <MinimumAllocatedMemory>5</MinimumAllocatedMemory>

        <WaitCountIfHighMemory>10</WaitCountIfHighMemory>

        <DefaultPagesCountToReuse>2</DefaultPagesCountToReuse>

        <HandleIA64AlignmentFaults>0</HandleIA64AlignmentFaults>

        <PreAllocate>0</PreAllocate>

        <VertiPaqPagingPolicy>1</VertiPaqPagingPolicy>

        <PagePoolRestrictNumaNode>0</PagePoolRestrictNumaNode>

        <HeapTypeForObjectGroupCount>0</HeapTypeForObjectGroupCount>

        <UseCountersPerCPU>-1</UseCountersPerCPU>

    </Memory>

The connection timeout was exceeded.

This problem only happens if you have the build number 11.0.9167.412 of the SSAS OLE DB Provider shipped in Excel 2016 update. You can check the following files and see if the version is build 9167.

C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesX86\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll for 32-bit

C:\Program Files\Microsoft Office\root\VFS\ProgramFilesX64\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll for 64-bit

If I replace this dll from an earlier version, for example, build 11.0.9166.514, then the problem is resolved.

This is a known problem, and the dev team is investigating the cause and the fix. I expect a fix should come soon in an Excel update.

Excel 2013 does not have this problem.

[Update 6/10/2016]: The fix will be in July's Current Channel/Insider's Channel Office 365 update release.