Purpose: By default, the Noah 4 Activity log saves the activity logs to a CE or SQLite database on the Noah Server computer.  If your installation of Noah 4 System is setup to use a SQL Server database, it is possible to set up the Noah 4 Activity log to save to a SQL database.  Below are the directions on how to use the Noah4ActivityLogDBConverter.exe utility to create the Noah4ActivityLog SQL database and how to configure Noah system to save the activity logs to this database. Below are directions to show how to use the Noah4ActivityLogDBConverter.exe utility if your SQL instance is Mixed Mode or Windows Authentication.

There are several important requirements to be aware of before you begin:

  • The location configuring Noah to use SQL Server must assume the responsibility for installing, configuring, maintaining, and backing up the Noah database on SQL Server.
  • The Noah 4 database Backup and Restore tools will not function after Noah 4 has been connected to SQL Server.
  • Do not uninstall the Microsoft SQL Compact Edition database after configuring Noah to use Microsoft SQL Server. There are required preference settings in the NoahCfgDatabase.sdf file and Noah will not launch if the database has been uninstalled.
  • If you have an existing local Noah CE or SQLite database that you are migrating to SQL Server and would like to ensure that patient data is removed after successfully migrating the data to SQL Server, click here for more information.
  • Noah encrypts data in transmission between the Noah server and the database. If Noah and the SQL database are on the same computer, the encryption is handled by Noah automatically. If the SQL database is located on a different machine, you can add transmission encryption via the connection string.  Please see the second connection string in section A, step i below.
  1. Launch the Noah4ActivityLogDBConverter.exe utility with Windows administrator rights.
  2. Once the Noah4ActivityLogDBConverter.exe utility is open populate the Connection String box with your connection string.  This is the same connection string you used when you set up Noah 4 to use SQL for its database. 

A)  Mixed Mode

i.) The connection string for mixed mode will look like this.

Data Source= TESTDATAHOST\TESTSITE;Initial Catalog=MASTER;User ID = SA; Password=ABC123

Or if you used Mixed Mode Authentication with encryption.**The SQL Server is on a different machine and you added encryption of data between Noah and the SQL Server.

Data Source= TESTDATAHOST\TESTSITE; Initial Catalog=MASTER;User ID = SA; Password= ABC123; Encrypt=True;TrustServerCertificate=True

ii.)   Select the “Test Connection String” button.

iii.)  If your connection string is valid, you will see a message that says, “SUCCESS: Connection String test was Successful.”

iv.)  Now Select the “Write Activity Log Configuration to disk” button. If everything is successful you will see messages like the messages in the picture below.

 You will also see a message box saying you need to either restart the PC or restart the Noah Server Service.  Please see the picture below.

v.) Once you have rebooted please skip to Step 3.

B)  Windows Authentication

i.) The connection string for Windows Authentication should look like the one below.

Data Source=WIN2012R2SQL\HEARING; Initial Catalog=MASTER;Integrated Security = True

ii.) Select the “Test Connection String” button.

iii.) If your connection string is valid, you will see a message that says, “SUCCESS: Connection String test was Successful.”

iv.) Now Select the “Write Activity Log Configuration to disk” button. If everything is successful, you will see messages like the messages in the picture below.

v.) You will also see a message box saying you need to either restart the PC or restart the Noah Server Service.  Please see the picture below.

vi.) Go to Step 3.

3. After rebooting the PC or restarting the Noah Server Service launch Microsoft SQL Server Management Studio.

4. Navigate to the Security directory in the tree structure, expand it.  Expand the Logins directory.  Please see the picture below.

5. Find the NT AUTHORITY\System Login.  Right Click on it and select “Properties.”

6. When the properties window appears click on User Mapping.

7. Now Check the checkbox by the Noah4ActivityLog Database and select it.

8. Once the Database role membership for: Noah4ActivityLog box becomes active, check the db_owner box.  Please see the picture below.

9. Select the OK button. 

10. Now close out of Noah Server Service launch Microsoft SQL Server Management Studio.  Launch Noah System.

11. Once Noah System is open, go to the File menu and open the Noah Console. 

12. Finally, select the Activity Log under the Noah Console tree structure.  If the Activity Log is populated, with a login message, this was created because you logged into Noah in step 11, the Activity Log is successfully saving the logs to the Noah4ActivityLog SQL database.