How to set max connections?

I'm use class.forName to load SQLServerDriver. If I want to set the max
connections to other than the default, how do I do that?
Thanks,
-- Frank
Frank wrote:

> I'm use class.forName to load SQLServerDriver. If I want to set the max
> connections to other than the default, how do I do that?
> Thanks,
> -- Frank
What is 'max connections'? It is not a driver property that I know of...
Joe Weinstein at BEA
|||Hello Frank,
I think you are talking about the server-side setting called "user
connections". There is no client-side property that you can set to do the
same.
You can configure this value from Enterprize Manager on the Connections tab
or with a
sp_configure 'user connections' statement in Query Analyzer. Please see the
"user connections Option" Books Online topic for more important information
about this setting.
Thanks,
Kamil
Kamil Sykora
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/securXity.
| Thread-Topic: How to set max connections?
| thread-index: AcWMfQTydRvRJc6qT2ieYQQnWcyC1g==
| X-WBNR-Posting-Host: 204.64.62.132
| From: "=?Utf-8?B?RnJhbms=?=" <Frank@.discussions.microsoft.com>
| Subject: How to set max connections?
| Date: Tue, 19 Jul 2005 09:15:03 -0700
| Lines: 5
| Message-ID: <39B925FA-078E-4F4C-AD28-3DA12EF8E20C@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.jdbcdriver:1201
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I'm use class.forName to load SQLServerDriver. If I want to set the max
| connections to other than the default, how do I do that?
|
| Thanks,
| -- Frank
|

How to set default SQL Timeout

I have an app that uses ADO connections, and when I run a particular
operation I get a SQL Timeout, but when I run the same operation with the
same executable on another client I don't get a timeout. A Profiler trace
confirms that the first query times out after 30 seconds (the default), and
the second client succeeds after about 40 seconds. Both clients are running
the same MDAC version.
I thought that the query timeout is set in the ADO command object, but this
behavior leads me to think otherwise. Is there a way to set the default
timeout value on a client?
Thanks,
Tom
Well, I've partially explained my own problem. The client that isn't timing
out is running on the server using the shared memory protocol LPC. When I
disable that and force the connection to use TCP/IP or named pipes, then I
get the SQL Timeout. So now my question is why is there a different timeout
value for TCP/IP and named pipe connections than there is for shared memory
connections?
Tom
"Tom" wrote:

> I have an app that uses ADO connections, and when I run a particular
> operation I get a SQL Timeout, but when I run the same operation with the
> same executable on another client I don't get a timeout. A Profiler trace
> confirms that the first query times out after 30 seconds (the default), and
> the second client succeeds after about 40 seconds. Both clients are running
> the same MDAC version.
> I thought that the query timeout is set in the ADO command object, but this
> behavior leads me to think otherwise. Is there a way to set the default
> timeout value on a client?
> Thanks,
> Tom

How to set default SQL Timeout

I have an app that uses ADO connections, and when I run a particular
operation I get a SQL Timeout, but when I run the same operation with the
same executable on another client I don't get a timeout. A Profiler trace
confirms that the first query times out after 30 seconds (the default), and
the second client succeeds after about 40 seconds. Both clients are running
the same MDAC version.
I thought that the query timeout is set in the ADO command object, but this
behavior leads me to think otherwise. Is there a way to set the default
timeout value on a client?
Thanks,
TomWell, I've partially explained my own problem. The client that isn't timing
out is running on the server using the shared memory protocol LPC. When I
disable that and force the connection to use TCP/IP or named pipes, then I
get the SQL Timeout. So now my question is why is there a different timeout
value for TCP/IP and named pipe connections than there is for shared memory
connections?
Tom
"Tom" wrote:

> I have an app that uses ADO connections, and when I run a particular
> operation I get a SQL Timeout, but when I run the same operation with the
> same executable on another client I don't get a timeout. A Profiler trace
> confirms that the first query times out after 30 seconds (the default), an
d
> the second client succeeds after about 40 seconds. Both clients are runni
ng
> the same MDAC version.
> I thought that the query timeout is set in the ADO command object, but thi
s
> behavior leads me to think otherwise. Is there a way to set the default
> timeout value on a client?
> Thanks,
> Tom

How to set default SQL Timeout

I have an app that uses ADO connections, and when I run a particular
operation I get a SQL Timeout, but when I run the same operation with the
same executable on another client I don't get a timeout. A Profiler trace
confirms that the first query times out after 30 seconds (the default), and
the second client succeeds after about 40 seconds. Both clients are running
the same MDAC version.
I thought that the query timeout is set in the ADO command object, but this
behavior leads me to think otherwise. Is there a way to set the default
timeout value on a client?
Thanks,
TomWell, I've partially explained my own problem. The client that isn't timing
out is running on the server using the shared memory protocol LPC. When I
disable that and force the connection to use TCP/IP or named pipes, then I
get the SQL Timeout. So now my question is why is there a different timeout
value for TCP/IP and named pipe connections than there is for shared memory
connections?
Tom
"Tom" wrote:
> I have an app that uses ADO connections, and when I run a particular
> operation I get a SQL Timeout, but when I run the same operation with the
> same executable on another client I don't get a timeout. A Profiler trace
> confirms that the first query times out after 30 seconds (the default), and
> the second client succeeds after about 40 seconds. Both clients are running
> the same MDAC version.
> I thought that the query timeout is set in the ADO command object, but this
> behavior leads me to think otherwise. Is there a way to set the default
> timeout value on a client?
> Thanks,
> Tom