Reports on Web farm-Please reply

Hi
We are planning to deploy SQL Server reports on our Internet site which is a
web farm of Windows 2003 web edition servers. We have total 9 boxes in our
Internet web farm and they sit in DMZ spread onto multiple locations. Our
dev/qa environment is inside our network and here are my questions:
1. Does the SQL Server database being used by our Internet servers has to be
in same DMZ domain or can it sit inside out network and then we can pass all
the db transactions back to database inside network? I read somewhere that RS
and SQL Server DB have to be on same domain to work. Is this correct?
2. Also I would like to know how we can deploy all the reports from our
internal dev/qa environment onto our Internet boxes on a continuous basis. I
guess I will have to setup report services on each box and then use some
scripting to move over the required files over to all 9 boxes. Is this
correct assumption? Do we need to copy some files onto each web servers or if
they are talking to same database then the moment we update the db, changes
will be reflected across all web farm sites? Is there any online resource
which describes this whole thing?
Please note that I am not SQL DBA and have just started using SQL Server
reports.
--
ThanksIf you are deploying over the internet then you need to use forms based
authentication and my understanding (but I am hazy on this so don't consider
the answer definitive) is the issue with domains will not matter.
I can answer your second question more definitively than the first. If you
look at a server and look for any rdl files you will not find any. When you
deploy you are not copying files. Deployment is the process where the
reports get stored in the object store for Reporting Services (i.e. in the
database). The whole point of a web farm is they all point to a single
database for the object store and they all see the same reports, report
cache, subscriptions, etc. As far as how you deploy, you can deploy from
your dev machines or you can copy the rdl files over someplace else and then
you scripting to deploy them. An example of how to do this ships with the
product (I always just deploy from the dev environment so I have no ever
scripted this but I know it is possible).
Note for a web farm you have to be running enterprise edition of SQL Server.
Also you need an enterprise edition license for each server in the web farm.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"tiwanap" <tiwanap@.discussions.microsoft.com> wrote in message
news:5A5A9C26-2106-4E25-9BC6-6E52000ED2CB@.microsoft.com...
> Hi
> We are planning to deploy SQL Server reports on our Internet site which is
> a
> web farm of Windows 2003 web edition servers. We have total 9 boxes in our
> Internet web farm and they sit in DMZ spread onto multiple locations. Our
> dev/qa environment is inside our network and here are my questions:
> 1. Does the SQL Server database being used by our Internet servers has to
> be
> in same DMZ domain or can it sit inside out network and then we can pass
> all
> the db transactions back to database inside network? I read somewhere that
> RS
> and SQL Server DB have to be on same domain to work. Is this correct?
> 2. Also I would like to know how we can deploy all the reports from our
> internal dev/qa environment onto our Internet boxes on a continuous basis.
> I
> guess I will have to setup report services on each box and then use some
> scripting to move over the required files over to all 9 boxes. Is this
> correct assumption? Do we need to copy some files onto each web servers or
> if
> they are talking to same database then the moment we update the db,
> changes
> will be reflected across all web farm sites? Is there any online resource
> which describes this whole thing?
> Please note that I am not SQL DBA and have just started using SQL Server
> reports.
> --
> Thanks