Connection Type for ODBC Link to SQL/ADP

[MattieG]

Hi

I currently have about 30 clients connecting to an SQL server using an
ODBC link connecting by NT login.
If I changed all these logins to an SQL login would it cut down the
number of current connections on SQL server and would this give me any
benefit?

I also have about 20 ADP cliens connecting using NT Login name and was
wonderring if I also changed these to the SQL login it would also cut
down on connections?

Any help or information would be appreciated.

Mattie
Chester Zoo

 

[Tom van Stiphout]

On Mon, 12 Nov 2007 02:30:12 -0800, MattieG

No. You would just have the same number of connections but this time
using the same SQL Server login.
SQL Server can EASILY handle 30 connections, even with one hand tied
on its back.

-Tom.

 

[MattieG]

On Mon, 12 Nov 2007 02:30:12 -0800, MattieG


No. You would just have the same number of connections but this time
using the same SQL Server login.
SQL Server can EASILY handle 30 connections, even with one hand tied
on its back.

-Tom.








- Show quoted text -

Hi

Would connection pooling with the ODBC links help though?

Mattie

 

[Sylvain Lafontaine]

While not zero, the amount of work done by SQL-Server to open and keep a
connection is usually very small in comparaison to other types of work like
retrieving the result of a query. If you are starting experiencing
performance problem with your sql-server, you are most likely to gain
benefit by looking at other types of optimization (like make sure that you
have all (and only) the needed indexes, don't have bad query plans on a too
high frequency, buy a bigger/better machine, etc. than by looking at the
type of connection/login used.

Missing indexes, bad indexing and bad query plans are usually the first
things to look at in order to optimize a SQL-Server installation but you
must not forget to have a good maintenance plan (reindexing, etc.) and make
sure that your design is OK, too.

You should ask this type of question in the newsgroup m.p.sqlserver.server.

 

[Tom van Stiphout]

On Mon, 12 Nov 2007 07:25:02 -0800, MattieG

Connection pooling is not a bad idea, but also not something the
average developer has to worry about. Your tools provide it, or they
don't. Again, 30 connections is no big deal. You can make much more
severe performance errors with a bad database design.

-Tom.