Reporting Services in SQL 2000

I would like to learn/more, practice creating and using reports but I don't know if I can do that on my home laptop with version 2000. I know, I know... upgrade to 2005. Can't do that due to technical difficulties on my other pc. Can I do this with my current setup?

thx

Kat

Yes you can. For SQL 2000, Reporting Services came as an add on component rather that being part of main install package.

You will need to have Windows 2000 or XP Professional which comes with IIS. This is required for running Reporting Services.

|||

here are some links that will be helpful to you:

Download of Reporting Services for SQL Server 2000
http://www.microsoft.com/downloads/details.aspx?FamilyId=502C0D89-1308-4662-8F58-CEC55EF1235B&displaylang=en

Reporting Services for SQL Server 2000 documentation
http://www.microsoft.com/downloads/details.aspx?FamilyID=5e550d73-8f35-435e-bb71-c8573a1cdbdb&DisplayLang=en

White papers and Technical articles about Reporting Services for SQL Server 2000
http://www.microsoft.com/technet/prodtechnol/sql/2000/technologies/rptsvcs.mspx

hope this helps,

Tai Yee
SQL Server

|||

It looks like I can't do this on a standalone pc, but need to have a server that I'm using... frustrating!

Kat

|||

Hi,

Do you have the SQL Server 2000 is installed on your computer? As I remember, Reporting Services needs at least a Standart Edition for SQL2K

If you have SQL Server, then you need the IIS also installed on your pc.

If you want to create reports, you need also the VS.Net 2003 installed on your pc.

I can all run them on my laptop which is an XP SP2. Your machine does not need to be a server :)

Eralper

http://www.kodyaz.com

|||That's right. But I believe you need XP Professional and not XP Home edition because you don't get IIS with XP Home.|||

I only have 2000 Professional Edition. Looks like I'll have to wait for my other laptop to be repaired and then I'll try again.

I HOPE, I HOPE, I HOPE it works!

thx

Kat

|||Windows 2000 Professional should work just fine.|||

Hi,

I should get my xp professional laptop back this next week and I will have the Developer edition of SQL Server 2000 soon to be upgraded to 2005. You say I need IIS installed which I understand, but is VS.Net 2003 a free product or does this have to be paid for?

thx,

Kathleen

Reporting Services DB Best Practice.

Ok, so, I see in an early post, that I need to ask a bigger question.
I have a production SQL 2005 Standard Server. I have another SQL 2005
Standard server that is used for reporting services only. What is the best
method for updating that reporting services DB on a 15 - 30 minute cycle.
The database should be read-only, but I do need to set different permissions
on it.
What's the best practice?
Mirror
Replication
Log ShippingHi,
Best option is "REPLICATION". depending on your need it should be
"Transaction Replication" for online reports. Instead of 15 min, go for
online transaction replication only.
In fact we use the same setup and transaction replication works absolutely
fine.
Amarnath
"Kevin Antel" wrote:
> Ok, so, I see in an early post, that I need to ask a bigger question.
> I have a production SQL 2005 Standard Server. I have another SQL 2005
> Standard server that is used for reporting services only. What is the best
> method for updating that reporting services DB on a 15 - 30 minute cycle.
> The database should be read-only, but I do need to set different permissions
> on it.
> What's the best practice?
> Mirror
> Replication
> Log Shipping
>
>|||I'm confused. What are you trying to do. Are you trying to have a hot
backup? You are not talking about the data that is being used in the report
but the report server databases?
I think you are making this harder than necessary if the purpose is a hot
backup. If one server goes down and the other comes on-line, the only thing
you will lose are whatever new subscriptions that have been setup since the
last time you synced the servers. Seems to me that doing that nightly would
be good enough. First, the chances are low you even need to even use this
(assuming you have normal fault tolerant hardware). Two, it is not a
transaction system where valuable data is lots. In the unlikely event the
server crashed then the users would have to recreate any new subscriptions.
If you are using report builder then the chance for some lost work is
higher. But still, weighing the complexity and the effort versus the gain.
I agree with the other post that if you have to do this that you are talking
replication, there are a variety of ways to do this (log shipping etc). SQL
Server 2005 has more options in this area than 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:u86ZH0DRGHA.5500@.TK2MSFTNGP12.phx.gbl...
> Ok, so, I see in an early post, that I need to ask a bigger question.
> I have a production SQL 2005 Standard Server. I have another SQL 2005
> Standard server that is used for reporting services only. What is the
> best method for updating that reporting services DB on a 15 - 30 minute
> cycle. The database should be read-only, but I do need to set different
> permissions on it.
> What's the best practice?
> Mirror
> Replication
> Log Shipping
>