DSN connection to SQL Server

[Mark]

Are there any inherent issues with using a DSN connection on a windows
network from an ASP.NET web page to a SQL Server on the same windows network
(different box) using Windows Authentication? I'm aware of other options
(impersonation, delegation, asp.net account, etc), but wanted to hear about
problems one could run into using the DSN (performance, security,
configuration, etc). On the surface it appears that if we're ok with
configuring the DSN on each developer's box, on our test machine, and our
live box, this could be a pretty good option for a small (5+) team of
developers.

Thanks in advance.

Mark

 

[Kevin Spencer]

A System DSN is ODBC (Open Database Connectivity). ODBC is a wrapper for OLE
DB (Object Linking and Embedding for Databases). Therefore, ODBC uses more
resources than OLE DB, and OLE DB uses more resources than the native
SqlClient classes. So, if the shortest distance between 2 points is a
straight line, you're talking the LONGEST route.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

 

[Mark]

drat. Very useful information. Thanks Kevin.

I'm assuming this would apply to a File DSN as well?

Mark

 

[Kevin Spencer]

If it's a DSN, it's ODBC.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.