Description

This procedure allows you to switch from Noah System 4’s SQL CE database (4GB) to a version of SQL purchased from Microsoft.

These directions are valid for a configuration that is new to Noah 4 or for a machine that has been running Noah 4 and now wants to move to SQL Server.

These directions will work on all Windows operating systems listed in the Noah System 4 minimum requirements that support SQL Server, and with both 32-bit and 64-bit versions of SQL.

The examples in this document are using Windows Server 2008 (64-Bit) Standard and SQL Server 2008. The SQL Server was set to use Windows Authentication during installation.

IMPORTANT: The location configuring Noah to use SQL Server must assume the responsibility for installing and configuring the SQL Server.

IMPORTANT: Noah 4’s built in database backup and restore tools will not function after Noah 4 has been connected to your SQL server. It is the Noah location’s responsibility to setup, use, and maintain the Microsoft SQL backup tools that come with the SQL server. HIMSA is not able to provide support or advice on the use of these tools.

IMPORTANT: If you are using SQL Server 2012 or later and Windows Authentication additional steps must be taken. These steps are performed AFTER the switch to SQL Server has been made.

IMPORTANT: Do not uninstall the Microsoft SQL Compact Edition database after configuring Noah to use Microsoft SQL Server. There are preference settings in the CE database files and Noah will not launch if these files have been removed.

NOTE: If you decide to locate your SQL server on a different machine than the Noah 4 server, you must install the SQL Server instance using mixed mode authenticationSee the FAQ for more information on the sql user permissions required when using mixed mode. Other than the mixed mode requirement, the directions for configuring Noah 4 to use SQL on a separate server are the same.

Installation Procedure

1. Install SQL Server.

  • IMPORTANT: DO NOT use the default instance when installing SQL Server, choose to create a named instance. When naming the instance do not use NOAH or HIMSA for the instance name or you will not be able to use Noah 4. Give the instance an original name. Write down the instance name as you will need it later.

2. Install NOAH 4. The Noah Configuration Wizard will launch. in the Choose your Noah Installation Typescreen, select the first option Store all my patient records on this computer.

3. Once Noah launches create a test patient record. 



Note:
 This test patient will be used to verify that Noah 4 is using SQL. During the switch you will migrate this test patient from the default Noah 4 SQL CE database to MS SQL. If you can see the test patient in the SQL Studio management studio utility once the switch is completed, the switch was successful.

4. Next, download and install the Noah 4 SQLCE2MSSQL utility appropriate for your Noah 4 version from the table via the Related Links to the right. After you download and unzip the utility, select setup.exe and choose all the default options.

5. After the installation of the Noah 4 SQLCE2MSSQL utility has completed, navigate toStart\Programs\HIMSA\Noah 4 SQLCE2MSSQL. Launch the Noah 4 SQLCE2MSSQL utility. 

6. If you have patients in your SQL CE database, these will be shown in the screen. The test patient you created earlier should be listed in here.

7. Select the Migrate menu on the tool bar and select the Edit Configuration File option.

8. The Edit Configuration file window will come up. You will now need to edit some of these options. Please see the picture below for reference. 

  • The Instance name will need to be changed to the instance name during the SQL installation (see step 1). In this example the instance was named Audiology.
  • The Server name will need to be changed to the name of the server computer where the SQL Server is installed. In this example, the server is called Hearing.
  • Finally, the Connection String will need to be edited. The Data Source will need to be the server\instance. In this example the data source is Hearing\Audiology. The security may need to be changed as well. If you are using Windows Authentication you can use Integrated Security = True

IMPORTANT: The Initial Catalog has to be MASTER. If it is changed the MSSQL database connection test will fail.

IMPORTANT: If you are using SQL Server 2012 or later and Windows Authentication, there are additional steps to complete at the end of this setup.

IMPORTANT: Note any spaces used in the example strings. These spaces must be there.

Example of the connection string for Windows Authentication:



Data Source=Hearing\Audiology;Initial Catalog=MASTER;Integrated Security = True

Example of the connection string for Mixed Mode authentication:

Data Source= Hearing\Audiology;Initial Catalog=MASTER;User ID = SA; Password=yourpassword

  • Select OK when you have completed making changes in the Edit Configuration file window.

9. Navigate to the Migrate menu in the tool bar. This time, select the Create MSSQL Db option. Select OKto continue with creating the Noah 4 database and tables in MS SQL.

10. The creation of the database and tables could take a few moments. When the creation has completed you will see a successful creation message.

Note: If you entered the Configuration string incorrectly in the previous step, you will receive an error similar to the following:

11. Next, the database connection string will need to be tested. Navigate to the Migrate menu on the toolbar. Select the Test MSSQL database connection option.

12 To test the database connection, select Test. If the connection is good, the Not Validated will change to OK:

13. Next navigate to the Migrate menu and select ‘Export data to MSSQL’. This step will populate the SQL database with Noah user information and passwords. Any patient records in the Noah 4 compact edition database will be migrated to the SQL server database.

14. The next step is to select “Settings file update” from the Migrate menu. Navigate to and select theNOAHDatabaseCore.dll file in your Noah 4 folder (default path for a 32-bit OS is: C:\program files\HIMSA\Noah 4). 

15. Once you have selected Open on the NOAHDatabase.Core.dll, you will be prompted to restart theNOAH Server Service

Navigate to the services in Control Panel. Stop the Noah Client service. Restart the Noah Server Service. Then Restart the Noah Client service



Note: You can reboot your computer if you would rather do this instead of rebooting the Noah Server Service.

16. At this point, your Noah 4 should be using MS SQL. To verify this, launch the SQL Studio Management utility. Make sure to select the instance you created.

17. Under Databases navigate to NoahDatabaseCore. Expand to view the tables. Open the Patient table and verify the test patient you created earlier is present.

18. Your Noah 4 is now using MS SQL as the database.

19. If you are using SQL Server 2012 or later and Windows Authentication, remain in the SQL Studio Management Utility and follow the steps in this document to complete the setup of Noah 4 and SQL Server.