|
Move SQL Server databases from one server to another
Overview
Prepare and backup your databases on the old server.
Move the databases from the old server to the new server.
Confirm user logins and permissions on the new server
Install the new version of Treasury Software (client) on a test
machine and connect to the new server.
Rollout - Install the new version of Treasury Software (client)
on production workstations.
Note: The following instructions involves advanced knowledge of SQL server, and requires the support of your IT department.
Prepare and backup your databases on the old server.
1. Transmit any untransmitted ACH transactions in ACH Universal.
Exit the software.
2. Backup the current SQL databases per your corporate policies.
Move the databases from the old server to the new server.
1. Detach the databases
2. Copy/move the databases to the new server. Note: Do not move
the sample database.
3. Attach the databases on the new server.
For detailed
assistance with the above three steps, see Moving SQL Databases for System Administrators.
4. Grant security permissions to the newly mounted databases. Make
sure that you have proper login IDs and have granted permission
to the BankRecPosPayUser group in each database.
Confirm user logins and create permissions on the new server
Confirm the user's login on the SQL server with your database administrator (as below):
Enter into SQL Server Management Studio for the new server databases that you just mounted.
Select Security (at the server level). Select 'Login'. Confirm the existence of the user's ID.
If there is no login, please create one now.
To add a login, right click on 'Login' and select 'New Login'.
Enter the user's login name and complete the security options per your corporate environment.
For all users - you will need to grant permissions to the databases that you just mounted.
--Select the User Mapping's page
--Check the databases they need access to. Note: Always grant access to the 'Sample' database.
--Make sure that the role 'BankRecPosPayUsers' is checked
Click OK when finished.
Install the new version of Treasury Software (client) on a workstation and connect to the new server.
Go to a non-production workstation and follow the instructions for a first time SQL installation.
***IMPORTANT - Follow the instructions for a first time
SQL installation above before continuing.***
In addition, add the new accounts that you copied over.From the main menu select 'File', 'New Account', 'Add an Existing Account'. Select the accounts that the user should be able to see on their list of accounts.
Treasury Software may attempt to upgrade the database(s) at this point, allow it to do so.
Have your primary user confirm the data in the upgraded account(s).
Rollout - Install the new version of Treasury Software (client)
on production workstations.
Repeat the steps below for each client workstation which needs software. Follow the instructions for adding a new workstation in a SQL environment.
Tips:
The #1 issue in any upgrade is security.
--Make sure that you have a system administrator login ID before
starting
--Create/arrange for logins for all users
--Confirm that the BankRecPosPayUser group has been granted rights
to each database
and
--don't rollout to the users until you have fully tested the new
system.
Congratulations!
Alternate approaches:
Export data to a pass thru file and then re-import it into the target database.
Note: Contact Treasury Software first for the appropriate tables to migrate - not all tables are copied.
See http://www.treasurysoftware.com/support2-SQL-Import-Export.html
| 
