Q. Why would I choose to configure Noah System to use a Microsoft SQL Server database?
A. The default Noah database, Microsoft Compact Edition (CE), has a 4 GB size limit which is adequate for almost all Noah locations. You may decide to configure Noah to use SQL Server to comply with administrative and/or security requirements. In addition it is only possible to separate the database from the Noah application if you use a Microsoft SQL Server database.

Q. What versions of Microsoft SQL Server are supported with Noah 4? Which operating systems are supported for Noah 4 using a SQL Server database?
A. Complete information on supported operating systems and Microsoft SQL Server versions can be found in HIMSA’s Platform Strategy document located here.

Q. Is Noah using SQL Server supported in the same manner as Noah configured with the default Compact Edition database?
A. Support for Microsoft SQL Server is the responsibility of the location configuring Noah with SQL Server. The Noah Database Tools, including the backup utility, are disabled when configured with SQL Server. First level technical support, provided by HIMSA member companies, is still available for Noah specific issues when using SQL Server.

Q. Can the Noah database be located on a database server separate from the Noah Server application?
A. Yes with Noah 4 the database can be on a different server from the Noah Server application. In this case you must install SQL Server using mixed mode authentication.

Q. We have an application server configured. We also have a separate database server. What role does the application server play in this scenario? Will the clients connect directly to the database? 
A. Noah Clients DO NOT connect directly to the database. The Noah clients communicate with Noah Server on the application server, Noah Server communicates with the database.

Q. What authentication mode is required for SQL Server when installing for use with Noah?
A. Windows Authentication can be used if Noah and the SQL database are on the same machine. Mixed Mode Authentication needs to be selected if the Noah application and Noah database will be located on different machines.

Q. Does the SQL Server user have to be sa? Can it be another SQL Server account that is in sysadmin role?
A. If using mixed mode authentication a sql user and password are required for the connection string. HIMSA testing has been done with the sql user being the sa user. A location can create their own sql user with administrative rights. If they want to then limit rights on the user account after creating the Noah database, DBO should be fine but this has not been extensively tested by HIMSA.

Q.  Can the Noah application be used in a SQL Clustered Environment?
A. Yes

Q. Am I able to host our NOAH database on an Azure SQL database?
A. No

Q. Once I have implemented the use of SQL server am I am able to read or manipulate data directly?

A. No.  The Noah End User License agreement does not allow the ability to access or alter data in the Noah database from outside of the Noah Software.

Q. Microsoft SQL Server Enterprise allows database files to be encrypted using Transparent Data Encryption, TDE. Is configuring TDE permitted with Noah System 4?

A. HIMSA has no reason to believe that enabling TDE will cause issues as this type of encryption is completely independent of Noah System 4. However, with the SQL Server configuration, the responsibility for installing, configuring, maintaining, and backing up the Noah database falls to the location, and HIMSA will not commit the resources to provide verification testing.