syslogins

master database only

Description

syslogins contains one row for each valid Adaptive Server user account.

Columns

The columns for syslogins are:

Name

Datatype

Description

suid

int

Server user ID.

status

smallint

Status of the account (see Table 1-17).

accdate

datetime

Date totcpu and totio were last cleared.

totcpu

int

CPU time accumulated by login.

totio

int

I/O accumulated by login.

spacelimit

int

Reserved.

timelimit

int

Reserved.

resultlimit

int

Reserved.

dbname

sysname null

Name of database in which to put user when connection established.

name

sysname

Login name of user.

password

varbinary(128) null

Password of user (encrypted).

language

varchar(30) null

User’s default language.

pwdate

datetime null

Date the password was last changed.

audflags

int null

User’s audit settings.

fullname

varchar(30) null

Full name of the user.

srvname

varchar(30) null

Name of server to which a passthrough connection must be established if the AUTOCONNECT flag is turned on.

logincount

smallint null

Number of failed login attempts; reset to 0 by a successful login.

procid

int null

Stores the login trigger registered with the login script option in sp_modifylogin

lastlogindate

datetime

Timestamp for the user’s last login.

crdate

datetime

Timestamp when the login was created.

locksuid

int

The server user ID (suid) responsible for locking the login.

lockreason

int

Reasons for lock; one of:

  • NULL – account has not been locked

  • 0 – locksuid locked the account by executing sp_locklogin

  • 1 – locksuid locked the inactive account by executing sp_locklogin 'all', 'lock', 'ndays'

  • 2 – Adaptive Server locked the account because the number of failed login attempts reached max failed logins.

  • 3 – locksuid locked the account because the password downgrade period has ended and a login or role was not transitioned to SHA-256

lockdate

datetime

Timestamp when the login was locked.

On the Adaptive Server distribution media, syslogins contains an entry in which the name is “sa”, the suid is 1, and the password is null. It also contains the entry “probe” with an unpublished password. The login “probe” and the user “probe” exist for the two-phase commit probe process, which uses a challenge and response mechanism to access Adaptive Server.

Table 1-17 lists the bit representations for the status column:

Table 1-17: status control bits in the syslogins table

Decimal

Hex

Status

2

0x2

Account is locked.

4

0x4

Password has expired.

8

0x8

User has RepSrv authorization.

16

0x10

OMNI:autoconnect mode is enabled.

32

0x20

May use Adaptive Server internal authentication mechanism – syslogins.

64

0x40

May use LDAP external authentication.

128

0x80

May use PAM external authentication

256

0x100

May use Kerberos external authentication

Indexes