Create the Database
On this page
The Database Management wizard is the only supported way to create an Alloy Navigator database. Besides Create a new database, it offers Upgrade your existing database and Manage your Database Access Key; this topic covers creating a new database.
There are two database types:
- A Production database is seeded with the Default Workflow; see Default Workflow Configuration.
- An Evaluation database is seeded with sample data.
Creating the database produces its Database Access Key, which holds the server name, the database name, and the Database Account credentials. The wizard writes the key to the registry, saves a copy in the database, and exports it to a .reg file. Every computer that must reach the database (the Automation Server host, each web server, and each technician workstation running the Settings App) needs a registered copy, distributed as that .reg file or as an encoded string; see Database Access Key and Connections.
Before you begin
- A supported database engine: Microsoft SQL Server 2012, 2014, 2016, 2017, 2019, 2022, or 2025, each also in its Express edition, in a 32-bit or 64-bit version; Azure SQL Database; or Azure SQL Managed Instance. This requirement applies to on-premises installations; in Alloy Navigator Cloud, the provider meets it.
- The credentials of a SQL Server account with the
sysadminfixed server role on the target server. These credentials are used only for creating the database and are not stored.
In the Database Management wizard
Create a new database
The Alloy Control Panel lists the Database Management wizard on a computer where the wizard is installed. The wizard shows only the pages that apply to your choices.
- On the Task page, choose Create a new database ("Create a new database for production or evaluation purposes."). The page opens with Upgrade your existing database selected.
- On the Database Type page, choose Production or Evaluation.
- On the Database Server and Database page, enter the connection details of the SQL Server (SQL Server, Authentication, Login, Password) and the name of the new database in Database. For a non-standard port, enter the server as
SERVER,port. To also set the collation and the database files, select Configure advanced database properties (collation, storage, etc.). - If you selected the advanced properties, choose a collation in Name on the Database Collation page. The page advises you to choose the correct collation, because changing it would require a significant effort.
- If you selected the advanced properties and the target is not Azure SQL, define the files on the Database Files page. The Data files and Transaction log groups each list File Name, Location, and Initial Size (MB), with Add, Edit, and Delete commands; add secondary files here.
- If the FILESTREAM storage page appears, choose whether to enable FILESTREAM and set its folder; see Optional FILESTREAM storage.
- On the Database Account page, provide the credentials of the SQL Server account that Alloy Navigator will use to access the database. Authentication opens on SQL Server Authentication. The Login list shows the enabled logins of the chosen authentication type, except logins whose names begin with
##orNTor end with$. Choose an existing login in Login and enter its Password, or click Create SQL Server Account... to create a login. - On the Database Access Key page, view the key. The page also names the
.regfile the key is exported to; by default, the file is exported to your desktop. - On the Administrative Account page, choose Windows Authentication or Standard Authentication, and enter the Username, Password, and Confirm Password of the first administrative account. When the page first opens, it copies the authentication chosen on the Database Server and Database page and fills Username with the current Windows account or with the SQL login entered on that page.
- On the Administrator page, enter the person record associated with the administrative account: First Name, Last Name, Full Name, E-mail, and Business Phone. Only Full Name is required. To fill the form from Active Directory, click Browse Active Directory....
- On the Ready to Proceed page, click Back to review your choices, or click Next to start creating the database.
- On the Summary page, review the report, and click Finish.
What the wizard checks and shows along the way:
- Any connection: the wizard refuses a SQL Server older than 2012 with "Your version of Microsoft SQL Server is not supported. Use Microsoft SQL Server 2012 or later." It offers no way past this refusal.
- Database Server and Database: Next rejects an empty server, database, or login, and rejects a database name that contains
",:,', or`with "Invalid characters in the Database name." - Database Collation: Next does not continue until a collation is selected.
- FILESTREAM storage: when Enable FILESTREAM is selected and no folder is given, Next shows "The "Folder for FILESTREAM data" field is mandatory, it can't be left blank."
- Database Account: Next needs a login, and a password unless Windows authentication is chosen, and then tests the connection.
- Administrative Account: Next requires the user name and matching passwords. Under Windows authentication, the user name must contain a backslash (
\); otherwise the wizard shows "The account you have specified is not a Windows account. Please choose a Windows account." When the SQL Server supports only Windows authentication, the page shows "Your SQL Server doesn't support SQL Server Authentication." - Administrator: when the administrative account is a Windows account and you edited its user name, or no full name has been set yet, the wizard imports that account's person details from the directory when you leave the Administrative Account page, so the form is often already filled.
- Progress Status: this page shows a progress bar, Estimated time left, and Current operation. Back and Next are unavailable. Closing the window asks for confirmation and cancels the run.
- Execution Error: if creation fails, the wizard shows "The wizard couldn't complete the requested action due to an error. Remove the cause of the error and restart the wizard." with a View error details link and "Click Cancel to exit the wizard." If you canceled the run, it shows "The requested action was canceled by user." On this page, Next is unavailable; for a create, Back is available.
- Summary: after a create, the report lists the server, the database, the administrative account, the person, the Database Account login and authentication, and the file the Database Access Key was exported to. Back and Cancel are unavailable on this page. Once the database has a license, the page is titled Completion instead.
The administrative account has full administrative permissions to configure and manage Alloy Navigator, and it is also the first technician account. The wizard makes it a member of the built-in Administrator security role; see Security Roles.
Creation enables full-text search when full-text search is installed on the SQL Server instance.
When you close the wizard from the Summary page and the new database has no license yet, the wizard launches the Settings App with the new connection and the administrative account, and signs in automatically when a user name or Windows authentication is available. You apply the license there; see License Management.
Optional FILESTREAM storage
If you started the wizard from the command line with the /USEFILESTREAM switch, the target is not Azure SQL, and the SQL Server supports FILESTREAM, the FILESTREAM storage page follows; without the switch, the page does not appear. FILESTREAM stores attachments on the file system to improve streaming performance and reduce database size, and the page links to limitations and tips to review before you use it. To use FILESTREAM, select Enable FILESTREAM and enter a folder in Folder for FILESTREAM data, or click the button next to the field to choose one. The field is available only while Enable FILESTREAM is selected.
Create a SQL Server account for the Database Account
The Create SQL Server Account dialog opens from the Database Account page.
- In Authentication, choose the type of account.
- In Login, enter the login name. For a Windows account, you can click Find... to look it up.
- For a SQL Server login, enter the Password and Confirm Password, or click Generate to fill both with a generated password.
- Click OK. The wizard creates the login.
OK needs a login and, for a SQL Server login, two matching passwords that are not empty. If a login other than sa already exists, the wizard shows "This account already exists." and does not create it.
What the Database Account receives
The Database Account is the one SQL Server login that the rest of Alloy Navigator uses to reach the database. On creation, the wizard grants it db_owner on the new database and, except on Azure SQL Database, VIEW SERVER STATE and VIEW ANY DEFINITION at server level.
The Database Account also receives its rights on archive databases without any action from you:
- When the wizard issues the Database Access Key, it grants the Database Account
db_owneron every archive database on the same SQL Server instance, unless the login issaor is already the owner (dbo) of that archive database. - When an archiving job creates an archive database, it adds the Database Account to
db_datareaderanddb_datawriterin that database, unless the login is already its owner (dbo) or does not exist on that server. See Data Archiving.
Changing this login afterward requires a new Database Access Key, a reconfiguration of every service, and a change on every technician workstation. The Database Account is changed with the Manage your Database Access Key task; see Database Access Key and Connections.
Creating the database on Azure SQL
When the target is Azure SQL Database or Azure SQL Managed Instance:
- The Database Files and FILESTREAM storage pages are not shown.
- The wizard does not set the simple recovery model on the database.
- On Azure SQL Database, the Database Account does not receive the server-level
VIEW SERVER STATEandVIEW ANY DEFINITIONgrants, so it has fewer permissions than on an on-premises SQL Server. On Azure SQL Managed Instance, it receives them. - A database created on Azure SQL Database starts on the Basic service objective. For production, service tier S3 or greater is recommended.
- Ticket archiving is not supported on Azure.