October 19, 2015 at 1:26 pm
I have worked with SSAS and cubes before, but never been on the front end of setting it up and getting it running. I have a few questions if some of you can point me in the right direction...
My understanding is that as far as licensing goes, SSAS is part of the SQL Server license. So if I install it on the same server where SQL is running, I do not need an additional license. But if I stand up a new server and put SSAS alone on it, I will need an additional license.
However, if I put it on the same server as SQL, is that going to be a problem for resources? How can I estimate the resources that it will need?
Thanks for any information you can help with.
October 19, 2015 at 1:37 pm
robert.wiglesworth (10/19/2015)
I have worked with SSAS and cubes before, but never been on the front end of setting it up and getting it running. I have a few questions if some of you can point me in the right direction...My understanding is that as far as licensing goes, SSAS is part of the SQL Server license. So if I install it on the same server where SQL is running, I do not need an additional license. But if I stand up a new server and put SSAS alone on it, I will need an additional license.
However, if I put it on the same server as SQL, is that going to be a problem for resources? How can I estimate the resources that it will need?
Thanks for any information you can help with.
As far as licensing is concerned, you are correct.
As far as resources are concerned, it's hard to tell. The first thing I would look at how much of the resources are currently being used. After that, you need to figure out how much SSAS will be used. Is the usage going to be light or heavy?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 19, 2015 at 1:40 pm
I've always had them on the same server, even large ones, and it's never been such as issue as to be worth having them on a second server. You can always change it later without too much effort.
October 19, 2015 at 1:51 pm
It is going to be used lightly. At least initially, probably for a year or two. So it sounds like putting it on the same server would be a viable solution to begin with. We could monitor resources and usage and make changes later, if needed.
Thank you for the opinions.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply