Re: Db connexion mode ???

That's an approach I discuss in the book. It can be easier to maintain but
it does require mixed-mode security. Another approach is to grant access to
a group to which the Windows users belong. See Chapter 9.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"calderara" <calderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5684F197-E8B5-4E26-8D37-850E3C02265E@xxxxxxxxxxxxxxxx
Thanks for your comments.

Does it make sense to you then if I define a single SQL login that each
exe
file will use instead of using windows credentials , as I am not
interresting
in any auditing ?

thanks
serge

"William (Bill) Vaughn" wrote:

In this case, the Connection pool (which resides on the client) is
created
for each client application--even if they are identical. The Connection
Pool
was designed to deal with ASP issues and does not really help Windows
Forms
application performance--as a matter of fact, it can hurt performance and
can cut back on the number of data access alternatives.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"calderara" <calderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5E0A1842-A393-4FC5-8DCA-7AAF93E9ECCC@xxxxxxxxxxxxxxxx
This is a windows forms application.
IN fact I have different windows forms application in separate exe file
each.
Each also make some requets to database

"William (Bill) Vaughn" wrote:

Ah, is this an ASP.NET application or a Windows Forms application? If
the
latter, the Connection pool is not a factor. Each process/program gets
its
own pool.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest
book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"serge calderara" <sergecalderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:3F10235E-E02D-4726-99E4-5E23A3E0F92B@xxxxxxxxxxxxxxxx
Dear all,

I have different .NET library which request a connection to an SQL
server
database.
As far as I understoo authentication methode for SQL, as long as we
have
windows oprating system everywhere we can select SSI authentication
methode
for the database connection string. But in case if I have 5
different
login
user connecting at the same time to the database using such method,
it
will
create 5 different connection string that will be aplce in the pool
(
if
pooling is sued right) right ?

So in oder to use a single connection string ro all my library
accessing
to
the sever, would it be more eficcient to define an SQL
authentication
method
with a unique user credential that everyone will use concurantly ?
Does this solution will simplify and improve connection performance
by
having such unique conenction string ? in that way we do not need to
handle
pooling.

As also I do not want to make any login tracing, windows
authentication
might not be necesary in that case.

Any comment ?

Thanks for help
Regards








.

Relevant Pages

  • Re: What are OleDbParameter names with Original_ prefix?
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Since the table has a primary key column, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: ADO.NET Transaction
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Client transactions put too much schema-dependent, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Performance problems with OracleDataReader
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... referencing the columns by ordinal is far faster than using strings. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Very slow
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ...
    (microsoft.public.sqlserver.ce)
  • Re: SQL Compact Edition - Connection Pool --> Slow!
    ... You might want to check out my EBook on SQL Server Compact. ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... mind (--> get a connection, use it and release it as soon as possible ...
    (microsoft.public.sqlserver.ce)
Loading