Skip to main content

Setting Up SQL Server for ScrewDrivers

ScrewDrivers Pro and Enterprise store configuration, printer assignments, profiles, and reporting data in a Microsoft SQL Server database. This guide takes you from "we don't have SQL Server" (or "we have one, how do we point ScrewDrivers at it?") to a database ready for the ScrewDrivers Database installer.

Choosing a SQL Server edition​

ScrewDrivers requires Microsoft SQL Server 2012 or newer, in any edition:

  • SQL Server Express (free) — suitable for small to medium deployments, up to roughly 500 users. If you don't already run SQL Server, this is the usual choice.
  • SQL Server Standard — for enterprise deployments and high-availability scenarios.
  • SQL Server Enterprise — required for AlwaysOn Availability Groups; see SQL Always On Compatibility.

You don't create the ScrewDrivers database by hand — the ScrewDrivers Database installer creates it (and later upgrades its schema) for you. Your job is to have a reachable SQL Server and an account with sufficient rights.

Installing SQL Server Express​

If you're standing up SQL Express for ScrewDrivers, the defaults get you most of the way. Three settings matter:

  1. Authentication mode: choose Mixed Mode (Windows + SQL Server authentication). This gives you the widest flexibility — unattended ScrewDrivers services authenticate with SQL or Static Windows credentials, while interactive tools can use Windows authentication. See Choosing Database Credentials and Authentication for how ScrewDrivers uses each mode.
  2. Enable TCP/IP: in SQL Server Configuration Manager under SQL Server Network Configuration → Protocols, enable TCP/IP and restart the SQL Server service. ScrewDrivers components connect over the network, and Express disables TCP/IP by default.
  3. SQL Server Browser: if you'll connect by named instance (Express installs as <host>\SQLEXPRESS by default), set the SQL Server Browser service to start automatically so clients can resolve the instance.

Download SQL Server Express from Microsoft.

Permissions: one elevated step, then least privilege​

ScrewDrivers v7 separates database permissions cleanly:

  • The ScrewDrivers Database installer — run once per environment — performs every high-permission action: creating the database, initializing it, and upgrading the schema on later releases. Run it with an account that can create databases on the target server. It also initializes ScrewDrivers Administration's built-in authorization.
  • Everything else needs only basic read and write access to the Tricerat database. The main ScrewDriversProOrEnterprise installer and the runtime components never require elevated database rights.
  • Stored procedure execution: if your DBA scopes permissions tightly, grant execution rights with the db_executor role.

Connecting: server names, ports, instances, and aliases​

When a ScrewDrivers installer asks for your SQL Server, the name syntax is:

<host name or IP><, port number><\instance name>
  • Default port: SQL Server listens on TCP 1433 by default. If yours listens elsewhere, append the port: TRICERAT-SQLDB,11119.
  • Named instances: connect as <host>\<instance> (for example dbserver\SQLEXPRESS). The SQL Server Browser service resolves the instance to its port.
  • Port beats instance: if you supply both a port and an instance name, SQL Server ignores the instance name and uses the port. Pick one style.
  • Database server aliases: fully supported — ScrewDrivers needs no special configuration. Aliases let your DBA re-host the database later without touching ScrewDrivers connection settings.
  • Firewalls: allow the SQL port (1433 or your static port) from every machine running a ScrewDrivers component that reaches the database, plus UDP 1434 if you rely on the SQL Server Browser.

Microsoft's references: configure SQL Server to listen on a specific port and server aliases.

Changing the connection later​

Moved, renamed, or re-credentialed the database after installation? You don't reinstall — use the ScrewDrivers Database Connection tool. Changing SQL Access Data After Your Install covers it.