Installing the SQL Server Version

 

 

Before you begin:

a. Confirm that you have a SQL Server Administrator level password.

b. If you are upgrading from our desktop version, note the location of the existing data (.brd) files.  They can be found at 'File', 'Maintenance', 'List of Accounts' tab.

c. Unlock pass phrases for the InstallShield files.

d. Security - Best practices require that a unique SQL User login ID be created for each user, even if you are utilizing Integrated Security.  If the user currently has a login ID, create an additional ID specifically for this application.  The user should not have access to the password.

 

I.  Download and install onto a Workstation:

--SQL Version Client Support Files (http://www.treasurysoftware.com/support-files.html).

--Correct version of our software.  If not specified, use our public download (http://www.treasurysoftware.com/download.html).  Accept all default settings and install the software to the local workstation.

II. Start the program ('Start' button, 'Programs', etc...).

--Enter into the 'Sample' account - use the hyperlink on the Welcome page or from the main menu, select 'File', 'Open'.

--From the main menu, select 'File', then 'Migrate to SQL ...' to start the SQL Wizard.  The Wizard will prompt you to select the SQL Server to use, as well as for your (user, not administrator) SQL log in information.  Enter the unique Login ID created in 'Before you Begin, Step D'.  After completing the Wizard, exit and then re-enter the program.

III. Upon re-entering the program, you will be in 'SQL Mode'.

--From the main menu, select 'File', 'New Account', 'Create' to start the Account Creation Wizard.  When prompted for an ID, you will need to provide a System Administrator ID.

--Enter the name of the account you want to create, ie. 'checking', 'main', etc...   This name will also be used as the database name - so keep it SQL Server friendly (guidelines are posted in the Wizard).

--Note: If a 'brd' file was supplied to you, in 'Type of Account' - select 'Migrate' and browse to the file.  Otherwise, simply accept the default in 'Type of Account' as 'New Account'.

IV. Upon completion of the SQL Wizard you will be prompted to create a sample account.   Please do so.

Done.  You should now be able to access your accounts (sample + new account) you just created.

V. Test your connections

--Start the program ('Start' button, 'Programs', etc...).

--Enter into the 'Sample' account.

--Select from the main menu 'Reports', then select 'All Records' from the 'Select a Report' on the Report's toolbar.

 

VI. Enter a Custom Configuration Code (if applicable)

--Enter into the account created in Step III.

--From the main menu, select 'File', 'Options', 'General', then 'Custom Code'.

--Please note that there are 'Per Account' and 'System-Wide' codes.  Enter your code into the appropriate location.

 

Note:  As needed, repeat step III and VI for each account you wish to create.

 

 

Good Housekeeping & Security

Remember, just because you can access the accounts, doesn't mean anyone else can. You will still need to grant access rights.

VII. Grant users/roles/groups access rights on the SQL Server.  To assist you, we have created the role 'BankRecPosPayUsers' in each database (account) with user level rights.

 

To grant rights, open the SQL Server Enterprise Manager (supplied with Microsoft SQL) with an Administrator login.

 

Within Enterprise Manager, select the server, then expand the list of databases.  Select the database (account) to work with and expand the selection tree below it (click on the plus sign).  Depending on your environment, you may either:

 

--select 'Users' - right click - 'New Database User' - check 'BankRecPosPayUsers' and add users from the login drop down box

 

--select 'Roles', then double-click on 'BankRecPosPayUsers'.  Click the 'Add' button to add roles/groups.

 

Note: If a user is not listed, or if you wish to create one, select 'Security' (at the same level of the menu structure as 'Databases', 'Data Transformation Services', etc...), and then right click on 'Users'.

As always, follow your standard procedures for granting rights.

 

Workstations

VIII. Download and install the software on the remainder of the workstations.  Always install the SQL Utility before installing the program.  Switch each to 'SQL mode' as described in Step II. above.

IX. Each workstation maintains its own local listing/catalog of accounts (A/P staff should only list A/P accounts, payroll - payroll, etc...). Go to each workstation and select 'File', 'New' and then 'Add existing account'.  Select the accounts to add to the user's local catalog.

X. Enter the license codes at each workstation. To enter the codes, select from the main menu 'File', 'Enter License Codes'.  Note: Your registered phone number is your ID. Both will be provided to you.  If you have not received a license code, ask your representative for an extension of time code if needed.

 

 

Our Experience

The success and speed of a SQL Server installation/conversion is directly related to your security infrastructure. Plan ahead to grant proper access to your users.  Use our preset roles in each database.

 

Tip: For multiple upgrades, simply download the InstallShield file once to a shared resource (server) and install on each workstation using that copy.

 

 

FAQ's:

Do we need to install, load, or run any scripts on the SQL Server?

No - all software is loaded at the individual workstations.  The SQL Server is used only for the storage of data.

During the bank account creation process (above), a database will be created on the server for each bank account.

 

 

I accidentally entered an extra account for a user.  How do I remove the account from that user's catalog?

If you entered an incorrect account, go to the 'File', 'Maintenance', 'List of Accounts'. You can delete an entry in the catalog, without deleting the database (and records). Note - This functionality is different then our desktop version.  Our desktop version would delete the entire file.

Are there any requirements as the SQL Server?

Supported Server Software:

Microsoft SQL Server 7.0, with Service Pack 1,

Microsoft SQL Server 2000

We support all configurations of these versions from desktop (MSDE) to Enterprise.

 

There are no special hardware requirements, other than those of the minimal requirements set by Microsoft for SQL Server.

 

In sizing a server, we recommend that you consider:

--existing load - applications and processes.  Are they are they running to your expected level of service?  Are any Mission Critical applications on your server? Do any of them have unique security needs (payroll, etc...).

--number of connections, ie users - each new user will require additional resources from the server.  Will there be a significant increase in the number of users on the server?

 

Knowledge Base Article: KB2240

Treasury Software Corp. 1999 - 2005.  All rights reserved.

Can't find what you need? Contact us