Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 18,614 of 19,505    |
|    Gene Wirchenko to All    |
|    Handling New Versions    |
|    07 May 12 20:40:32    |
      XPost: microsoft.public.sqlserver.programming       From: genew@ocis.net              Dear SQLers:               Here is something that I have not seen addressed in anything I       have read. How does one handle changing versions?               It turns out that my opposite number and I installed different       versions of SQL Server 2008 Express. He has R2 and I have "" (R1?).       My system is a sacrificial goat so I can blow away SQL Server any time       I want. But what of a production environment?               Suppose that there is an existing installation of SSE. Call it       OLD. We wish to install a new version. Call that one NEW. It would       be irresponsible to blow away OLD, install NEW, and hope that it all       works. We would like to be able to test that NEW does work with our       existing databases before taking out OLD.               When we have completed this, how do we do a switchover so that       whatever was pointing to OLD is now pointing to NEW? Is it possible       to rename an instance? What questions should I be asking here?              Sincerely,              Gene Wirchenko              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca