Post reply

sp_who2 shows blank hostname

  • August 28, 2018 at 2:19 pm

    #378499

    Hello experts,

    There's an application change being done here and it involved a new host for the application that is pointing to our SQL Server. I now see two kinds of connections -
    1. Connections with a login_name and hostname filled in.
    2. Connections with the same login_name but where the hostname column is blank.

    I assume the connections with the blank hostname are stale connections that are still there because I did not disconnect them before (future checklist item, I know) - is that correct?
    If so, will they eventually die off on their own, or do I need to kill them? And is it safe to kill them?

    Thanks for any help.
    - webrunner

    -------------------
    A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
    Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

  • August 28, 2018 at 3:35 pm

    #2003736

    webrunner - Tuesday, August 28, 2018 2:19 PM

    Hello experts,

    There's an application change being done here and it involved a new host for the application that is pointing to our SQL Server. I now see two kinds of connections -
    1. Connections with a login_name and hostname filled in.
    2. Connections with the same login_name but where the hostname column is blank.

    I assume the connections with the blank hostname are stale connections that are still there because I did not disconnect them before (future checklist item, I know) - is that correct?
    If so, will they eventually die off on their own, or do I need to kill them? And is it safe to kill them?

    Thanks for any help.
    - webrunner

    No those aren't necessarily stale connections. Did you check if these are user or system processes?
    Query sys.dm_exec_sessions where is_user_process = 1

    Sue

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply