|
|
You're in the
sql server reporting services
group:SQL Reporting Services Setup
sql server reporting services:
me and I need an answer soon. I am trying to set up SQL reporting services. I want a web application to be able to call reports from the reporting server. However with the licensing information I have found so far, it seems that in order to do this every user needs their own CAL license. This can get expensive in an application with thousands of users. One of our programmers suggested buying one cal for the application and then when a user requests a report have the application impersonate the id that has a CAL to call the report. That way we have a license for the reporting for the application and everyone who uses the application can get reports without their own CAL. Do you guys think this would work? Is impersonation easy? Thanks -
So your saying this should work in an internet application.
The users log in to the application using their unique id, This ID determines what the page allows them to access. When the user requests a report, the application connects to the dtabase with the Application's ID. You said that internet applications only need a per processor liscence so this scenario should work with only enough licenses to power the reporting database? [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> All the vendors figured this out a long time ago. When you consider that > with web applications going against a database and it being best practice to > use a few logins as possible so that connection pooling works all the > database vendors quickly changed their licensing when 3 tier came about. > They have licensing for internet application where obviously you don't know > who is accessing it and intranet applications. The licenses have nothing to > do with the login user. You could have everybody use the same login in a > 10,000 person company, but that sure doesn't mean you can have a single CAL. > What matters is the end user, it doesn't matter how many boxes are between > them or what login is used. > > You didn't say whether this was an internet or intranet application. You can > do CALS, you can do per processor (I believe for internet applications you > only can do per processor). I suggest seeing if Standard will do what you > need, it is a lot cheaper. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > > "JAlexander" <JAlexander@discussions.microsoft.com> wrote in message > news:9CAB5136-40D3-41EC-AE92-927EF42F00B4@microsoft.com... > >I have tried to ask microsoft this question but they have not gotten back > >to > > me and I need an answer soon. > > > > I am trying to set up SQL reporting services. I want a web application to > > be able to call reports from the reporting server. However with the > > licensing information I have found so far, it seems that in order to do > > this > > every user needs their own CAL license. This can get expensive in an > > application with thousands of users. One of our programmers suggested > > buying > > one cal for the application and then when a user requests a report have > > the > > application impersonate the id that has a CAL to call the report. That > > way > > we have a license for the reporting for the application and everyone who > > uses > > the application can get reports without their own CAL. > > > > Do you guys think this would work? Is impersonation easy? > > > > Thanks > > - > > Joseph Alexander > >
Thanks for your help. I will check out that site.
[quoted text, click to view] "Bruce L-C [MVP]" wrote:
> The licensing for Reporting Services is the same as for SQL Server Database. > So, when thinking of reporting services just mentally put in SQL Server > Database. You need a SQL Server license for whatever box RS is running on. > If the same as the database then no additional license is needed. Otherwise > you need a SQL Server License. MS has licensing specified for an internet > scenario. I don't know what they call it. Just look for SQL Server Database > and using it for internet (versus intranet) and you should find the > licensing to use. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "JAlexander" <JAlexander@discussions.microsoft.com> wrote in message > news:E06C2CF3-F3A2-4DF2-9F40-E23E059E178C@microsoft.com... > > So your saying this should work in an internet application. > > > > The users log in to the application using their unique id, This ID > > determines what the page allows them to access. When the user requests a > > report, the application connects to the dtabase with the Application's ID. > > > > You said that internet applications only need a per processor liscence so > > this scenario should work with only enough licenses to power the reporting > > database? > > > > "Bruce L-C [MVP]" wrote: > > > >> All the vendors figured this out a long time ago. When you consider that > >> with web applications going against a database and it being best practice > >> to > >> use a few logins as possible so that connection pooling works all the > >> database vendors quickly changed their licensing when 3 tier came about. > >> They have licensing for internet application where obviously you don't > >> know > >> who is accessing it and intranet applications. The licenses have nothing > >> to > >> do with the login user. You could have everybody use the same login in a > >> 10,000 person company, but that sure doesn't mean you can have a single > >> CAL. > >> What matters is the end user, it doesn't matter how many boxes are > >> between > >> them or what login is used. > >> > >> You didn't say whether this was an internet or intranet application. You > >> can > >> do CALS, you can do per processor (I believe for internet applications > >> you > >> only can do per processor). I suggest seeing if Standard will do what you > >> need, it is a lot cheaper. > >> > >> > >> -- > >> Bruce Loehle-Conger > >> MVP SQL Server Reporting Services > >> > >> > >> "JAlexander" <JAlexander@discussions.microsoft.com> wrote in message > >> news:9CAB5136-40D3-41EC-AE92-927EF42F00B4@microsoft.com... > >> >I have tried to ask microsoft this question but they have not gotten > >> >back > >> >to > >> > me and I need an answer soon. > >> > > >> > I am trying to set up SQL reporting services. I want a web application > >> > to > >> > be able to call reports from the reporting server. However with the > >> > licensing information I have found so far, it seems that in order to do > >> > this > >> > every user needs their own CAL license. This can get expensive in an > >> > application with thousands of users. One of our programmers suggested > >> > buying > >> > one cal for the application and then when a user requests a report have > >> > the > >> > application impersonate the id that has a CAL to call the report. That > >> > way > >> > we have a license for the reporting for the application and everyone > >> > who > >> > uses > >> > the application can get reports without their own CAL. > >> > > >> > Do you guys think this would work? Is impersonation easy? > >> > > >> > Thanks > >> > - > >> > Joseph Alexander > >> > >> > >> > >
I have a question on this statement - "You need a SQL Server license
for whatever box RS is running on." I want to setup a scenario where I will have the report server or report manager setup on one box which has IIS. And the RS metadata databases I want to setup on the server which has the SQL Server license. Does that mean that the box on which I have the report server should also have SQL Server license? Thanks PTosh
All the vendors figured this out a long time ago. When you consider that
with web applications going against a database and it being best practice to use a few logins as possible so that connection pooling works all the database vendors quickly changed their licensing when 3 tier came about. They have licensing for internet application where obviously you don't know who is accessing it and intranet applications. The licenses have nothing to do with the login user. You could have everybody use the same login in a 10,000 person company, but that sure doesn't mean you can have a single CAL. What matters is the end user, it doesn't matter how many boxes are between them or what login is used. You didn't say whether this was an internet or intranet application. You can do CALS, you can do per processor (I believe for internet applications you only can do per processor). I suggest seeing if Standard will do what you need, it is a lot cheaper. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "JAlexander" <JAlexander@discussions.microsoft.com> wrote in message news:9CAB5136-40D3-41EC-AE92-927EF42F00B4@microsoft.com... >I have tried to ask microsoft this question but they have not gotten back >to > me and I need an answer soon. > > I am trying to set up SQL reporting services. I want a web application to > be able to call reports from the reporting server. However with the > licensing information I have found so far, it seems that in order to do > this > every user needs their own CAL license. This can get expensive in an > application with thousands of users. One of our programmers suggested > buying > one cal for the application and then when a user requests a report have > the > application impersonate the id that has a CAL to call the report. That > way > we have a license for the reporting for the application and everyone who > uses > the application can get reports without their own CAL. > > Do you guys think this would work? Is impersonation easy? > > Thanks > - > Joseph Alexander
The licensing for Reporting Services is the same as for SQL Server Database.
So, when thinking of reporting services just mentally put in SQL Server Database. You need a SQL Server license for whatever box RS is running on. If the same as the database then no additional license is needed. Otherwise you need a SQL Server License. MS has licensing specified for an internet scenario. I don't know what they call it. Just look for SQL Server Database and using it for internet (versus intranet) and you should find the licensing to use. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "JAlexander" <JAlexander@discussions.microsoft.com> wrote in message news:E06C2CF3-F3A2-4DF2-9F40-E23E059E178C@microsoft.com... > So your saying this should work in an internet application. > > The users log in to the application using their unique id, This ID > determines what the page allows them to access. When the user requests a > report, the application connects to the dtabase with the Application's ID. > > You said that internet applications only need a per processor liscence so > this scenario should work with only enough licenses to power the reporting > database? > > "Bruce L-C [MVP]" wrote: > >> All the vendors figured this out a long time ago. When you consider that >> with web applications going against a database and it being best practice >> to >> use a few logins as possible so that connection pooling works all the >> database vendors quickly changed their licensing when 3 tier came about. >> They have licensing for internet application where obviously you don't >> know >> who is accessing it and intranet applications. The licenses have nothing >> to >> do with the login user. You could have everybody use the same login in a >> 10,000 person company, but that sure doesn't mean you can have a single >> CAL. >> What matters is the end user, it doesn't matter how many boxes are >> between >> them or what login is used. >> >> You didn't say whether this was an internet or intranet application. You >> can >> do CALS, you can do per processor (I believe for internet applications >> you >> only can do per processor). I suggest seeing if Standard will do what you >> need, it is a lot cheaper. >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> >> "JAlexander" <JAlexander@discussions.microsoft.com> wrote in message >> news:9CAB5136-40D3-41EC-AE92-927EF42F00B4@microsoft.com... >> >I have tried to ask microsoft this question but they have not gotten >> >back >> >to >> > me and I need an answer soon. >> > >> > I am trying to set up SQL reporting services. I want a web application >> > to >> > be able to call reports from the reporting server. However with the >> > licensing information I have found so far, it seems that in order to do >> > this >> > every user needs their own CAL license. This can get expensive in an >> > application with thousands of users. One of our programmers suggested >> > buying >> > one cal for the application and then when a user requests a report have >> > the >> > application impersonate the id that has a CAL to call the report. That >> > way >> > we have a license for the reporting for the application and everyone >> > who >> > uses >> > the application can get reports without their own CAL. >> > >> > Do you guys think this would work? Is impersonation easy? >> > >> > Thanks >> > - >> > Joseph Alexander >> >> >>
Yes it does. If you have a web farm with RS on multiple IIS boxes and all of
them sharing the same RS database, you need a license for each IIS box that has RS installed on it. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "PTosh" <pooja.lohiya@gmail.com> wrote in message news:1127511072.870674.320320@f14g2000cwb.googlegroups.com... >I have a question on this statement - "You need a SQL Server license > for whatever box RS is running on." > > I want to setup a scenario where I will have the report server or > report manager setup on one box which has IIS. And the RS metadata > databases I want to setup on the server which has the SQL Server > license. Does that mean that the box on which I have the report server > should also have SQL Server license? > > Thanks > PTosh >
Hi PTosh,
the new licensing only made sense to me after I read a book on 2005.....it's simple in the end......RS is a service that comes with SQL Server......as in .. you buy SQL Server and you get RS for free.......so if you want RS on a different server to you database you must buy SQL server for that other server too.....because you are not buying RS you are buying SQL Server which has RS as a component.....but don't forget, you do not need to buy enterprise version of SQL Server to get SR...you can buy workgroup or standard and still get RS....and the price difference is very substantial..... At least, that is my understanding... Best Regards Peter
You have it correct. Another way to look at it is to consider Office. If you
buy Office, it doesn't mean you can put Excel on one computer, PowerPoint on another, Word on another and Access on a fourth. You care buying Office, regardless of which of the apps you use. SQL Server now has Analysis Services, Notification Services and Reporting Services. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Peter Nolan" <peter@peternolan.com> wrote in message news:1127600069.210401.307910@f14g2000cwb.googlegroups.com... > Hi PTosh, > the new licensing only made sense to me after I read a book on > 2005.....it's simple in the end......RS is a service that comes with > SQL Server......as in .. you buy SQL Server and you get RS for > free.......so if you want RS on a different server to you database you > must buy SQL server for that other server too.....because you are not > buying RS you are buying SQL Server which has RS as a component.....but > don't forget, you do not need to buy enterprise version of SQL Server > to get SR...you can buy workgroup or standard and still get RS....and > the price difference is very substantial..... > > At least, that is my understanding... > > Best Regards > > Peter >
[quoted text, click to view] "Bruce L-C [MVP]" wrote:
> You have it correct. Another way to look at it is to consider Office. If you > buy Office, it doesn't mean you can put Excel on one computer, PowerPoint on > another, Word on another and Access on a fourth. You care buying Office, > regardless of which of the apps you use. SQL Server now has Analysis > Services, Notification Services and Reporting Services. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Peter Nolan" <peter@peternolan.com> wrote in message > news:1127600069.210401.307910@f14g2000cwb.googlegroups.com... > > Hi PTosh, > > the new licensing only made sense to me after I read a book on > > 2005.....it's simple in the end......RS is a service that comes with > > SQL Server......as in .. you buy SQL Server and you get RS for > > free.......so if you want RS on a different server to you database you > > must buy SQL server for that other server too.....because you are not > > buying RS you are buying SQL Server which has RS as a component.....but > > don't forget, you do not need to buy enterprise version of SQL Server > > to get SR...you can buy workgroup or standard and still get RS....and > > the price difference is very substantial..... > > > > At least, that is my understanding... > > > > Best Regards > > > > Peter > > > >
Hi,
I have a front end IIS server and need to put reporting services on it. I appreciate that I need to buy a license for it but my question is this. 1. We are running SQL Clustering so I am using SQL Enterprise. Does this mean I have to buy an Enterprise license to run reporting services on the IIS server. 2. We are running in Active – pasive mode, so does that mean I only need the one license or two for boath the NLB IIS Servers. Many thanks Noel [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> You have it correct. Another way to look at it is to consider Office. If you > buy Office, it doesn't mean you can put Excel on one computer, PowerPoint on > another, Word on another and Access on a fourth. You care buying Office, > regardless of which of the apps you use. SQL Server now has Analysis > Services, Notification Services and Reporting Services. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Peter Nolan" <peter@peternolan.com> wrote in message > news:1127600069.210401.307910@f14g2000cwb.googlegroups.com... > > Hi PTosh, > > the new licensing only made sense to me after I read a book on > > 2005.....it's simple in the end......RS is a service that comes with > > SQL Server......as in .. you buy SQL Server and you get RS for > > free.......so if you want RS on a different server to you database you > > must buy SQL server for that other server too.....because you are not > > buying RS you are buying SQL Server which has RS as a component.....but > > don't forget, you do not need to buy enterprise version of SQL Server > > to get SR...you can buy workgroup or standard and still get RS....and > > the price difference is very substantial..... > > > > At least, that is my understanding... > > > > Best Regards > > > > Peter > > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |