Hi,
Seems we could not from SSAS side know which kind of client tool is connecting to SSAS, neither we could block certain client tool like QlikView form SSAS side.
- how do i see which users are running the particular tabular cube
- which tabular cube is causing this, so that i can prove my theory
For this we could use SQL Profiler to monitor the SSAS tabular server, we could know which user is access which particular tabular. SSAS Tabular Logging Methods
For the memory monitoring you could using Server Performance Monitor
I noticed today the sql dw was struggling badly and the memory for DB and SSAS Tabualr was swapped around and went to 500mb whereas the tabular service memeory was at 34gb
Depends on you tabular size, this could be a normal behavior. Since SSAS tabular and SQL Server are both resource intensive software, normally we would suggest company to install them on two machines or add more RAM to the server (if you have to had them on one machine). This way these two server would not compete for hardware resource.
Notice that tabular server is especially RAM intensive app.
At last, my personal opinion, is that the client tool probably won't affect server performance. Whether they are using Power BI or Excel or QlikView, what critical is the query they made, not the tools.
(Also QlikView for personal is free to use, I noticed that you've asked this in another thread.)
Hope this helps a bit.
Regards,
Lukas
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
What can I do if my transaction log is full?--- Hot issues November
How to convert Profiler trace into a SQL Server table -- Hot issues November