How to find out who is connected to database?

Polar
Polar Member Posts: 32
edited 2004-07-29 in Navision Attain
Navision Attain 3.60 on SQL 2000.
Sometime I need to restart server where SQL is installed.
How to find out users connected by Navision Client to call them and say something like
"don't worry, be happy" server.RESET :D
May be somewhere in Navision is a tool to send messages to active users
like in Axapta?
keep it simple

Comments

  • fb
    fb Member Posts: 246
    I presume you already know about the menu path 'File, Database, Information', Sessions tab, and the drill down on 'Current Sessions'.

    If calling the users one at a time is insufficient, you could create a report (or other process) based on the 'Session' virtual table no. 2000000009.

    In some version (? 3.70 SQL ?) you can forcefully disconnect a user by deleting their entry in the Session table! -- Very rude, but sometimes necessary!

    Coming in v4.0 -- same session kill feature for the Navision db server, along with an 'Idle Time' field in the Session table.
  • dmccrae
    dmccrae Member, Microsoft Employee Posts: 144
    There's nothing like this right now.

    Just for your information, in 4.0 for SQL there is a method of doing something similar. You can create a stored procedure that is executed when every user logs in. It can display an informational message ('server shuting down for maintenance at 18:00') or can deny login altogether - for all users or particular users.
    Dean McCrae - Senior Software Developer, NAV Server & Tools

    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Polar
    Polar Member Posts: 32
    Hello, fb
    I thought in file->database->information I'd see userid of users connected
    but there are about a hundred sessions where userid is the same - SA
    One session was marked as "my session", but userid was SA , Application
    MS SQLEM , not Navision Attain Client , database MASTER. I connect to SQL using my own login, not SA, and database not MASTER.
    may be something is wrong in russian localisation or database authentication?
    Has anyone an idea?
    keep it simple

Categories