What is difference between Session and Connection?

Question

1.00/5 (2 votes)

See more:

What is difference between Session and Connection? Could any one explain it in simple way. I read many articles but I didn't get it. The more I read, the more I am getting confused.

Thanks in advance,
Pushkar

Posted 30-May-15 23:21pm

Pushkar Prabhu

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2015-05-30T23:50:00

Let's take a step back, and ignore computers for a moment.

You want to drive to the shops.
To do this, you need to do two things:
1) Get into the car.
2) Use your driving skills to navigate your way.
These are separate "events" - there is no point in trying to navigate unless you are in the car! "Getting into the car" establishes a connection between you are the car, and while that connection exists, you can have a session of navigation. If at any point you get out of the car, you have broken the connection, and the navigation session ends.

From an SQL perspective, it's the same, your application establishes a connection to SQL Server - the "physical" link between them - and SQL Server establishes a Session within which you can issue commands over the connection. If at any time the connection is closed, your session ends - and if you are using Transactions for example, they will automatically be "rolled back" at that point because you didn't Commit them.

In reality, it's more complex than that - you can have more than one session per connection (but not the other way round, two connections cannot "share" a session) under some circumstances, and there are some conditions under which you can have a session without a connection.

But in practice (and for 99.99% of your working life) you can treat the two as the same: a connection establishes a session and the session ends when the connection is terminated.