I'm running into a maddening problem processing a particular model in SSAS (Tabular)
I have a Fact table partitioned by date, and every hour a job setup to refresh the current partition. The majority of the time this is working fine and the partition is updated, but occasionally (maybe once or twice a day right now) it will report that the processing was successful, but when I go look at the data in a report no data from that partition is viewable. If I simply rerun the the same processing job it magically comes back.
I've had our DBA monitoring the server resources to see if we're having memory issues/contention/errors but so far haven't seen anything out of the ordinary. Wondering if anyone has ever seen something like this and what solutions come to mind.
We have recently encountered a very similar problem: fact table current partition with 0 rows after normal SSAS Tabular model processing.
What we found is that there were two jobs working simultaneously with the same table: one job loaded data (data was first deleted and then inserted) and the other processed the above-mentioned model. It is possible that processing job accessed the table exactly at the moment when data had already been deleted and had not been loaded back yet.
So I disabled processing job schedule and added a step to the loading job so that the processing started strictly after data load is completed.