Overview

You must be a 3.x user before 06/01/2000 to migrate.

This set of directions does not apply to 4.x users.

Before beginning, you must have the following:

SQL installed and running. (SOAPware, Inc. will not support the installation or maintenance of SQL. It is up to the user to administrate SQL. (SOAPware, Inc. will not support the installation or maintenance of SQL. It is up to the user to administrate SQL. Chart Searcher currently does not work with SQL databases, but development is underway for a Chart Searcher for SQL)

Access97 installed and running.

Update for Upsizing for Access97. This update is located on the Microsoft web site. (www.microsoft.com).
Please Note: The upsizing of an Access97 database to SQL is intended for advanced users. If you do not feel comfortable with this task, please contact your hardware or network support.

Step 1: Access Modifications

Before we start upsizing the database, we must make some corrections to the database. Please skip to Step 2 if you have installed SOAPware for the first time after 6/15/98. From Access97, open the SW_Charts database located in the data directory, inside your Soapware30 directory. Once opened, you should see the many different tables located inside the database. Locate the table "ExtendedGen_Demo". After finding this, delete the table. This table is not used in SQL. Locate the table, "Insurance_Demo". Open this table and locate the field ‘Authorization’. Delete this field from the table, as it is also not used in SQL. Save and Close the database.

Step 2: Device Initialization

From your SQL server, create a new database device called Soapware. Set the size of the database device to the maximum possible. (Leave enough room for a 35 Meg log file and any other programs that may run on the server. Keep in mind that the server it’s self will need hard drive space for its page file.)
From you SQL server, create a new database device called Soapwarelog. Set the size of the database device to 35 Meg.

Step 3: Database Initialization

From your SQL server, create a new database called sw_audio. Set the Data Device to Soapware and the Log Device to Soapwarelog. Since this will be one of seven databases inside the Soapware Device, we must reduce the size allotted to this database proportionally to its use. The chart below shows a normal distribution of resources.

Note: There are many things that can effect these percentages. For instance, if a site is using the scanning module, you may want to allot 50% of the resources to the imaging database. If you do not plan on scanning images, there is no reason to set the imaging database at a high level.

Set the Soapwarelog to 5 Meg.

Once created, edit the database and select the Options tab. One of the options to check is "Truncate Log on Checkpoint" This is the only option that you need to change.

Please repeat step 3 on all SOAPware databases. A list of the databases can be found in Figure 1.1.

Step 4: Modifying ODBC

From a client machine, open the control panel then open ODBC. Once opened, you should see the different SOAPware databases that begin with ‘SW’. If there are no databases of this type shown, SOAPware is not installed on this machine.

Click on "Add". This will bring up another window which allows you to select the "SQL Server". Once selected click on "Finish".

This will bring up another window called "ODBC SQL Server Setup". For the Data Source Name, enter the name of the database located in the "ODBC Data Source Administrator". For example, your first database should be "SW Audio". Choose your Server which will contain the new SQL databases. Make sure that you checkmark "Use Trusted Connection". From here, click on the "Options" button.

Your window should expand down and you should see a field called "Database Name". In this field, fill in the name of the database on the SQL server. In our case, that would be "sw_audio". Be sure to uncheck "Generate Stored Procedure for Prepared Statement"

Click OK, you will be asked if you would like to over write the data source name. Since this is the old Access data source, click yes.

You now have changed the database SW Audio in ODBC to point to your SQL server. Repeat step 4 for all SW databases. Repeat Step 4 for all client computers. See Figure 1.4.

Note: If you have upgraded your SOAPware from your original version, you may have two extra database sources. (SW Mover and SW Updates) Please ignore the databases as they do not affect SOAPware and should not be upsized to SQL.

Step 5: Upsizing the database:

Go to the computer which houses the SOAPware databases.

Note: You must also set the sources in ODBC on this computer even if SOAPware is not installed. (i.e., the computer is used as a file server.)

Start Access97 (upsizing upgrade must be installed), and open the database "sw_audio.mdb" located in the Soapware30\data directory. If you click on the Tables tab, you should see two tables "Reports_Binary", "Version".

From your menu, select Tools, Add-Ins, and finally Upsize to SQL-Server. A window will appear asking us to use or create a new database. Select the "Use existing database" and click on "Next".

A new window will appear in which you will want to click on the "Machine Data Source" tab, located at the top of the window.

From here, click on the Data Source we are upsizing, (SW Audio). Once selected, click "OK".
This will open another window which will have two areas in which tables can be listed inside. The one on the left will be called "Available Tables" and the one on the right will be called "Export to SQL Server". In this window, we will want to select all the tables for conversion. Click the ">>" which will bring all of the tables over to the right side and click on "Next".

Another window will appear. Select the same options in the window as the figure below. Please be sure "Link newly created SQL Server tables" is not checked.

To begin the upsizing, click "Finish".

Repeat Step 5 until all database have been upsized.