Feedback after one week of using

Hi all,
Just installed the software on Monday and I already have 2 reports in the
production. This software is so amazing, I did a little demo today at work
and everyone was shocked to see that it took me only 15 minutes to author
one simple report with no line of code! It's very easy to use, I think
coming up with the query is hard. I still think it needs some improvements,
i.e. calendar control (this is a must in any report, I don't believe they
didn't think of it when they released the software!)
I still have some questions though:
1. Since we have SQL and Web servers in the DMZ (they belong to DMZ domain),
we don't want to have users (on separate domain) log on (using DMZ domain
account - no trust allowed) to view and subscribe reports. Is there a way to
set anonymous access to default reports, except for few reports and certain
features that we want to lock out from anonymous users? This helps us a lot
with maintenance and support.
2. Can I connect to 2 or more datasources in the same report?
Thanks in advance for the help.
SQL Server Reporting Services ROCKS!Thanks for using our product.
1. Allowing both anonymous and authenticated access would require to
configure IIS to accept both anonymous and windows integrated
authentication. We found this configuration to be very confusing and asking
customers to avoid it. If you allow both, internet explorer will not know
which one to use. This will cause unstable behavior, sometimes it will try
to go as anonymous and sometimes will ask for user name and password.
One way to solve this problem is to install another report server and point
it to the same database. Then allow only anonymous access on one RS and only
integrated authentication on another. After that you can give rights to
account under which IIS runs anonymous user for some reports. Note that if
you use different boxes for this, you'll have to make this used a domain
user known to both boxes and SQL.
2. Yes, this is possible.
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"VNN" <VNN@.hotmail.com> wrote in message
news:enXXJ7lCFHA.1268@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> Just installed the software on Monday and I already have 2 reports in the
> production. This software is so amazing, I did a little demo today at work
> and everyone was shocked to see that it took me only 15 minutes to author
> one simple report with no line of code! It's very easy to use, I think
> coming up with the query is hard. I still think it needs some
improvements,
> i.e. calendar control (this is a must in any report, I don't believe they
> didn't think of it when they released the software!)
> I still have some questions though:
> 1. Since we have SQL and Web servers in the DMZ (they belong to DMZ
domain),
> we don't want to have users (on separate domain) log on (using DMZ domain
> account - no trust allowed) to view and subscribe reports. Is there a way
to
> set anonymous access to default reports, except for few reports and
certain
> features that we want to lock out from anonymous users? This helps us a
lot
> with maintenance and support.
> 2. Can I connect to 2 or more datasources in the same report?
> Thanks in advance for the help.
> SQL Server Reporting Services ROCKS!
>|||Hello Dmitry,
I can echo the comments of VNN. I am into my second week using RS,
apart from initial hiccups of installation, development has been rapid.
I am eagerly awaiting SP2 to see if they can add some features which i
feel can make my life easier.
As you mentioned multiple installations of RS pointing to same DB, I
would like to know more about this.
I am trying to deploy my reports on a remote server. But i am not sure
to use the existing RS DB on a machine in my domain or
Create a new RS db on the server.
Would like to know how to go about
1. Using the existing DB
2. Creating a new DB on the server.
In case of creating a new DB is there a way I can export all the
reports I created on my local machine to the new report server ?
What are the security/account types/auth/IIS issues I need to take care
of.
I am gonna do the installation tommorow and trying to get as much info
as possible.
Thx
Bofo|||When multiple servers are sharing the same SQL DB that is called a web farm
configuration. It is more complicated to setup and it is more expensive (you
have to have an enterprise server license). For what you are doing you
definitely do not need to do this and I would recommend against it (even if
you are already using enterprise). In your case it is best to have
development and production separate. It is very easy to deploy all reports
again. RS has multiple configurations you can deploy to (I have three). You
can deploy all your reports or you can deploy just the ones you need (select
the ones to deploy, right mouse click deploy).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RemoteDeploy" <bofobofo@.yahoo.com> wrote in message
news:1107497967.753916.202930@.l41g2000cwc.googlegroups.com...
> Hello Dmitry,
> I can echo the comments of VNN. I am into my second week using RS,
> apart from initial hiccups of installation, development has been rapid.
> I am eagerly awaiting SP2 to see if they can add some features which i
> feel can make my life easier.
> As you mentioned multiple installations of RS pointing to same DB, I
> would like to know more about this.
> I am trying to deploy my reports on a remote server. But i am not sure
> to use the existing RS DB on a machine in my domain or
> Create a new RS db on the server.
> Would like to know how to go about
> 1. Using the existing DB
> 2. Creating a new DB on the server.
> In case of creating a new DB is there a way I can export all the
> reports I created on my local machine to the new report server ?
> What are the security/account types/auth/IIS issues I need to take care
> of.
> I am gonna do the installation tommorow and trying to get as much info
> as possible.
>
> Thx
> Bofo
>