Skip to main content

Connection and Sessions


What is the differences between Connection and Sessions in SQL-Server?

The CONNECTION is the physical communication channel between SQL Server and the applications: the TCP socket, the named pipe, the shared memory . The connections show only external connections and each connection has an spid.

select a.spid , a.nt_username , a.loginame , a.program_name from sys.sysprocesses a , sys.dm_exec_connections b where a.spid=b.session_id

A SESSION is a semi-permanent interactive information interchange, between two or more communicating devices  or between an application and users.

We must open a connection in order to create a session. Normally there is one session on each connection, but there could be multiple session on a single connection.

eg. If we connect to sql server using management studio then its one connection. once we connected we can  open 3 query windows then these are 3 sessions.

Microsoft  SQL-Server has two DMVs to maintain Sessions and Connections :-

1.       Sys.dm_exec_sessions
2.       sys.dm_exec_connections


Happy Reading
Sumanjha_Accidental_Dba

Comments

  1. I really like what you guys are usually up too. Such clever work and coverage!

    Keep up the terrific works guys I've included you guys to blogroll.


    my web-site: duvet covers queen

    ReplyDelete
    Replies
    1. Thank you so much friend such a nice comment on my post.. you really encourage my works...

      Delete
  2. Heya this is kind of of offf topic but I was wanting to know if blogs
    use WYSIWYG editors or if you have to manually code with HTML.

    I'm starting a blog soon but have no coding skills so I wanted to get
    advice from someone with experience. Any hewlp would be enormously appreciated!


    my web-site - queen duvet covers

    ReplyDelete
  3. Asking questions are really pleasant thing if you are not understanding something
    totally, but this article presents good understanding even.

    Here is my homepage; kids comforter sets

    ReplyDelete

Post a Comment

Plz dont forget to like Facebook Page..
https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

Popular posts from this blog

How to encrypt and decrypt Table data in postgres

For encrypting and decrypting , we must use the bytea data type on the column which we implement. Bcoz bytea will use the pgcrypto method by default. However, you will need to create the pgcrypto extension to enable these functions as they are not pre-defined in PostgreSQL/PPAS. Example CREATE EXTENSION pgcrypto; CREATE TABLE userinfo (username varchar(20), password bytea); >>    Inserting the data in an encrypted format INSERT INTO userinfo VALUES(' suman ',encrypt('111222','password','aes')); select * from userinfo ; >>    Retrieving the data as decrypted format SELECT decrypt(password,decode('password','escape'::text),'aes'::text) FROM userinfo; Thanks for reading Plz dont forget to like Facebook Page.. https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

How to recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element xx.xxx.xx:function .dbo.xxx has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally