How to list reports, parameters, subcriptions for SQL 2000 with no

Hello,
I am really hoping someone can help me out, I don't have a lot of SQL or SQL
Reporting Services knowledge so please bear with me.
We use SQL 2000 Reporting Services at our office but the front end (web
interface) is not functioning (long story but we disabled OWA on the same box
and the SQL WI failed; turning OWA back on doesn't correct the problem).
Unfortunately we did not keep a listing of the available reports, their
parameters, the subscriptions or the schedules. This is our error and will
not happen going forward however I need to get this information; it looks
like we are going to have to rebuild it.
It is only the web interface itself that is broken, the back end is still
working properly and scheduled reports are being sent out. We just can't
modify anything.
Is it possible to retrieve this information? Where is it stored and how do
I get this information?
I saw a post somewhere that touched on this but I can't find it anywhere.
TIA,
NancyNancy,
Yes, it is possible to see the reports and their parameters. RS has a
ReportServer database that contains all of this information. You just need
to query the appropriate tables. For example, to see all of the reports
published to the Report Manager site, query the Catalog table in the
ReportServer database "Select *
from Catalog" presuming the list of report is not too long. The table names
are fairly well named so you should not have a problem determining where
information is stored. Obviously you will need to have read writes to the
ReportServer database to do this. Hope this helps.
"Nancy R" wrote:
> Hello,
> I am really hoping someone can help me out, I don't have a lot of SQL or SQL
> Reporting Services knowledge so please bear with me.
> We use SQL 2000 Reporting Services at our office but the front end (web
> interface) is not functioning (long story but we disabled OWA on the same box
> and the SQL WI failed; turning OWA back on doesn't correct the problem).
> Unfortunately we did not keep a listing of the available reports, their
> parameters, the subscriptions or the schedules. This is our error and will
> not happen going forward however I need to get this information; it looks
> like we are going to have to rebuild it.
> It is only the web interface itself that is broken, the back end is still
> working properly and scheduled reports are being sent out. We just can't
> modify anything.
> Is it possible to retrieve this information? Where is it stored and how do
> I get this information?
> I saw a post somewhere that touched on this but I can't find it anywhere.
> TIA,
> Nancy|||Hi,
This helps alot, thanks.
Now I have what is hopefully my last question: do I find these tables in a
db on the reporting server or on the backend SQL server we have?
Thanks again,
Nancy
"bsod55" wrote:
> Nancy,
> Yes, it is possible to see the reports and their parameters. RS has a
> ReportServer database that contains all of this information. You just need
> to query the appropriate tables. For example, to see all of the reports
> published to the Report Manager site, query the Catalog table in the
> ReportServer database "Select *
> from Catalog" presuming the list of report is not too long. The table names
> are fairly well named so you should not have a problem determining where
> information is stored. Obviously you will need to have read writes to the
> ReportServer database to do this. Hope this helps.
> "Nancy R" wrote:
> > Hello,
> >
> > I am really hoping someone can help me out, I don't have a lot of SQL or SQL
> > Reporting Services knowledge so please bear with me.
> >
> > We use SQL 2000 Reporting Services at our office but the front end (web
> > interface) is not functioning (long story but we disabled OWA on the same box
> > and the SQL WI failed; turning OWA back on doesn't correct the problem).
> >
> > Unfortunately we did not keep a listing of the available reports, their
> > parameters, the subscriptions or the schedules. This is our error and will
> > not happen going forward however I need to get this information; it looks
> > like we are going to have to rebuild it.
> >
> > It is only the web interface itself that is broken, the back end is still
> > working properly and scheduled reports are being sent out. We just can't
> > modify anything.
> >
> > Is it possible to retrieve this information? Where is it stored and how do
> > I get this information?
> >
> > I saw a post somewhere that touched on this but I can't find it anywhere.
> >
> > TIA,
> > Nancy|||It may depend on how things were set up inititally, on my SQL Server, I see
2 databases (ReportServer and ReportServerTempDB), Opening the
ReportServices icon in Management Studio shows the DataSources, Models, a
solution I created in VS.Net, User Folders and My Reports.
"Nancy R" <NancyR@.discussions.microsoft.com> wrote in message
news:57C20B42-9098-438F-89D6-8D63591F2E61@.microsoft.com...
> Hi,
> This helps alot, thanks.
> Now I have what is hopefully my last question: do I find these tables in
> a
> db on the reporting server or on the backend SQL server we have?
> Thanks again,
> Nancy
> "bsod55" wrote:
>> Nancy,
>> Yes, it is possible to see the reports and their parameters. RS has a
>> ReportServer database that contains all of this information. You just
>> need
>> to query the appropriate tables. For example, to see all of the reports
>> published to the Report Manager site, query the Catalog table in the
>> ReportServer database "Select *
>> from Catalog" presuming the list of report is not too long. The table
>> names
>> are fairly well named so you should not have a problem determining where
>> information is stored. Obviously you will need to have read writes to
>> the
>> ReportServer database to do this. Hope this helps.
>> "Nancy R" wrote:
>> > Hello,
>> >
>> > I am really hoping someone can help me out, I don't have a lot of SQL
>> > or SQL
>> > Reporting Services knowledge so please bear with me.
>> >
>> > We use SQL 2000 Reporting Services at our office but the front end (web
>> > interface) is not functioning (long story but we disabled OWA on the
>> > same box
>> > and the SQL WI failed; turning OWA back on doesn't correct the
>> > problem).
>> >
>> > Unfortunately we did not keep a listing of the available reports, their
>> > parameters, the subscriptions or the schedules. This is our error and
>> > will
>> > not happen going forward however I need to get this information; it
>> > looks
>> > like we are going to have to rebuild it.
>> >
>> > It is only the web interface itself that is broken, the back end is
>> > still
>> > working properly and scheduled reports are being sent out. We just
>> > can't
>> > modify anything.
>> >
>> > Is it possible to retrieve this information? Where is it stored and
>> > how do
>> > I get this information?
>> >
>> > I saw a post somewhere that touched on this but I can't find it
>> > anywhere.
>> >
>> > TIA,
>> > Nancy|||Microsoft do not recommend that you directly query the tables in the
ReportServer database. You should instead use the SSIS package and
reports that come provided as one of the Reporting Services samples.
These files (and instructions) can usually be found in C:\Program Files
\Microsoft SQL Server\90\Samples\Reporting Services\Report Samples
\Server Management Sample Reports but it will depend on your
installation path.
If you are going to query the ReportServer database directly then I'd
suggest you use the WITH (NOLOCK) directive in your query.
Regards,
Shane.
On Jun 12, 7:41 pm, bsod55 <bso...@.discussions.microsoft.com> wrote:
> Nancy,
> Yes, it is possible to see the reports and their parameters. RS has a
> ReportServer database that contains all of this information. You just need
> to query the appropriate tables. For example, to see all of the reports
> published to the Report Manager site, query the Catalog table in the
> ReportServer database "Select *
> from Catalog" presuming the list of report is not too long. The table names
> are fairly well named so you should not have a problem determining where
> information is stored. Obviously you will need to have read writes to the
> ReportServer database to do this. Hope this helps.
> "Nancy R" wrote:
> > Hello,
> > I am really hoping someone can help me out, I don't have a lot of SQL or SQL
> > Reporting Services knowledge so please bear with me.
> > We use SQL 2000 Reporting Services at our office but the front end (web
> > interface) is not functioning (long story but we disabled OWA on the same box
> > and the SQL WI failed; turning OWA back on doesn't correct the problem).
> > Unfortunately we did not keep a listing of the available reports, their
> > parameters, the subscriptions or the schedules. This is our error and will
> > not happen going forward however I need to get this information; it looks
> > like we are going to have to rebuild it.
> > It is only the web interface itself that is broken, the back end is still
> > working properly and scheduled reports are being sent out. We just can't
> > modify anything.
> > Is it possible to retrieve this information? Where is it stored and how do
> > I get this information?
> > I saw a post somewhere that touched on this but I can't find it anywhere.
> > TIA,
> > Nancy|||Hi Shane,
I don't have this folder, my path looks something like this: C:\Program
Files\Microsoft SQL Server\80 and I only have "RS Setup Bootstrap" and Tools
under this folder.
Should I be looking somewhere else for this?
Thanks,
Nancy
"shanejokeeffe" wrote:
> Microsoft do not recommend that you directly query the tables in the
> ReportServer database. You should instead use the SSIS package and
> reports that come provided as one of the Reporting Services samples.
> These files (and instructions) can usually be found in C:\Program Files
> \Microsoft SQL Server\90\Samples\Reporting Services\Report Samples
> \Server Management Sample Reports but it will depend on your
> installation path.
> If you are going to query the ReportServer database directly then I'd
> suggest you use the WITH (NOLOCK) directive in your query.
> Regards,
> Shane.
> On Jun 12, 7:41 pm, bsod55 <bso...@.discussions.microsoft.com> wrote:
> > Nancy,
> >
> > Yes, it is possible to see the reports and their parameters. RS has a
> > ReportServer database that contains all of this information. You just need
> > to query the appropriate tables. For example, to see all of the reports
> > published to the Report Manager site, query the Catalog table in the
> > ReportServer database "Select *
> > from Catalog" presuming the list of report is not too long. The table names
> > are fairly well named so you should not have a problem determining where
> > information is stored. Obviously you will need to have read writes to the
> > ReportServer database to do this. Hope this helps.
> >
> > "Nancy R" wrote:
> > > Hello,
> >
> > > I am really hoping someone can help me out, I don't have a lot of SQL or SQL
> > > Reporting Services knowledge so please bear with me.
> >
> > > We use SQL 2000 Reporting Services at our office but the front end (web
> > > interface) is not functioning (long story but we disabled OWA on the same box
> > > and the SQL WI failed; turning OWA back on doesn't correct the problem).
> >
> > > Unfortunately we did not keep a listing of the available reports, their
> > > parameters, the subscriptions or the schedules. This is our error and will
> > > not happen going forward however I need to get this information; it looks
> > > like we are going to have to rebuild it.
> >
> > > It is only the web interface itself that is broken, the back end is still
> > > working properly and scheduled reports are being sent out. We just can't
> > > modify anything.
> >
> > > Is it possible to retrieve this information? Where is it stored and how do
> > > I get this information?
> >
> > > I saw a post somewhere that touched on this but I can't find it anywhere.
> >
> > > TIA,
> > > Nancy
>
>|||Hi Nancy,
I'd wrongly assumed that this sample had also shipped with SQL Server
2000 Reporting Services. I just checked our old dev machine and
they're not there either so it looks like they're for SQL 2005 only.
It looks like your quickest option is the query the ReportServer
tables directly. Querying the tables directly should be ok once you
don't lock any of the tables with long running queries. Just bear in
mind that it's not a recommended practice.
Regards,
Shane.
On Jun 13, 2:11 pm, Nancy R <Nan...@.discussions.microsoft.com> wrote:
> Hi Shane,
> I don't have this folder, my path looks something like this: C:\Program
> Files\Microsoft SQL Server\80 and I only have "RS Setup Bootstrap" and Tools
> under this folder.
> Should I be looking somewhere else for this?
> Thanks,
> Nancy
> "shanejokeeffe" wrote:
> > Microsoft do not recommend that you directly query the tables in the
> > ReportServer database. You should instead use the SSIS package and
> > reports that come provided as one of the Reporting Services samples.
> > These files (and instructions) can usually be found in C:\Program Files
> > \Microsoft SQL Server\90\Samples\Reporting Services\Report Samples
> > \Server Management Sample Reports but it will depend on your
> > installation path.
> > If you are going to query the ReportServer database directly then I'd
> > suggest you use the WITH (NOLOCK) directive in your query.
> > Regards,
> > Shane.
> > On Jun 12, 7:41 pm, bsod55 <bso...@.discussions.microsoft.com> wrote:
> > > Nancy,
> > > Yes, it is possible to see the reports and their parameters. RS has a
> > > ReportServer database that contains all of this information. You just need
> > > to query the appropriate tables. For example, to see all of the reports
> > > published to the Report Manager site, query the Catalog table in the
> > > ReportServer database "Select *
> > > from Catalog" presuming the list of report is not too long. The table names
> > > are fairly well named so you should not have a problem determining where
> > > information is stored. Obviously you will need to have read writes to the
> > > ReportServer database to do this. Hope this helps.
> > > "Nancy R" wrote:
> > > > Hello,
> > > > I am really hoping someone can help me out, I don't have a lot of SQL or SQL
> > > > Reporting Services knowledge so please bear with me.
> > > > We use SQL 2000 Reporting Services at our office but the front end (web
> > > > interface) is not functioning (long story but we disabled OWA on the same box
> > > > and the SQL WI failed; turning OWA back on doesn't correct the problem).
> > > > Unfortunately we did not keep a listing of the available reports, their
> > > > parameters, the subscriptions or the schedules. This is our error and will
> > > > not happen going forward however I need to get this information; it looks
> > > > like we are going to have to rebuild it.
> > > > It is only the web interface itself that is broken, the back end is still
> > > > working properly and scheduled reports are being sent out. We just can't
> > > > modify anything.
> > > > Is it possible to retrieve this information? Where is it stored and how do
> > > > I get this information?
> > > > I saw a post somewhere that touched on this but I can't find it anywhere.
> > > > TIA,
> > > > Nancy|||Thanks everyone for your help, I appreciate it.
Nancy
"shanejokeeffe" wrote:
> Hi Nancy,
> I'd wrongly assumed that this sample had also shipped with SQL Server
> 2000 Reporting Services. I just checked our old dev machine and
> they're not there either so it looks like they're for SQL 2005 only.
> It looks like your quickest option is the query the ReportServer
> tables directly. Querying the tables directly should be ok once you
> don't lock any of the tables with long running queries. Just bear in
> mind that it's not a recommended practice.
> Regards,
> Shane.
>
> On Jun 13, 2:11 pm, Nancy R <Nan...@.discussions.microsoft.com> wrote:
> > Hi Shane,
> >
> > I don't have this folder, my path looks something like this: C:\Program
> > Files\Microsoft SQL Server\80 and I only have "RS Setup Bootstrap" and Tools
> > under this folder.
> >
> > Should I be looking somewhere else for this?
> >
> > Thanks,
> > Nancy
> >
> > "shanejokeeffe" wrote:
> > > Microsoft do not recommend that you directly query the tables in the
> > > ReportServer database. You should instead use the SSIS package and
> > > reports that come provided as one of the Reporting Services samples.
> > > These files (and instructions) can usually be found in C:\Program Files
> > > \Microsoft SQL Server\90\Samples\Reporting Services\Report Samples
> > > \Server Management Sample Reports but it will depend on your
> > > installation path.
> >
> > > If you are going to query the ReportServer database directly then I'd
> > > suggest you use the WITH (NOLOCK) directive in your query.
> >
> > > Regards,
> >
> > > Shane.
> >
> > > On Jun 12, 7:41 pm, bsod55 <bso...@.discussions.microsoft.com> wrote:
> > > > Nancy,
> >
> > > > Yes, it is possible to see the reports and their parameters. RS has a
> > > > ReportServer database that contains all of this information. You just need
> > > > to query the appropriate tables. For example, to see all of the reports
> > > > published to the Report Manager site, query the Catalog table in the
> > > > ReportServer database "Select *
> > > > from Catalog" presuming the list of report is not too long. The table names
> > > > are fairly well named so you should not have a problem determining where
> > > > information is stored. Obviously you will need to have read writes to the
> > > > ReportServer database to do this. Hope this helps.
> >
> > > > "Nancy R" wrote:
> > > > > Hello,
> >
> > > > > I am really hoping someone can help me out, I don't have a lot of SQL or SQL
> > > > > Reporting Services knowledge so please bear with me.
> >
> > > > > We use SQL 2000 Reporting Services at our office but the front end (web
> > > > > interface) is not functioning (long story but we disabled OWA on the same box
> > > > > and the SQL WI failed; turning OWA back on doesn't correct the problem).
> >
> > > > > Unfortunately we did not keep a listing of the available reports, their
> > > > > parameters, the subscriptions or the schedules. This is our error and will
> > > > > not happen going forward however I need to get this information; it looks
> > > > > like we are going to have to rebuild it.
> >
> > > > > It is only the web interface itself that is broken, the back end is still
> > > > > working properly and scheduled reports are being sent out. We just can't
> > > > > modify anything.
> >
> > > > > Is it possible to retrieve this information? Where is it stored and how do
> > > > > I get this information?
> >
> > > > > I saw a post somewhere that touched on this but I can't find it anywhere.
> >
> > > > > TIA,
> > > > > Nancy
>
>