Showing posts with label boxes. Show all posts
Showing posts with label boxes. Show all posts

Wednesday, March 7, 2012

Keeping IIS and SQL Server on seperate boxes

Hi,
I have a problem in that I have one server with IIS and another with SQL
Server 2000. I would like to run SSRS from the SQL Server and then store all
my pages on the IIS server. Is there a way of doing this. Only installing
SSRS on the SQL Server and then everything else on the IIS server. I have
installed SSRS on a server that has both SQL Server and IIS on it and no
problems. The thing is I need the Virtual Directories on the IIS server and
not the SQL Server box. I am not allowed to install SSRS on the IIS box as
this would mean another license which my company is not prepared to do.
Please any help on how this could be done would be greatly appreciated.
ThanksThe license is clear. Anywhere you install the server component of RS you
need a license. What you are asking not only can not be done from a
licensing perspective but RS itself is an asp.net application. The SQL
Server DB is an object repository and can reside either on the same box or
on another box. However, if it is on another box you need a server license.
You didn't say if you are doing an intranet or internet application. If you
are not doing a processor license (which is what you would have to do if it
was for the internet but if intranet is optional) but instead have CALs.
Assuming the people accessing it already have CALs (in my case they do) then
all you need to do is buy the server license. For standard addition it is
very inexpensive to buy another server license. Even for enterprise
(assuming you have the CALs, a very important point) it is still much less
expensive than any other solution I am aware of.
Bruce L-C
"PLSH" <PLSH@.discussions.microsoft.com> wrote in message
news:AC4DF146-4A24-4A12-8440-6D6230AD6C4E@.microsoft.com...
> Hi,
> I have a problem in that I have one server with IIS and another with SQL
> Server 2000. I would like to run SSRS from the SQL Server and then store
all
> my pages on the IIS server. Is there a way of doing this. Only installing
> SSRS on the SQL Server and then everything else on the IIS server. I have
> installed SSRS on a server that has both SQL Server and IIS on it and no
> problems. The thing is I need the Virtual Directories on the IIS server
and
> not the SQL Server box. I am not allowed to install SSRS on the IIS box as
> this would mean another license which my company is not prepared to do.
> Please any help on how this could be done would be greatly appreciated.
> Thanks

Keep Together Function Not Working

These 3 posts all address same problem: Basically, have some data, either in
a group of text boxes or in a table and they are ending up on two pages of
the report, when they should only be on one.
Has anyone found a solution?
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=47aa22ae-f3a2-41bd-9b5b-a233914f7c7d&sloc=en-us
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=12c7fbc6-1aca-4e3a-9b2f-e15917fb7c22&sloc=en-us
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=76f3399b-06f1-4438-bd6a-d468578e6e20&sloc=en-usI HAVE FOUND A "DIRTY" WAY TO GET THE GROUPINGS WORKING.
THE TRICK IS TO CREATE NESTED GROUPING TABLES.
For example,
I have a query output with Agent name , client name and client details.
In order to keep them grouped, I create a table with one group, the Agent
(header, no details).
In that group, I create a table with one group, the Client (same as above).
And in that I group I create another table with the Client Details.
I only use details at the lower lever (the client details).
That works.
I don't like it because it makes the report complicated but it works.
"msflinx" wrote:
> These 3 posts all address same problem: Basically, have some data, either in
> a group of text boxes or in a table and they are ending up on two pages of
> the report, when they should only be on one.
> Has anyone found a solution?
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=47aa22ae-f3a2-41bd-9b5b-a233914f7c7d&sloc=en-us
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=12c7fbc6-1aca-4e3a-9b2f-e15917fb7c22&sloc=en-us
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=76f3399b-06f1-4438-bd6a-d468578e6e20&sloc=en-us
>|||Very interesting approach. Should work though and since most of my reports
are only three levels deep, I might try it.
Thanks for you assistance.
"Kyriakos" wrote:
> I HAVE FOUND A "DIRTY" WAY TO GET THE GROUPINGS WORKING.
> THE TRICK IS TO CREATE NESTED GROUPING TABLES.
> For example,
> I have a query output with Agent name , client name and client details.
> In order to keep them grouped, I create a table with one group, the Agent
> (header, no details).
> In that group, I create a table with one group, the Client (same as above).
> And in that I group I create another table with the Client Details.
> I only use details at the lower lever (the client details).
> That works.
> I don't like it because it makes the report complicated but it works.
> "msflinx" wrote:
> > These 3 posts all address same problem: Basically, have some data, either in
> > a group of text boxes or in a table and they are ending up on two pages of
> > the report, when they should only be on one.
> >
> > Has anyone found a solution?
> >
> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=47aa22ae-f3a2-41bd-9b5b-a233914f7c7d&sloc=en-us
> >
> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=12c7fbc6-1aca-4e3a-9b2f-e15917fb7c22&sloc=en-us
> >
> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=76f3399b-06f1-4438-bd6a-d468578e6e20&sloc=en-us
> >
> >