If the server hosting SQL Server 2008 is powerful enough (mainly RAM), it is fairly easy to add another instance of SQL Server to host a second ARSystem. I did this on my current production SQL Server while doing the migration from 7.1/7.0 to 7.6.04 last year so that I could host an upgrade instance and a new install instance side by side. Once we got 7.6.04 into production, we turned off the second SQL Server instance and increased the resources for the production SQL Server.
Anything that causes you to use a different name for the ARSystem database will always make it harder to restore that db to another server and ARS instance. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Drew Shuller Sent: Thursday, November 08, 2012 11:03 AM To: [email protected] Subject: Multiple ARSystem databases on one database server ** Hello everyone, There is plenty of documentation about moving an ARSystem database from one database server to the other. But what do you need to do if that database server already contains a database called ARSystem? We are considering two options: either create a new instance so that we can keep using the ARSystem name for both, or we rename that database, after moving the database files over. Is either option better than the other? Are there any showstoppers to doing it one way or the other? Database 1: SQL Server 2003, hosting the database for a custom Remedy 6.3 app Database 2: SQL Server 2008, hosting the database for ARS and ITSM 8 Thanks for all replies. Drew Shuller JTF-Bravo, Honduras _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
