Help! Where can we download the REAL Reporting Server Software?

Hi,
We downloaded Reporting Services software earlier this year and have been developing reports.
Now we are ready to start integration testing and I can not access the Report Manager on my development machine.
I get the message: Evaluation License Expired.

We have valid MS SQL 2000 licenses and thus my understanding is that we are entitled to download the developer and Standard editions of Report Services. Unfortunately, the only version provided to us at the time of our installation was the "eval" version.

Does anyone know where we can obtain Report Services Software that will not time-out on us?
More importantly, how can we upgrade our existing installations so that our report definitions and other meta-data are not lost?

We've done quite a bit of work in creating numerous reports and we would have a very difficult time recreating our existing reports.

Best Regards, Jane

PS - We do not have an MSDN subscription.

YOu should check the licensing forSQL Reporting Services it is a separate product.|||
Thanks for your note. Yes, I understand SQL Reporting Services is a separate product. However, it is a free
separate product if you have a valid MS SQL Server 2000 license. This is exactly our problem, because of our retail
MS SQL 2000 licenses we should be able to upgrade to retail standard and developer editions of Reporting
Services but I have not been able find a site from which to download this software [without a subscription to MSDN].
I am also working with Microsoft and will post the solution to this dilemma when it has been resolved.
|||I understand what you mean now.Check herefor more instructions on how to obtain your copy. Look under: Existing SQL Server 2000 Customers.

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I am
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I a
m
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I am
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........
Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

Help! 120day Eval to Full version

Ok, several months ago we had an independant contractor install some
financial software on a server I provided. I gave the guy a fully licenced
version of SQL Server and let him do his work.
Unfortunately, it appears he didn't use my copy of SQL, he downloaded and
used the 120 day evaluation version of SQL which has now expired.
Does anyone know if I can simply uninstall the 120 day eval version of SQL,
install the Full version and the copy over the raw data and log files? I am
unable to do a normal backup and restore since the Eval services won't
start.
Please help!
http://support.microsoft.com/default...b;en-us;281574
Take a filesystem backup that includes the database files before you start.
David Portas
SQL Server MVP

Help! 120day Eval to Full version

Ok, several months ago we had an independant contractor install some
financial software on a server I provided. I gave the guy a fully licenced
version of SQL Server and let him do his work.
Unfortunately, it appears he didn't use my copy of SQL, he downloaded and
used the 120 day evaluation version of SQL which has now expired.
Does anyone know if I can simply uninstall the 120 day eval version of SQL,
install the Full version and the copy over the raw data and log files? I am
unable to do a normal backup and restore since the Eval services won't
start.
Please help!http://support.microsoft.com/default.aspx?scid=kb;en-us;281574
Take a filesystem backup that includes the database files before you start.
--
David Portas
SQL Server MVP
--

Help! 120day Eval to Full version

Ok, several months ago we had an independant contractor install some
financial software on a server I provided. I gave the guy a fully licenced
version of SQL Server and let him do his work.
Unfortunately, it appears he didn't use my copy of SQL, he downloaded and
used the 120 day evaluation version of SQL which has now expired.
Does anyone know if I can simply uninstall the 120 day eval version of SQL,
install the Full version and the copy over the raw data and log files? I am
unable to do a normal backup and restore since the Eval services won't
start.
Please help!http://support.microsoft.com/defaul...kb;en-us;281574
Take a filesystem backup that includes the database files before you start.
David Portas
SQL Server MVP
--