Q: Standard or Enterprise

Hello,
Can I use my Standard SQL Server and Reporting services and run report
though our companyâ's internet site for everyone? Or does it have to be an
Enterprise version of SQL Server?
Thanks,
Jim.Are you talking internet or intranet. The licensing as far as RS is the same
as SQL Server. I.e. if everyone in your company can access your SQL Server
then they can access your RS. If you have RS on another machine you need an
additional license. There is no difference between Standard Edition and
Enterprise as far as how many can access RS. There is a difference in
functionality and if you don't need the additional functionality then
Standard Edition will work. Enterprise Edition adds web farm capability,
data driven subscriptions, etc. See this link for the differences in the
versions:
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx
http://www.microsoft.com/sql/reporting/techinfo/techoverview.mspx
Here is a licensing FAQ:
http://www.microsoft.com/sql/reporting/howtobuy/faq.mspx
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:17707232-9B95-443C-B342-95244D1045A3@.microsoft.com...
> Hello,
> Can I use my Standard SQL Server and Reporting services and run report
> though our company's internet site for everyone? Or does it have to be an
> Enterprise version of SQL Server?
> Thanks,
> Jim.
>|||Hello Bruce,
Thanks you very much for all your help. You helped me a lot now and in the
past.
I am using RS on top of Standard SQL Server in the intranet. We have enough
SQL Server licenses for this. Now I need to deploy some reports to internet
for our partners:
1. Can I do this if I meet licensing requirement for SQL Server without any
technical problem? (I assume I need to buy more licenses, correct?, before
doing that I want to make sure I can use Standard SQL Server and RS for our
Internet, please advice.)
2. We already have our web site accessing to our Standard SQL Server to
fetch data (there is no RS functionality on there at this point). Now; here
is more detail: our Standard SQL Server is in our domain, but Web Server is
actually is not in the domain but it is in its own workgroup. Our current
html internet application accesses this Standard SQL Server through ODBC.
Now, in our local network, my asp.net and RS applications work fine, if I put
my asp.net and RS application to this web sever, will it still access
Standard SQL Server without problem? I am suing standard SqlDataAdapter to
connect to database.
Please advice.
Thanks,
Jim.
"Bruce L-C [MVP]" wrote:
> Are you talking internet or intranet. The licensing as far as RS is the same
> as SQL Server. I.e. if everyone in your company can access your SQL Server
> then they can access your RS. If you have RS on another machine you need an
> additional license. There is no difference between Standard Edition and
> Enterprise as far as how many can access RS. There is a difference in
> functionality and if you don't need the additional functionality then
> Standard Edition will work. Enterprise Edition adds web farm capability,
> data driven subscriptions, etc. See this link for the differences in the
> versions:
> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx
> http://www.microsoft.com/sql/reporting/techinfo/techoverview.mspx
> Here is a licensing FAQ:
> http://www.microsoft.com/sql/reporting/howtobuy/faq.mspx
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
> news:17707232-9B95-443C-B342-95244D1045A3@.microsoft.com...
> > Hello,
> > Can I use my Standard SQL Server and Reporting services and run report
> > though our company's internet site for everyone? Or does it have to be an
> > Enterprise version of SQL Server?
> > Thanks,
> > Jim.
> >
>
>|||Let me just clarify a few things. Are you using your own front end or are
you using Report Manager? I.e. do you have your own web front end and then
are using either URL integration or web services to integrate with RS? Also,
what type of security are you using?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:C558B489-11AE-45E4-84C8-218A49C5D1B8@.microsoft.com...
> Hello Bruce,
> Thanks you very much for all your help. You helped me a lot now and in the
> past.
> I am using RS on top of Standard SQL Server in the intranet. We have
> enough
> SQL Server licenses for this. Now I need to deploy some reports to
> internet
> for our partners:
> 1. Can I do this if I meet licensing requirement for SQL Server without
> any
> technical problem? (I assume I need to buy more licenses, correct?, before
> doing that I want to make sure I can use Standard SQL Server and RS for
> our
> Internet, please advice.)
> 2. We already have our web site accessing to our Standard SQL Server to
> fetch data (there is no RS functionality on there at this point). Now;
> here
> is more detail: our Standard SQL Server is in our domain, but Web Server
> is
> actually is not in the domain but it is in its own workgroup. Our current
> html internet application accesses this Standard SQL Server through ODBC.
> Now, in our local network, my asp.net and RS applications work fine, if I
> put
> my asp.net and RS application to this web sever, will it still access
> Standard SQL Server without problem? I am suing standard SqlDataAdapter to
> connect to database.
> Please advice.
> Thanks,
> Jim.
>
> "Bruce L-C [MVP]" wrote:
>> Are you talking internet or intranet. The licensing as far as RS is the
>> same
>> as SQL Server. I.e. if everyone in your company can access your SQL
>> Server
>> then they can access your RS. If you have RS on another machine you need
>> an
>> additional license. There is no difference between Standard Edition and
>> Enterprise as far as how many can access RS. There is a difference in
>> functionality and if you don't need the additional functionality then
>> Standard Edition will work. Enterprise Edition adds web farm capability,
>> data driven subscriptions, etc. See this link for the differences in the
>> versions:
>> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx
>> http://www.microsoft.com/sql/reporting/techinfo/techoverview.mspx
>> Here is a licensing FAQ:
>> http://www.microsoft.com/sql/reporting/howtobuy/faq.mspx
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
>> news:17707232-9B95-443C-B342-95244D1045A3@.microsoft.com...
>> > Hello,
>> > Can I use my Standard SQL Server and Reporting services and run report
>> > though our company's internet site for everyone? Or does it have to be
>> > an
>> > Enterprise version of SQL Server?
>> > Thanks,
>> > Jim.
>> >
>>|||Hello Bruce,
I embedded ReportViewer into my ASP.Net application and using it as a
component. I am guessing it calls report manager, fetch data and show it
through the viewer. It works in our intranet. I am using integrated windows
authentication in our intranet. Does this answer your question? Please let me
know.
Thanks,
"Bruce L-C [MVP]" wrote:
> Let me just clarify a few things. Are you using your own front end or are
> you using Report Manager? I.e. do you have your own web front end and then
> are using either URL integration or web services to integrate with RS? Also,
> what type of security are you using?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
> news:C558B489-11AE-45E4-84C8-218A49C5D1B8@.microsoft.com...
> > Hello Bruce,
> >
> > Thanks you very much for all your help. You helped me a lot now and in the
> > past.
> >
> > I am using RS on top of Standard SQL Server in the intranet. We have
> > enough
> > SQL Server licenses for this. Now I need to deploy some reports to
> > internet
> > for our partners:
> >
> > 1. Can I do this if I meet licensing requirement for SQL Server without
> > any
> > technical problem? (I assume I need to buy more licenses, correct?, before
> > doing that I want to make sure I can use Standard SQL Server and RS for
> > our
> > Internet, please advice.)
> >
> > 2. We already have our web site accessing to our Standard SQL Server to
> > fetch data (there is no RS functionality on there at this point). Now;
> > here
> > is more detail: our Standard SQL Server is in our domain, but Web Server
> > is
> > actually is not in the domain but it is in its own workgroup. Our current
> > html internet application accesses this Standard SQL Server through ODBC.
> > Now, in our local network, my asp.net and RS applications work fine, if I
> > put
> > my asp.net and RS application to this web sever, will it still access
> > Standard SQL Server without problem? I am suing standard SqlDataAdapter to
> > connect to database.
> > Please advice.
> > Thanks,
> > Jim.
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Are you talking internet or intranet. The licensing as far as RS is the
> >> same
> >> as SQL Server. I.e. if everyone in your company can access your SQL
> >> Server
> >> then they can access your RS. If you have RS on another machine you need
> >> an
> >> additional license. There is no difference between Standard Edition and
> >> Enterprise as far as how many can access RS. There is a difference in
> >> functionality and if you don't need the additional functionality then
> >> Standard Edition will work. Enterprise Edition adds web farm capability,
> >> data driven subscriptions, etc. See this link for the differences in the
> >> versions:
> >> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx
> >>
> >> http://www.microsoft.com/sql/reporting/techinfo/techoverview.mspx
> >>
> >> Here is a licensing FAQ:
> >> http://www.microsoft.com/sql/reporting/howtobuy/faq.mspx
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
> >> news:17707232-9B95-443C-B342-95244D1045A3@.microsoft.com...
> >> > Hello,
> >> > Can I use my Standard SQL Server and Reporting services and run report
> >> > though our company's internet site for everyone? Or does it have to be
> >> > an
> >> > Enterprise version of SQL Server?
> >> > Thanks,
> >> > Jim.
> >> >
> >>
> >>
> >>
>
>|||The ReportViewer control uses URL integration. So, whether this is an issue
depends on how your internet access is setup. If you have a DMZ it could be
a problem. URL integration with the report control is really no different
than typing in the URL from the PC over on the internet. What I mean is that
the user has to have access to the RS machine. If your web server is on one
side of the DMZ and the RS is on the other, the user on the Internet will
not have access to it.
Another issue is security. How is the user on the internet going to be
validated. This is from Books On Line:
>>>>>>>>
Securing Reports for Global Access
Report Manager and HTML Viewer are not intended for extranet or Internet
deployment scenarios. To support external users of a report server
effectively, consider building a custom Web application. The application you
provide should be installed on the same computer as report server. You
should also implement Secure Sockets Layer (SSL) to encrypt transmitted
data.
Although custom authentication models are not currently supported, you can
use Windows authentication to support report server access to users that are
external to your organization. The following list provides guidelines about
supporting this scenario:
a.. Create a low-privileged domain user account with read-only
permissions. The account must have access to the computer hosting the report
server.
b.. Create role assignments that map the user account to specific items in
the report server folder hierarchy. You can limit access to read-only
operations by choosing the Browser predefined role for the role assignment.
c.. Configure data source connections to use Windows NT Integrated
Security if you want to access a data source using the security context of
the user. Alternatively, you can use stored credentials that specify a
different account. This approach is useful if you want to query the external
data source using an account that is different from the account that allows
access to the report server. For more information about these options, see
Specifying Credential and Connection Information.
If you have a small number of external users to support, you can consider
using Microsoft Passport. Passport accounts can be mapped to Windows
accounts. Mapping accounts is a manual process that must be performed by a
system administrator, so this approach is not practical if you want to
provide access to a large number of users.
>>>>>>>>>>
The other option (which I have never implemented so I am not an expert on
it) is to provide your own authentication instead of using Windows accounts.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:A832A82A-F212-4696-95F3-7A460C1CF618@.microsoft.com...
> Hello Bruce,
> I embedded ReportViewer into my ASP.Net application and using it as a
> component. I am guessing it calls report manager, fetch data and show it
> through the viewer. It works in our intranet. I am using integrated
> windows
> authentication in our intranet. Does this answer your question? Please let
> me
> know.
> Thanks,
> "Bruce L-C [MVP]" wrote:
>> Let me just clarify a few things. Are you using your own front end or are
>> you using Report Manager? I.e. do you have your own web front end and
>> then
>> are using either URL integration or web services to integrate with RS?
>> Also,
>> what type of security are you using?
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
>> news:C558B489-11AE-45E4-84C8-218A49C5D1B8@.microsoft.com...
>> > Hello Bruce,
>> >
>> > Thanks you very much for all your help. You helped me a lot now and in
>> > the
>> > past.
>> >
>> > I am using RS on top of Standard SQL Server in the intranet. We have
>> > enough
>> > SQL Server licenses for this. Now I need to deploy some reports to
>> > internet
>> > for our partners:
>> >
>> > 1. Can I do this if I meet licensing requirement for SQL Server without
>> > any
>> > technical problem? (I assume I need to buy more licenses, correct?,
>> > before
>> > doing that I want to make sure I can use Standard SQL Server and RS for
>> > our
>> > Internet, please advice.)
>> >
>> > 2. We already have our web site accessing to our Standard SQL Server to
>> > fetch data (there is no RS functionality on there at this point). Now;
>> > here
>> > is more detail: our Standard SQL Server is in our domain, but Web
>> > Server
>> > is
>> > actually is not in the domain but it is in its own workgroup. Our
>> > current
>> > html internet application accesses this Standard SQL Server through
>> > ODBC.
>> > Now, in our local network, my asp.net and RS applications work fine, if
>> > I
>> > put
>> > my asp.net and RS application to this web sever, will it still access
>> > Standard SQL Server without problem? I am suing standard SqlDataAdapter
>> > to
>> > connect to database.
>> > Please advice.
>> > Thanks,
>> > Jim.
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Are you talking internet or intranet. The licensing as far as RS is
>> >> the
>> >> same
>> >> as SQL Server. I.e. if everyone in your company can access your SQL
>> >> Server
>> >> then they can access your RS. If you have RS on another machine you
>> >> need
>> >> an
>> >> additional license. There is no difference between Standard Edition
>> >> and
>> >> Enterprise as far as how many can access RS. There is a difference in
>> >> functionality and if you don't need the additional functionality then
>> >> Standard Edition will work. Enterprise Edition adds web farm
>> >> capability,
>> >> data driven subscriptions, etc. See this link for the differences in
>> >> the
>> >> versions:
>> >> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx
>> >>
>> >> http://www.microsoft.com/sql/reporting/techinfo/techoverview.mspx
>> >>
>> >> Here is a licensing FAQ:
>> >> http://www.microsoft.com/sql/reporting/howtobuy/faq.mspx
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
>> >> news:17707232-9B95-443C-B342-95244D1045A3@.microsoft.com...
>> >> > Hello,
>> >> > Can I use my Standard SQL Server and Reporting services and run
>> >> > report
>> >> > though our company's internet site for everyone? Or does it have to
>> >> > be
>> >> > an
>> >> > Enterprise version of SQL Server?
>> >> > Thanks,
>> >> > Jim.
>> >> >
>> >>
>> >>
>> >>
>>|||Hi Bruce,
Thanks for your responses. I will be implementing your security steps, if I
install RS to DMZ machine, and point it to the database in our domain (so DB
is in the network and application and RS is in the DMZ), will that work?
Thanks,
"Bruce L-C [MVP]" wrote:
> The ReportViewer control uses URL integration. So, whether this is an issue
> depends on how your internet access is setup. If you have a DMZ it could be
> a problem. URL integration with the report control is really no different
> than typing in the URL from the PC over on the internet. What I mean is that
> the user has to have access to the RS machine. If your web server is on one
> side of the DMZ and the RS is on the other, the user on the Internet will
> not have access to it.
> Another issue is security. How is the user on the internet going to be
> validated. This is from Books On Line:
> >>>>>>>>
> Securing Reports for Global Access
> Report Manager and HTML Viewer are not intended for extranet or Internet
> deployment scenarios. To support external users of a report server
> effectively, consider building a custom Web application. The application you
> provide should be installed on the same computer as report server. You
> should also implement Secure Sockets Layer (SSL) to encrypt transmitted
> data.
> Although custom authentication models are not currently supported, you can
> use Windows authentication to support report server access to users that are
> external to your organization. The following list provides guidelines about
> supporting this scenario:
> a.. Create a low-privileged domain user account with read-only
> permissions. The account must have access to the computer hosting the report
> server.
> b.. Create role assignments that map the user account to specific items in
> the report server folder hierarchy. You can limit access to read-only
> operations by choosing the Browser predefined role for the role assignment.
> c.. Configure data source connections to use Windows NT Integrated
> Security if you want to access a data source using the security context of
> the user. Alternatively, you can use stored credentials that specify a
> different account. This approach is useful if you want to query the external
> data source using an account that is different from the account that allows
> access to the report server. For more information about these options, see
> Specifying Credential and Connection Information.
> If you have a small number of external users to support, you can consider
> using Microsoft Passport. Passport accounts can be mapped to Windows
> accounts. Mapping accounts is a manual process that must be performed by a
> system administrator, so this approach is not practical if you want to
> provide access to a large number of users.
> >>>>>>>>>>
> The other option (which I have never implemented so I am not an expert on
> it) is to provide your own authentication instead of using Windows accounts.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
>
> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
> news:A832A82A-F212-4696-95F3-7A460C1CF618@.microsoft.com...
> > Hello Bruce,
> > I embedded ReportViewer into my ASP.Net application and using it as a
> > component. I am guessing it calls report manager, fetch data and show it
> > through the viewer. It works in our intranet. I am using integrated
> > windows
> > authentication in our intranet. Does this answer your question? Please let
> > me
> > know.
> > Thanks,
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Let me just clarify a few things. Are you using your own front end or are
> >> you using Report Manager? I.e. do you have your own web front end and
> >> then
> >> are using either URL integration or web services to integrate with RS?
> >> Also,
> >> what type of security are you using?
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
> >> news:C558B489-11AE-45E4-84C8-218A49C5D1B8@.microsoft.com...
> >> > Hello Bruce,
> >> >
> >> > Thanks you very much for all your help. You helped me a lot now and in
> >> > the
> >> > past.
> >> >
> >> > I am using RS on top of Standard SQL Server in the intranet. We have
> >> > enough
> >> > SQL Server licenses for this. Now I need to deploy some reports to
> >> > internet
> >> > for our partners:
> >> >
> >> > 1. Can I do this if I meet licensing requirement for SQL Server without
> >> > any
> >> > technical problem? (I assume I need to buy more licenses, correct?,
> >> > before
> >> > doing that I want to make sure I can use Standard SQL Server and RS for
> >> > our
> >> > Internet, please advice.)
> >> >
> >> > 2. We already have our web site accessing to our Standard SQL Server to
> >> > fetch data (there is no RS functionality on there at this point). Now;
> >> > here
> >> > is more detail: our Standard SQL Server is in our domain, but Web
> >> > Server
> >> > is
> >> > actually is not in the domain but it is in its own workgroup. Our
> >> > current
> >> > html internet application accesses this Standard SQL Server through
> >> > ODBC.
> >> > Now, in our local network, my asp.net and RS applications work fine, if
> >> > I
> >> > put
> >> > my asp.net and RS application to this web sever, will it still access
> >> > Standard SQL Server without problem? I am suing standard SqlDataAdapter
> >> > to
> >> > connect to database.
> >> > Please advice.
> >> > Thanks,
> >> > Jim.
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Are you talking internet or intranet. The licensing as far as RS is
> >> >> the
> >> >> same
> >> >> as SQL Server. I.e. if everyone in your company can access your SQL
> >> >> Server
> >> >> then they can access your RS. If you have RS on another machine you
> >> >> need
> >> >> an
> >> >> additional license. There is no difference between Standard Edition
> >> >> and
> >> >> Enterprise as far as how many can access RS. There is a difference in
> >> >> functionality and if you don't need the additional functionality then
> >> >> Standard Edition will work. Enterprise Edition adds web farm
> >> >> capability,
> >> >> data driven subscriptions, etc. See this link for the differences in
> >> >> the
> >> >> versions:
> >> >> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx
> >> >>
> >> >> http://www.microsoft.com/sql/reporting/techinfo/techoverview.mspx
> >> >>
> >> >> Here is a licensing FAQ:
> >> >> http://www.microsoft.com/sql/reporting/howtobuy/faq.mspx
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
> >> >> news:17707232-9B95-443C-B342-95244D1045A3@.microsoft.com...
> >> >> > Hello,
> >> >> > Can I use my Standard SQL Server and Reporting services and run
> >> >> > report
> >> >> > though our company's internet site for everyone? Or does it have to
> >> >> > be
> >> >> > an
> >> >> > Enterprise version of SQL Server?
> >> >> > Thanks,
> >> >> > Jim.
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||That will take care of the issue with URL integration. It does not deal with
the issue of accounts. If you can give your business users a domain account
then you will be in good shape. I do not operate this way so take it with a
grain of salt. What I have done is log into the intranet via VPN. When this
occurs and you connect to RS it does not know who you are (with my VPN
connection from home, I am not logged onto a domain). When I do this I then
get prompted for a username and password. I haven't done this for awhile so
I don't know if it prompts for the domain or if I have to put in the
username like this: MyDomainName\MyUsername
Note that putting your RS in the DMZ (which means you have split RS and the
Database) requires another license. Plus, when SQL Server is being used on
the internet that affects licensing.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:D961D195-A824-44C8-9BC7-88126739FFCF@.microsoft.com...
> Hi Bruce,
> Thanks for your responses. I will be implementing your security steps, if
> I
> install RS to DMZ machine, and point it to the database in our domain (so
> DB
> is in the network and application and RS is in the DMZ), will that work?
> Thanks,
>
> "Bruce L-C [MVP]" wrote:
>> The ReportViewer control uses URL integration. So, whether this is an
>> issue
>> depends on how your internet access is setup. If you have a DMZ it could
>> be
>> a problem. URL integration with the report control is really no different
>> than typing in the URL from the PC over on the internet. What I mean is
>> that
>> the user has to have access to the RS machine. If your web server is on
>> one
>> side of the DMZ and the RS is on the other, the user on the Internet will
>> not have access to it.
>> Another issue is security. How is the user on the internet going to be
>> validated. This is from Books On Line:
>> >>>>>>>>
>> Securing Reports for Global Access
>> Report Manager and HTML Viewer are not intended for extranet or Internet
>> deployment scenarios. To support external users of a report server
>> effectively, consider building a custom Web application. The application
>> you
>> provide should be installed on the same computer as report server. You
>> should also implement Secure Sockets Layer (SSL) to encrypt transmitted
>> data.
>> Although custom authentication models are not currently supported, you
>> can
>> use Windows authentication to support report server access to users that
>> are
>> external to your organization. The following list provides guidelines
>> about
>> supporting this scenario:
>> a.. Create a low-privileged domain user account with read-only
>> permissions. The account must have access to the computer hosting the
>> report
>> server.
>> b.. Create role assignments that map the user account to specific items
>> in
>> the report server folder hierarchy. You can limit access to read-only
>> operations by choosing the Browser predefined role for the role
>> assignment.
>> c.. Configure data source connections to use Windows NT Integrated
>> Security if you want to access a data source using the security context
>> of
>> the user. Alternatively, you can use stored credentials that specify a
>> different account. This approach is useful if you want to query the
>> external
>> data source using an account that is different from the account that
>> allows
>> access to the report server. For more information about these options,
>> see
>> Specifying Credential and Connection Information.
>> If you have a small number of external users to support, you can consider
>> using Microsoft Passport. Passport accounts can be mapped to Windows
>> accounts. Mapping accounts is a manual process that must be performed by
>> a
>> system administrator, so this approach is not practical if you want to
>> provide access to a large number of users.
>> >>>>>>>>>>
>> The other option (which I have never implemented so I am not an expert on
>> it) is to provide your own authentication instead of using Windows
>> accounts.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>>
>> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
>> news:A832A82A-F212-4696-95F3-7A460C1CF618@.microsoft.com...
>> > Hello Bruce,
>> > I embedded ReportViewer into my ASP.Net application and using it as a
>> > component. I am guessing it calls report manager, fetch data and show
>> > it
>> > through the viewer. It works in our intranet. I am using integrated
>> > windows
>> > authentication in our intranet. Does this answer your question? Please
>> > let
>> > me
>> > know.
>> > Thanks,
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Let me just clarify a few things. Are you using your own front end or
>> >> are
>> >> you using Report Manager? I.e. do you have your own web front end and
>> >> then
>> >> are using either URL integration or web services to integrate with RS?
>> >> Also,
>> >> what type of security are you using?
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
>> >> news:C558B489-11AE-45E4-84C8-218A49C5D1B8@.microsoft.com...
>> >> > Hello Bruce,
>> >> >
>> >> > Thanks you very much for all your help. You helped me a lot now and
>> >> > in
>> >> > the
>> >> > past.
>> >> >
>> >> > I am using RS on top of Standard SQL Server in the intranet. We have
>> >> > enough
>> >> > SQL Server licenses for this. Now I need to deploy some reports to
>> >> > internet
>> >> > for our partners:
>> >> >
>> >> > 1. Can I do this if I meet licensing requirement for SQL Server
>> >> > without
>> >> > any
>> >> > technical problem? (I assume I need to buy more licenses, correct?,
>> >> > before
>> >> > doing that I want to make sure I can use Standard SQL Server and RS
>> >> > for
>> >> > our
>> >> > Internet, please advice.)
>> >> >
>> >> > 2. We already have our web site accessing to our Standard SQL Server
>> >> > to
>> >> > fetch data (there is no RS functionality on there at this point).
>> >> > Now;
>> >> > here
>> >> > is more detail: our Standard SQL Server is in our domain, but Web
>> >> > Server
>> >> > is
>> >> > actually is not in the domain but it is in its own workgroup. Our
>> >> > current
>> >> > html internet application accesses this Standard SQL Server through
>> >> > ODBC.
>> >> > Now, in our local network, my asp.net and RS applications work fine,
>> >> > if
>> >> > I
>> >> > put
>> >> > my asp.net and RS application to this web sever, will it still
>> >> > access
>> >> > Standard SQL Server without problem? I am suing standard
>> >> > SqlDataAdapter
>> >> > to
>> >> > connect to database.
>> >> > Please advice.
>> >> > Thanks,
>> >> > Jim.
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Are you talking internet or intranet. The licensing as far as RS is
>> >> >> the
>> >> >> same
>> >> >> as SQL Server. I.e. if everyone in your company can access your SQL
>> >> >> Server
>> >> >> then they can access your RS. If you have RS on another machine you
>> >> >> need
>> >> >> an
>> >> >> additional license. There is no difference between Standard Edition
>> >> >> and
>> >> >> Enterprise as far as how many can access RS. There is a difference
>> >> >> in
>> >> >> functionality and if you don't need the additional functionality
>> >> >> then
>> >> >> Standard Edition will work. Enterprise Edition adds web farm
>> >> >> capability,
>> >> >> data driven subscriptions, etc. See this link for the differences
>> >> >> in
>> >> >> the
>> >> >> versions:
>> >> >> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx
>> >> >>
>> >> >> http://www.microsoft.com/sql/reporting/techinfo/techoverview.mspx
>> >> >>
>> >> >> Here is a licensing FAQ:
>> >> >> http://www.microsoft.com/sql/reporting/howtobuy/faq.mspx
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
>> >> >> news:17707232-9B95-443C-B342-95244D1045A3@.microsoft.com...
>> >> >> > Hello,
>> >> >> > Can I use my Standard SQL Server and Reporting services and run
>> >> >> > report
>> >> >> > though our company's internet site for everyone? Or does it have
>> >> >> > to
>> >> >> > be
>> >> >> > an
>> >> >> > Enterprise version of SQL Server?
>> >> >> > Thanks,
>> >> >> > Jim.
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>