All you need to do then is make sure that the ARAdmin account has the same password. The password is encrypted if changed from the default and resides in your ar.cfg file. If you do not find the password line in the file it means you are using the default password.
Other than that there is not much that you might need to watch for except if you have db links to external data sources and need to re-establish those links if your workflow uses them through either View forms or AL's or Filters/Escalations or SQL menus.. Also make sure that the ARAdmin user is the dbo of all the objects (including the DB as a whole) after the import. There are MS-SQL stored proceedures sp_changedbowner and sp_changeobjectowner to help you do that. Cheers Joe ----- Original Message ---- From: sivarama velicheti <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, October 9, 2008 3:05:06 PM Subject: database instance move ** Hi group, We need to move the ARSystem database from the old SQL instance to a new SQL instance. Can you please let me know what the application connection strings (like changing the database name in ar.cfg etc.) may be changed? What are the steps to be followed for that, or what are the precautions that need to taken prior to the move. We are on AR Server 7.1 Patch 3, SQL server 2005 and windows 2003 R2. The environment its going to be moved to is going to be similar. We are not trying to migrate the AR Server installation to a new machine but just moving the tables in the ARAdmin account in the old SQL instance to a new instance of SQL Server. Do I need to make any changes for the Mid-Tier settings to make it work? Thanks Sivarama _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
