Hot answers tagged

3

The solution to this is fairly straightforward. Using SQL Agent Job Tokens, you can include the date and time of the backup in the filename to ensure a new file is created each tiem the job runs preventing the overwrite. Change the command in the SSAS job step to this: <Backup xmlns="schemas.microsoft.com/analysisservices/2003/engine"> <Object&...


2

I had similar problem and until we start using Azure Analysis Services, I had to find a work around with SSAS standard edition which can only allocate 16GB of memory regardless whether you're on-prem server has 64GB of memory. If you are using Enterprise Edition I suggest looking into creating partitions in the tables in your data model and only refresh ...


2

I'm somewhat surprised that your partitions are processed without you specifying "process affected objects" anywhere. Maybe you are confusing the output "partition processing operations" with the actual processing of the partitions. The logic to process partitions when updating dimensions is this. if you process update a dimension and only new members were ...


2

It sounds like you are trying to process your tabular model (which is of version >= 1200) with XMLA script (so all in all command is in XML). That kind of tabular model has to be processed with JSON command. I had the same error message and it just turned out that I was trying to refresh the newer tabular model (of version >=1200) with XMLA command. After ...


2

When you begin installation wizard via new stand-alone Installation option, you might have missed to select Perform a new installation .. option at Installation type which is first thing to select in the wizard. After this you would proceed with Product key -> License terms -> Feature selection as Tabular Or following command straight-away install ...


2

I was trying to deploy from my computer to a server on another domain The connection to SSAS to deploy always uses Windows Authentication, and always uses the account for Visual Studio. To deploy to an SSAS server in another domain (or no domain), launch SSAS with 'runas /netonly' providing the target domain credentials. This will launch Visual Studio ...


1

I highly recommend you check out Analysis Management Objects (AMO) - I use it to perform all maintenance tasks in SSAS such as creating Roles, Permissions, Databases and Models. I prefer to use C# but there are plenty of examples online of using the same classes in PowerShell. You need to make sure you use the correct classes based on the type of install ...


1

on this link: A quick overview of SSAS for DBAs you can find relevant information about SSAS that can help you to see why there are so many advantages using SSAS. You also need to manage permissions, as you mentioned Power BI, SSAS interacts very well with Power BI, in many environments I restrict the Power BI views by managing the permissions using AD and ...


1

That means that a VM with 16 CPUs will have 16 vCPUs with 1 core each. Not exactly, that means initially a Host with a CPU of 16 cores should only have 1 VM with 16 vCPUs or 2 VMs with 8 vCPUs each instead. But as the chapter 3.5.2 Allocating vCPU says: if the physical server that the various SQL Server workloads currently run on equates to 16 ...


1

Well after try a lot of things and post on microsoft forum The problem was I was trying to deploy from my computer to a server on another domain and need to use a domain account, doesn't matter if you can connect to SQL instance. I don't know why "Use services Account" didn't work.


1

I would suggest not removing it. Why do you need to remove it? If you aren't going to use it anymore, I would just remove it as a cluster resource (and any dependencies), and then disable the service on each node. No need to uninstall anything except to save a tiny amount of disk space. IMHO, anyway.


Only top voted, non community-wiki answers of a minimum length are eligible