Drew, Sorry to provide you with conflicting information, but at my last job our production DB was named 'ARSystemProd' and we routinely renamed the DB on restore to other environments, in fact all environments were named differently, and NEVER had any issue with it, in fact all of our dev (4 in total) were on the same DB server and instance with 4 different names, and our test instances were the same, having 4 different remedy db's in the same instance and never had a lick of problems with the setup. So unless you have an over abundance of resources and just want to go through the hassle of standing up another instance on an existing server, I would personally just use another name on the same db server.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Drew Shuller Sent: Thursday, November 08, 2012 10: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 ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
