10

I agree the documentation on this is a bit terse, but the error message on the other hand is very clear. ImpersonateCurrentUser is not supported for models attached to a SSAS instance. This is mentioned in the documentation of the ImpersonationMode Enumeration: ImpersonateCurrentUser: Not supported for tabular model databases attached to an Analysis ...


5

The easiest way is : using SSMS -- connect to instance --> reports -> standard reports --> General There are other ways as well - How to find Analysis Services Server Version ?.


5

You can try the following calculation: Openings:= CALCULATE( SUM( 'Requisition Counts'[NumberofOpeningsQT] ) , CALCULATETABLE( LASTNONBLANK( 'Requisition Counts'[SnapshotDateKEY] , 1 ) , ALL( 'Requisition Status' ) ) ) The important part is in setting the correct filter context for the ...


4

The problem in this case was that I was trying to replace an existing column also named 'Date Offset' - this was not a calculated column, but taken from the source table. Resolution was to do the deployment in 2 phases, first remove the old column, then deploy again to add the new calculated column.


4

One thing that could cause this is if you use the Name of the database instead of the ID. For example, I created a database with with the name Demo1, so the ID defaulted to the same string. Afterwards I renamed the database, but that doesn't change the ID. If your AMO script uses the name string instead of the ID string that could cause this error.


3

TL/DR: Add more Memory, reduce the size of your Model(s), and/or move either the SQL Server Services or SQL Server Analysis Services to a different server (e.g. scale out) Longer Explanation: We went through this exercise a few months back with our Tabular SSAS production server, and actually reached out to Microsoft for "formal" recommendations as our ...


2

What you are seeing is a typical example of a missing dimension relationship. Yes it has something to do with the relations in your dsv but easy to solve with dimension relationships. If you add a dimension to a measure group/cube/fact table the dimension relations are automatically generated based on the relations in the data source view, if a relation ...


2

The script block works a bit different when it comes to passing variables. You have to tell the command what the variable contains on the remote computer. As well if you want to pass the full command as a variable you will need at the type of the variable as [scriptblock]. $stop = "stop-service 'MSOLAP$TABULAR'" Invoke-Command -ComputerName $server { $...


2

Your named Pipes connections are disabled, try fixing this


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 ...


1

Generally I keep Date and Time in separate dimensions as this reduces the overall cardinality but even with your date dimension having a time element, you should not have a problem obtaining this value. The example below was written on my own system and tested in DAX Studio: DEFINE MEASURE Sales[TransactionCountPerTimePeriod] = COUNTROWS('Sales') ...


1

If a column name has brackets, you need to escape them. You can see how if you use function QUOTENAME(). SELECT QUOTENAME('[awful column name]') -- Result: [[awful column name]]] Note the extra closing brackets. You should try adding an extra pair of enclosing brackets together with an additional closing one for your column names that include brackets. ...


1

Not an answer to your exact question, but instead of translating the SQL to DAX and maintaining it in two places, you can reuse the SQL logic in your RLS implementation to materialize tables in your tabular model with the allowed (Username,BrandId) pairs, and the allowed (Username,ChannelId) pairs enumerated. So write a view and load a table in your tabular ...


1

In SSAS 2014 Tabular partitions inside a table process serially. In SSAS 2016 Tabular partitions inside a table can process in parallel. So in your version partitioning won't speed up processing if you process the whole table. However partitioning is great for use in incremental processing. If you partition by year and only 2017 rows changed then you can ...


1

In SQL Server Management Studio you can connect Object Explorer to SSAS, expand to the table, right click, choose Partitions, then click to process one or more partitions and do a Process Clear:


1

Thanks to @GregGalloway to set me to right track. I ended up with following schema: 1) I've added new mapping table [DateMap] that materialize mapping between UTC datetime (in those weird quarter-hours) to local time zone (again in quarter-hours) CREATE TABLE [dbo].[DateMap] ( -- time zone code (set as context info for given user) [TimeZoneCode] ...


1

I would study this white paper and the AsPartitionProcessing sample for ideas. Ignore that it targets Azure Analysis Services as it should work against your SSAS instance if you use that servername instead of asazure:// as the servername. It uses the Tabular Object Model (TOM).


1

The solution was to change the processing in Visual Studio (VS) from Default to Full. The issue is described in detail here: https://connect.microsoft.com/SQLServer/feedback/details/685325/processing-ssas-in-tabular-mode-not-refreshing-data (see Cathy Dumas's reply under "Posted by Microsoft on 8/25/2011 at 2:02 PM")


1

You can back up and restore SSAS Tabular 2012 databases, but you will have to adjust the security role memberships to include users in the correct domain. You can perform the backup and restore manually or through a script in Management Studio (or executed via PowerShell). You can also re-deploy an SSAS database from the SSDT project or using the SSAS ...


1

For the "Is it possible to remove old partitions from RAM?" portion of your question: Yes. The BOL entry for Process Database, Table, or Partition mentions Process Clear in the "To process one or more partitions" section. Effectively you could issue an XMLA command to Process Clear a specific partition (i.e. an old partition). Here's a method to get the ...


1

I had a similar scenario and used the following DAX query... First, to make it simple, I defined a measure to use inside the DAX so I don't have to repeat the formula. Then I used the generate to iterate on the TOPN formula: define measure TableInTabular[NameOfTheMeasure] = COUNTAX(FILTER('Stats', ISBLANK([DeactDate]) = TRUE), 1) evaluate ( addcolumns ...


1

I think i've found the problem. SSAS doesn't seem to relate data between tables if there are no measures defined. I added a simple measure like grade count and voila i have my data relationship.


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