Interesting, but all I am seeing is "management issues" if you don't own the
server. I do. If you have connections to multiple dbs then you must have
multiple datasource files (includes), which require you to make a change in
your actual code, when migrating from dev. to staging to production.
Everytime you make this migration for a new/updated complete site or
new/updated section you have to go into the code and change it. As opposed
to setting the dsn up once, with the same name across all servers.
What about security. Having the DSNless connection string carrying the
connection info such as username and password is dangerous as well. But of
course DSN connections have their security concerns too.
ODBC is deprecated? Meaning what exactly? MS doesn't recommend it anymore?
I would like to hear a little more "reasons" behind each for justification
"Aaron [SQL Server MVP]" wrote:
> database> > hard code the connection into your code calling the servername and> file)> > name directly (whether you place it in an include or in the Web.config> DSN> > or you can call a DSN where the only thing you have to do is give it the>> > name (you can add db name, username and password if you need to). The DSN
> > connection then relies on the ODBC connector you created earlier.
> ODBC is deprecated. Use OLEDB / DSN-less whenever possible.
> (Reverse address to reply.)