Contents x
    XA Server/SQL FAQ
    • 27 Mar 2023
    • 2 Minutes to read
    • Contributors
    • Dark
      Light
    • PDF
    Contents

    XA Server/SQL FAQ

    • Updated on 27 Mar 2023
    • 2 Minutes to read
    • Contributors
    • Dark
      Light
    • PDF
    Article summary

    The following questions and answers are provided to give you an additional level of detail regarding XA Server. If you do not see your question here, please contact your IA Support.

    Why do I need to add a dependency registry key to the services?

    In a server setup where SQL Server and XA Server are installed on the same machine, it is important that the SQL services begin to run before the ExactAccess Server service runs. This registry key configures the ExactAccess Server services to run after a SQL instance has been initiated.

    Why do you recommend Windows Authentication mode? Can SQL Authentication be used?

    Windows Authentication mode is recommended because it is more secure than SQL Authentication. The generic administrative account used for SQL Authentication is widely known, and often easy to exploit. Using Windows Authentication simplifies the installation and configuration of XA Server. We have chosen to document Windows Authentication to make the installation and configuration instructions simpler and easier to follow.

    XA Server does support SQL Authentication. If you are using SQL Authentication or SQL clusters in your environment, please contact your HealthCast Project Manager.

    Does XA support databases other than Microsoft SQL Server?

    No. XA only supports Microsoft SQL Server. HealthCast will consider support for additional databases in future releases of XA.

    How can I quickly determine the version of Microsoft SQL server?

    Execute the following query in the SQL Management Studio against the server the database resides on:

    SQL Version numbers

    SQL 2016 = 13.x
SQL 2014 = 12.x
SQL 2012 = 11.x
SQL 2008 = 10.x
SQL 2005 = 9.x
SQL 2000 = 8.x

    SQL Version Query

    SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
    • Example output when connected to SQL 2016 Enterprise
      • 13.0.1601.5 – RTM – Enterprise Edition: Core-based Licensing (64-bit)
        • RTM indicates, "release to manufacturing". This means that no service pack has been applied.
    • Example output when connected to SQL 2012 Enterprise
      • 11.0.5343.0 – SP2 – Enterprise Edition (64-bit)
    • Example output when connected to SQL 2005 Enterprise
      • 9.0.0.1399.06 -- RTM -- Enterprise Edition
      • RTM indicates, "release to manufacturing". This means that no service pack has been applied.
    NOTE

    While using the "select @@version" query may seem to be a quicker way to check the SQL version, this command actually shows the Operating System service pack level, not the SQL Server service pack level, which often leads to confusion of the version of the SQL server instance.

    Can I configure the ProxCard server to always save passwords, or set a high password save time so that passwords are never expired?

    It is now possible to set the server to always retain passwords so that they never expire. See ProxCard Server configuration.

    NOTE

    It is not recommended to have password expiration set to infinite in a mixed mode environment where PIN is not enabled on workstations.

    What is the maximum password save time for ProxCard server?

    ProxCard server does not support password expiration longer than 1440 minutes (24 hours) when configured to support expiration with the configuration tool - however, though not recommended, the value can be directly modified in the registry to support longer times. With rolling password save, it is recommended to have this value as short as possible for higher security.

    Was this article helpful?
    What's Next