|
Home > Archive > MS SQL Server > October 2006 > Connections
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Erencan SA�IRO�LU 2006-10-28, 7:14 pm |
| Hi Folks,
I have a question. I've developed a desktop application. But i can't decide
sql server connection strategy. The application uses by 15-20 Windows client
and it connects to same sql server.
What am i do ?
1- I can open connection start of the program and close when program is shut
down.
2- I can open connection when i need a connection and i can close
connection when i executed sql statements.
Do you have any idea?
Thanks.
| |
| John Bell 2006-10-28, 7:14 pm |
| Hi
In general two-tier applications tend to use a single connection for the
application runtime, web applications tend to use connection pooling and
close the connection. Your application seems to be best suited to the single
connection strategy. See my other reply for some links about these.
John
"Erencan SAÐIROÐLU" wrote:
> Hi Folks,
> I have a question. I've developed a desktop application. But i can't decide
> sql server connection strategy. The application uses by 15-20 Windows client
> and it connects to same sql server.
> What am i do ?
> 1- I can open connection start of the program and close when program is shut
> down.
> 2- I can open connection when i need a connection and i can close
> connection when i executed sql statements.
>
> Do you have any idea?
>
> Thanks.
>
>
>
| |
| Erencan SAĞIROĞLU 2006-10-28, 7:14 pm |
| John Bell wrote:[color=darkred
]
> Hi
>
> In general two-tier applications tend to use a single connection for the
> application runtime, web applications tend to use connection pooling and
> close the connection. Your application seems to be best suited to the single
> connection strategy. See my other reply for some links about these.
>
> John
>
> "Erencan SAÐIROÐLU" wrote:
>
Thanks John for all answers. :)
|
|
|
|
|