Programming - Best Practice

[bigHairy]

Hello.

I have been teaching myself .NET over the last few months and have had
some success. I would like to ask a question though...

A number of examples I have followed have the following in their
finally statement

Try
......
Catch
......
Finally

If (Not IsNothing(dbCon n)) Then
dbConn.Close()
End If

End Try

Will my data connection always close using this method or should I
just use dbConn.close?

I have a program that seems to be holding onto its connection - am I
missing something?

[PFC Sadr]

I've read 3 different figures for 'how much memory it takes on a db
server to leave a connection open'

I've got a couple of MS press books that claim 8kb.

I've got a couple of MS press books that claim 500kb.
and I just finished another SQL 2005 cert; and the figure that they
claimed there was 24k.

So if I've got a server with 1gb ram.. and a half dozen users.. what's
the big deal with leaving a half dozen connections OPEN?

it helps troubleshoot tremendously.

I mean.. how are you supposed to see sql statements when you can't
tell what spid they are?
I mean.. how are you supposed to see sql statements when you can't
tell what spid they are?
I mean.. how are you supposed to see sql statements when you can't
tell what spid they are?
I mean.. how are you supposed to see sql statements when you can't
tell what spid they are?
during development; ESPECIALLY-- it really helps to keep a half dozen
connections OPEN and see how things interact with each other; instead
of just 'close things as fast as you can and HOPE for the best'

that's what ADO.net is shoving down our throats.

'close connections as fast as you can and HOPE for the best'

and I don't believe in that type of 'fly by night' operation

if I wanted a nickel and dime data layer; I'd shop at Kmart
i used to have the choice to open a connection or close it. it was as
simple as changing a single variable in between a STRING and a
ADO.Connection.

i used to have the choice to open a connection or close it. it was as
simple as changing a single variable in between a STRING and a
ADO.Connection.

i used to have the choice to open a connection or close it. it was as
simple as changing a single variable in between a STRING and a
ADO.Connection.

i used to have the choice to open a connection or close it. it was as
simple as changing a single variable in between a STRING and a
ADO.Connection.

now?
MS FORCED THEIR PREMISE - that leaving connections open is bad- down
our throats.

AND I DO NOT ACCEPT THE ABILITY OF MS TO MAKE DECISIONS LIKE THIS
WITHOUT FIRST CONSULTING _ME_

Obviously they've proven that they are incapable of releasing stable
dependable software.
I mean, Visual Studio 2005 Pro, even with SP1 crashes 2 or 3 times a
day.

SO FUCK MS
On Feb 20, 5:59 am, "Michael D. Ober" <obermd.@.alum. mit.edu.nospam>
wrote:

There's another benefit to designing systems to open and close connections,
especially connections that sit idle most of the time. If your clients
assume that the connection is always open once it is opened, any burp that
causes the server to drop the connection will crash the client. If the
client doesn't make this assumption, a dropped connection is no big deal,
which also means the server can drop idle connections to free resources and
the client will simply reconnect when it needs to.

Mike Ober.

"CodeMonkey " <spamm...@suck. comwrote in message

news:um******** *****@TK2MSFTNG P04.phx.gbl...

PFC Sadr wrote:

I don't WANT to manually close it.
I want to leave it OPEN.

I don't see the point of opening it and re-opening it and all that
crap
and you can't utilize temp tables if your provider keeps on randomly
closing connections

uh; like seriously here

let's talk about programming apps for small business.
why would I constantly open and close and open and close connections??

This is especially important for small businesses. If a company has 10 PCs
that need to connect to an SQL server throughout the day, but not every PC
needs to look at the data all day, they might be able to get away with 5
licenses. If you keep those connections open the whole time the
application is open, you couldn't do that. We even have a company that
needs 8 people to connect to it constantly through the day. We close
connections and only open them when needed. They have 5 licenses and have
never had a problem. It's very cost effective.

It's also important for large companies. Having 100 connections open all
day is not very efficient when you can have 10 - 25 connections opening
and closing. Less load on the server...

It's just smarter and more efficient.- Hide quoted text -

- Show quoted text -

[aaron.kempf]

I fully agree.

I wish that MS had some sort of logic; instead of just forcing their
premonitions upon us


in ADO we can either use pooling or keep a connection open.

it it as easy as changing a single line of code and it's globally
changed EVERYWHERE

DREAM FUCKING WEAVER KIDS

they don't make you jump through hoops and play word games

fuck M$

On Feb 20, 10:20 pm, "PFC Sadr" <pfc_s...@hotma il.comwrote:

and it will keep the same SPID?

not the last time I checked.

why would a company invent a new library and then play word games like
this?

keeping a connection open shoudl keep the same SPID should it not?

On Feb 20, 5:06 am, "Brian Gideon" <briangid...@ya hoo.comwrote:

On Feb 20, 12:27 am, "aaron.ke...@gm ail.com" <aaron.ke...@gm ail.com>
wrote:

Cor

I don't understand what you're trying to say to me here.

Are you saying that you are GLAD that they automagically close
connections?

IT SHOULD BE OPTIONAL NOT MANDATORY

JUST LIKE IT WAS IN ADO; USING CONNECTION SHARING

Hi,

Like Spam said, closing a connection in ADO.NET is optional. You can
keep that IDbConnection object open as long as you'd like.

Brian- Hide quoted text -

- Show quoted text -