There are hundreds of locations worldwide that are using Noah configured with a Microsoft SQL Server database. Many of these installations have separated the Noah application from the SQL database. In some cases, the location may want to update to a new SQL Server machine. In this case they will need to switch Noah to point to this new SQL Server database.
First, the new SQL Server machine will need to have an instance installed according to HIMSA recommendations and have the Noah SQL database backup restored to the new instance.
Then, Noah needs to be able to locate that new machine and instance. We need to edit the connection string to point to the new database server.
If you are using Noah 4.14 and earlier, you will edit the connection string using the Noah4DBConverter.exe located at C:\Program Files (x86)\HIMSA\Noah 4.
If you are using Noah 4.15, and you will edit the connection string using the SQLiteToMSSQL.exe located at C:\Program Files (x86)\HIMSA\Noah 4.
1. Launch the tool, choose Migrate, Edit Configuration file
2. Make appropriate changes to the Server connection parameters. For more detail on these parameters see Step 4 in the Configuring Noah with SQL Server directions here:
3. Select OK when you have completed making changes in the Edit Configuration file window
4. You will NOT be creating the database files or exporting data as it already exists from the Restore on the new database server
Choose Migrate, Test MSSQL database connection. If all is set correctly, you will get an OK.
5. Close the Noah 4 DB Converter
6. Restart the Noah Server service and Noah Client service
7. At this point, your Noah 4 should be looking at the new SQL Server machine and Noah database. To verify this, you can add a test patient in Noah and locate it in the Patient table in the SQL Database.
HIMSA