Honeywell K14392V1 manual Multi Database Security, SQL-Server Option

System Administrator’s Guide

Multi Database Security

Flexibility in security

Like most Multi-Media security features, using network means to protect a Multi database is optional. If the Multi db is protected, Multi-Media unit operators need read/write permissions to a Multi db.

Protecting the database from deletion

The Multi db can be protected using server file system capabilities. As a preventive measure against the accidental deletion of a Multi db, back it up and use network settings (such as NTFS security). See also Deleting a Database on p. 245.

Password security

Passwords are encrypted in Multi db files (*.mdb and *.mdf).

Protecting the database from copying

It is important to protect your Multi db from copying, if only to avoid its use by external unauthorized users, who could also be licensed Multi software users.

SQL-Server Option

Security option for SQL-Server

To add security to a Multi database, your SQL database administrator can setup a SQL login just for Multi users. By default, Multi software connects to a server running SQL-Server by using ‘sa’ as a logon account, with no password.

SQL-server Type Logon, Reserved for Multi Operators

Tip

1.Run SQL Server Enterprise Manager.

2.Add a new log on.

3.The “public” and “db_owner” database roles need to be assigned to the log on, so that a user can connect to the Multi db, update it and—if Multi SAs are to use Admin to create a Multi db—create a new SQL-based Multi db.

Creating a SQL-server type logon is a procedure for a SQL-Server administrator, not for Admin users or View operators.

Result

When these changes are made to SQL-Server security, a “log on to SQL” window appears, as in figure 10–1.The Login and Password of SQL can differ from the User ID and Password of a Multi account.

Document K14392V1 Rev A	165
07/07