Hi,
We are running SQL 2000 still and I would like to implement reporting
services. When I install reporting services on the server will it require a
reboot to complete the installation? This is a production machine and I'd
like to install it during normal working hours but obviously can't if it
requires a reboot.
Generally speaking, does it take a lot of resources to run reporting
services? We have a rather small organization where only half a dozen folks
will need to run reports occasionally. Should I expect to see this using a
lot of system resources? Obviously, I know that some reports may take more
resources than others, but generally speaking...
We have SQL Server 2000 Standard, my understanding is that I am also
licensed for a single installation of reporting services. Can this
installation be on a different server than the actual SQL database or does
that take an additional license?
Thanks in advance,
LinnYes, if you install the Reporting Services on different computer, you need
another SQL Server 2000 license. You also need IIS runing and .NET1.1
installed. As far as I know, it does not need to restart computer (not 100%
sure, though).
We run SQL Server, reporting services and our major ASP.ENT app on a single
box (fairly powerful, though), to avoid to buy seperate SQL Server license,
just because of using RS. It is pretty smoother, so far, although our
ASP.NET apps and reporting services are used by more then 50 people daily
intensively.
"Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
news:egupPo6%23HHA.4592@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We are running SQL 2000 still and I would like to implement reporting
> services. When I install reporting services on the server will it require
> a reboot to complete the installation? This is a production machine and
> I'd like to install it during normal working hours but obviously can't if
> it requires a reboot.
> Generally speaking, does it take a lot of resources to run reporting
> services? We have a rather small organization where only half a dozen
> folks will need to run reports occasionally. Should I expect to see this
> using a lot of system resources? Obviously, I know that some reports may
> take more resources than others, but generally speaking...
> We have SQL Server 2000 Standard, my understanding is that I am also
> licensed for a single installation of reporting services. Can this
> installation be on a different server than the actual SQL database or does
> that take an additional license?
> Thanks in advance,
> Linn
>|||Just a heads up, be sure to install the RS 2000 service packs. Also, people
exporting to PDF or Excel can really hammer the server. If there is any way
to upgrade the license (note I say license, not database) to SQL 2005 so you
can install RS 2005 it would be a good idea. There are a lot of improvements
with RS 2005. Multi-select parameters, end user sorting, faster pdf and
excel rendering, calendar control, etc.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
news:egupPo6%23HHA.4592@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We are running SQL 2000 still and I would like to implement reporting
> services. When I install reporting services on the server will it require
> a reboot to complete the installation? This is a production machine and
> I'd like to install it during normal working hours but obviously can't if
> it requires a reboot.
> Generally speaking, does it take a lot of resources to run reporting
> services? We have a rather small organization where only half a dozen
> folks will need to run reports occasionally. Should I expect to see this
> using a lot of system resources? Obviously, I know that some reports may
> take more resources than others, but generally speaking...
> We have SQL Server 2000 Standard, my understanding is that I am also
> licensed for a single installation of reporting services. Can this
> installation be on a different server than the actual SQL database or does
> that take an additional license?
> Thanks in advance,
> Linn
>|||I hadn't thought of that, I was thinking that since it's SQL 2000 it should
be RS 2000 as well. We are subscribed to the assurance licensing with MS so
I'm assuming I can get 2005. My main concern is that I don't disrupt my SQL
server. Our main database application is not designed for use with SQL
2005. They are working on an upgrade and expect it sometime next year.
But that is a good thought, using RS 2005 with our existing DB. But can
they co-exist on the same hardware?
Thanks,
Linn
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OYJ1x56%23HHA.5948@.TK2MSFTNGP04.phx.gbl...
> Just a heads up, be sure to install the RS 2000 service packs. Also,
> people exporting to PDF or Excel can really hammer the server. If there is
> any way to upgrade the license (note I say license, not database) to SQL
> 2005 so you can install RS 2005 it would be a good idea. There are a lot
> of improvements with RS 2005. Multi-select parameters, end user sorting,
> faster pdf and excel rendering, calendar control, etc.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
> news:egupPo6%23HHA.4592@.TK2MSFTNGP03.phx.gbl...
>> Hi,
>> We are running SQL 2000 still and I would like to implement reporting
>> services. When I install reporting services on the server will it
>> require a reboot to complete the installation? This is a production
>> machine and I'd like to install it during normal working hours but
>> obviously can't if it requires a reboot.
>> Generally speaking, does it take a lot of resources to run reporting
>> services? We have a rather small organization where only half a dozen
>> folks will need to run reports occasionally. Should I expect to see this
>> using a lot of system resources? Obviously, I know that some reports may
>> take more resources than others, but generally speaking...
>> We have SQL Server 2000 Standard, my understanding is that I am also
>> licensed for a single installation of reporting services. Can this
>> installation be on a different server than the actual SQL database or
>> does that take an additional license?
>> Thanks in advance,
>> Linn
>>
>|||Yes. This is fully supported. I ran that way for 6 months. It is absolutely
no problem to have the metadata/object cache databases on SQL 2000.
I would hesitate to run RS 2000 on a production database server. I would
periodically have my server get totally frozen if a user exports a large
report to Excel or PDF. This problem for me went totally away when I went to
RS 2005. RS 2005 is on service pack 2, be sure to install that.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
news:%23rKXon7%23HHA.4732@.TK2MSFTNGP04.phx.gbl...
>I hadn't thought of that, I was thinking that since it's SQL 2000 it should
>be RS 2000 as well. We are subscribed to the assurance licensing with MS
>so I'm assuming I can get 2005. My main concern is that I don't disrupt my
>SQL server. Our main database application is not designed for use with SQL
>2005. They are working on an upgrade and expect it sometime next year.
> But that is a good thought, using RS 2005 with our existing DB. But can
> they co-exist on the same hardware?
> Thanks,
> Linn
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:OYJ1x56%23HHA.5948@.TK2MSFTNGP04.phx.gbl...
>> Just a heads up, be sure to install the RS 2000 service packs. Also,
>> people exporting to PDF or Excel can really hammer the server. If there
>> is any way to upgrade the license (note I say license, not database) to
>> SQL 2005 so you can install RS 2005 it would be a good idea. There are a
>> lot of improvements with RS 2005. Multi-select parameters, end user
>> sorting, faster pdf and excel rendering, calendar control, etc.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
>> news:egupPo6%23HHA.4592@.TK2MSFTNGP03.phx.gbl...
>> Hi,
>> We are running SQL 2000 still and I would like to implement reporting
>> services. When I install reporting services on the server will it
>> require a reboot to complete the installation? This is a production
>> machine and I'd like to install it during normal working hours but
>> obviously can't if it requires a reboot.
>> Generally speaking, does it take a lot of resources to run reporting
>> services? We have a rather small organization where only half a dozen
>> folks will need to run reports occasionally. Should I expect to see
>> this using a lot of system resources? Obviously, I know that some
>> reports may take more resources than others, but generally speaking...
>> We have SQL Server 2000 Standard, my understanding is that I am also
>> licensed for a single installation of reporting services. Can this
>> installation be on a different server than the actual SQL database or
>> does that take an additional license?
>> Thanks in advance,
>> Linn
>>
>>
>|||Thanks for the information Bruce. I just received my SQL 2005 disks and
will give it a try on the test system once I have Windows installed
successfully.
Linn
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eukF477%23HHA.5160@.TK2MSFTNGP05.phx.gbl...
> Yes. This is fully supported. I ran that way for 6 months. It is
> absolutely no problem to have the metadata/object cache databases on SQL
> 2000.
> I would hesitate to run RS 2000 on a production database server. I would
> periodically have my server get totally frozen if a user exports a large
> report to Excel or PDF. This problem for me went totally away when I went
> to RS 2005. RS 2005 is on service pack 2, be sure to install that.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
> news:%23rKXon7%23HHA.4732@.TK2MSFTNGP04.phx.gbl...
>>I hadn't thought of that, I was thinking that since it's SQL 2000 it
>>should be RS 2000 as well. We are subscribed to the assurance licensing
>>with MS so I'm assuming I can get 2005. My main concern is that I don't
>>disrupt my SQL server. Our main database application is not designed for
>>use with SQL 2005. They are working on an upgrade and expect it sometime
>>next year.
>> But that is a good thought, using RS 2005 with our existing DB. But can
>> they co-exist on the same hardware?
>> Thanks,
>> Linn
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:OYJ1x56%23HHA.5948@.TK2MSFTNGP04.phx.gbl...
>> Just a heads up, be sure to install the RS 2000 service packs. Also,
>> people exporting to PDF or Excel can really hammer the server. If there
>> is any way to upgrade the license (note I say license, not database) to
>> SQL 2005 so you can install RS 2005 it would be a good idea. There are a
>> lot of improvements with RS 2005. Multi-select parameters, end user
>> sorting, faster pdf and excel rendering, calendar control, etc.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
>> news:egupPo6%23HHA.4592@.TK2MSFTNGP03.phx.gbl...
>> Hi,
>> We are running SQL 2000 still and I would like to implement reporting
>> services. When I install reporting services on the server will it
>> require a reboot to complete the installation? This is a production
>> machine and I'd like to install it during normal working hours but
>> obviously can't if it requires a reboot.
>> Generally speaking, does it take a lot of resources to run reporting
>> services? We have a rather small organization where only half a dozen
>> folks will need to run reports occasionally. Should I expect to see
>> this using a lot of system resources? Obviously, I know that some
>> reports may take more resources than others, but generally speaking...
>> We have SQL Server 2000 Standard, my understanding is that I am also
>> licensed for a single installation of reporting services. Can this
>> installation be on a different server than the actual SQL database or
>> does that take an additional license?
>> Thanks in advance,
>> Linn
>>
>>
>>
>
No comments:
Post a Comment