September 8, 2005 at 4:32 pm
If I am installing Reporting Services on a IIS machine that doesn't have SQL Server installed, and my Reporting Services database is going to be on a SQL Server machine that has a standard edition sql, and is set up as a per processor license, then what SQL Server license do I need to purchase for the IIS box? A standard edition license with the appropriate number of processor licenses right? Now is it the number of processors on the SQL Server machine, or the IIS machine? Also when installing Reporting Services does it matter what licensing mode I select, as long as I have purchase the correct license? Or does the licensing mode need to match the licensing mode on the SQL Server machine that contains the reporting services database?
Gregory A. Larsen, MVP
September 10, 2005 at 11:45 am
It is my understanding that the licensing is based on the SQL Server that is running the report server database. IIS does not need a licence because although it is that server which is connecting to SQL it is the clients connecting through the IIS Sever that needs the licences.
To figure out which licence to get, I generally follow this rule of thumb: If you have 25 users or more on a single processor machine then go for a per processor licence, 50 users on dual processors and so on.
As for the mode selected during installation, to keep on the right side of the guys in suits at Redmond I would make sure that you select the same mode as the SQL Server.
One thing I will say though is that I have tried myself to get this sort of setup working with SQL Standard and Reporting Services Standard edition. After about 2 months of hair pulling and multiple calls to Microsoft support all over the world I was finally told that a distributed installation is only supported through the enterprise editions so now I have to have IIS on the SQL server.
Has anyone else had this problem?
September 11, 2005 at 9:23 pm
I would suggest talking to your local msft sales office re: the licensing.
My understanding about all of the add-on servers that come with MSSQL is that if they're on the same machine (as the SQL instance) then no additional license is required. As soon as you start spreading them out across servers you start incurring license costs for each server that has SQL or a MSSQL server component installed.
This site -> http://www.microsoft.com/sql/reporting/howtobuy/howtolicensers.mspx seems to support my theory on seperated machines.
Regardless of the above, I'd still be talkign with msft to see if they can help you with the best licensing option/s for your situation.
Cheers,
Steve.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply