That's actually where I was going in my mind as well....all server licenses loaded on each server so that no matter where a DB moves it has it's license already loaded
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Friday, September 28, 2007 3:56 PM To: [email protected] Subject: Re: 7.1 DB Restore L.J. I would think so... but here is an idea.... (Untested...) How about you apply all of your license to all of your servers in the progression? So likely DB progression would be Prod to Test. So you apply all of your Test keys on Production as well. That way when you move the DB to Test all the keys are already there. (And the "prod keys" should be ignored.) And similarly if Dev is moved to Test then you would also apply Test's keys on Dev too. (But I would think this type of a DB move would be rare if ever done.) But I think you get the idea. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/28/07, L. J. Head <[EMAIL PROTECTED]> wrote: > Ok...here is a new one....I think it is anyway > > with the 6.x world when syncing our environments we would take DB from > Server A (usually prod) and restore it to another DB for Dev, Test, Etc. > Now that in 7.1 licensing is stored in the DB instead of a file on the > server....when I perform this restore in our new environment...do I > need to re-apply licenses? ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
