Question about Reporting Services License

Reporting Services is due to come out in December 2003 or
January 2004 for SQL2000. I understand that it is free or
like an add on for current SQL licenses. My question is:
Do I have to install it on a SQL Server or can I install
in on a seperate server. I'd like to keep the load of
running reports off of our Production Server. If I had
say a reporting server that didn't have SQL2000 installed,
can I install reporting services there for use with the
Production SQL2000 Server?
Thanks,
VanIt is licensed like Analysis Services. You can install it on a separate
server (i.e. one not running SQL Server) however this requires a SQL license
(or licenses for per processor) for the separate server. There is a standard
edition and an enterprise edition available (enterprise allows web farm
support and dynamic data delivery). Have a look at
http://www.microsoft.com/sql/reporting/howtobuy/faq.asp
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Van Jones" <anonymous@.discussions.microsoft.com> wrote in message
news:1d9501c3aee7$d9d94880$a601280a@.phx.gbl...
Reporting Services is due to come out in December 2003 or
January 2004 for SQL2000. I understand that it is free or
like an add on for current SQL licenses. My question is:
Do I have to install it on a SQL Server or can I install
in on a seperate server. I'd like to keep the load of
running reports off of our Production Server. If I had
say a reporting server that didn't have SQL2000 installed,
can I install reporting services there for use with the
Production SQL2000 Server?
Thanks,
Vansql

Question about encrypting a current App.

When we convert an existing app to start encryption and decrypting data as needed, I am required to make changes to atleast 50 stored procs. Within each of these SPs I do:

-- OPEN SYMMETRIC KEY

-- do the ecrypt or decrypt operation

-- CLOSE SYMMETRIC KEY

Is it possible to not use these steps in each of my SP's? i.e, can we generalize the open and close key calls somewhere else? Any tips are greatly appreciated. TIA.

You can open the symmetric keys as part of connecting to the database and close them as you log out. Anything executing in that context will have access to the keys and be able to encrypt and decrypt with them.

If your application opens/uses multiple connections on behalf of a user and is supposed to encrypt/decrypt on all of them, you would need to open the keys when you open each connection and close them when you cease using a connection. If connections are not pooled, you don't need to close the keys if you're going to kill the connection anyway.

Thanks
Laurentiu