Which db connection is better? DSN vs. straight

[Aaron [SQL Server MVP]]

> hard code the connection into your code calling the servername and
database

> name directly (whether you place it in an include or in the Web.config

file)

> or you can call a DSN where the only thing you have to do is give it the

DSN

> 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.
[url]http://www.aspfaq.com/2126[/url]

--
[url]http://www.aspfaq.com/[/url]
(Reverse address to reply.)

[cheezebeetle]

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
of choice.

More discussion?

Brian



"Aaron [SQL Server MVP]" wrote:

> > hard code the connection into your code calling the servername and

> database

> > name directly (whether you place it in an include or in the Web.config

> file)

> > or you can call a DSN where the only thing you have to do is give it the

> DSN

> > 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.
> [url]http://www.aspfaq.com/2126[/url]
>
> --
> [url]http://www.aspfaq.com/[/url]
> (Reverse address to reply.)
>
>
>

[Bob Barrows [MVP]]

cheezebeetle wrote:

>
> 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
> of choice.
>

You failed to follow this link in the article:
[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/ado_deprecated_components.asp[/url]

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[joker]

Don't forget that ODBC uses more processor time then native jet drivers.

So stop using it. You will see an improvement in the speed of you
database applications when you do.

cheezebeetle wrote:

> 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
> of choice.
>
> More discussion?
>
> Brian
>
>
>
> "Aaron [SQL Server MVP]" wrote:
>
>

>>>hard code the connection into your code calling the servername and

>>
>>database
>>

>>>name directly (whether you place it in an include or in the Web.config

>>
>>file)
>>

>>>or you can call a DSN where the only thing you have to do is give it the

>>
>>DSN
>>

>>>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.
>>[url]http://www.aspfaq.com/2126[/url]
>>
>>--
>>[url]http://www.aspfaq.com/[/url]
>>(Reverse address to reply.)
>>
>>
>>