Watchdoc - Watchdocstats Database - SQL / PostgreSQL / SQLite

Principles

• In Watchdoc, printing activity is recorded in an SQL® or PostgreSQL® statistical database called Watchdocstats.

• This database is populated using data collected by Watchdoc via the SNMP protocol.

• The cross-server on-demand printing function also relies on an SQL-type statistical database.

• If you use quotas, these are based on another database called Watchdocpmv.

• The data is displayed in the Watchdoc administration interface but can also be analysed and exported via WDIS.

• Users can also view this data on their “My Account” page.

• The SQL database can also be used as a directory:

  • Users directory: In rare cases where the organisation does not have an LDAP directory, it can use an SQL table as a user directory (see Creating and configuring a user database).

  • Guests directory: By default, WSC provides a Guest database based on an SQL table. This directory is used to list users who are not included in the organisation’s directory but who must be recognised by Watchdoc in order to print (for example, a visiting partner, an intern, a contractor on a fixed-term assignment, etc. (see Managing the Guest Database).

  • PUK codes: This directory enables the generation of PUK codes for users registered in the Entra ID directory (Microsoft Azure). (See: Creating and configuring a PUK code database)

Compatibilities

The Watchdocstats and/or Watchdocpmv databases may be:

• MS SQL Server^® (Express/Standard/Enterprise) 2012, 2014, 2016, 2017, 2019 and 2022 ;

• PostgreSQL 17^®

• SQLite^®(version included in the Watchdoc installation package).
  

For further details, see Data Server Prerequisites.

Procedures

You must therefore install a database before installing Watchdoc. Unless you are installing the Watchdoc Express version, which automatically installs an MS SQL Express^® database.

To do this, please refer to:

• Database server requirements,

• Installation requirements and MS SQL^® packages,

• Creating the MS SQL^® database,

• Creating the PostgreSQL^® database,

• Connecting to and creating the SQL^® database during initial installation

Furthermore, as database data varies, query processing may be slowed down due to index fragmentation over time. We recommend that you regularly clean up your database by following the maintenance plan provided.

It is sometimes useful to back up the database so that it can be restored.

Finally, you may also need to transfer the database.