February 14, 2018 at 11:24 pm
Hi all
Firstly, apologies for the Sherlock Holmes-type reference. It is, however, accurate.
We've built a tabular cube using SSDT 2017 and deployed it on a SQL2016 Developers instance.
We can refresh it without any issues.
We also have a few multidimensional cubes on the same server.
However, every so often, with no pattern or reason that we can discern, the tabular cube will disappear from view and from the Databases section if we connect to the correct SSAS instance in SSMS.
We can redeploy it without any issues.
The server itself is as follows:-
4 CPUs
64GB Ram with 16GB for the databases, SSRS as default, SSAS (on the Tabular instance) set at 80, SSAS (on the Multidimensional instance) also set at 80.
LowMemoryLimit for both SSAS instances are set to 65.
I'm thinking it might be something to do with memory pressures on the server, but I'm not sure where to start looking.
We can ask for more RAM from our server team if we need it (it would be nice anyway, but we're realistically waiting on new SAN hardware).
Has anyone any ideas as to why it keeps disappearing?
Do tabular cubes "expire" from memory after a certain amount of time?
Any help on this would be greatly appreciated.
March 6, 2018 at 3:16 am
We've managed to solve the issue and I'll post it here for anyone who has the same problem.
We've changed model.bim properties and selected "Integrated Workspace".
This seems to have stopped the cube being deleted from the server while we're working on it and it only updates on the server when deployed.
Hope this helps someone else.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply