Connection strings.

Hi all,
Okay, a few questions. What is the difference between the following, and
which should I use?
1) Server=DBSERVER;Database=DATABASE;uid=UI
D;pwd=PWD
and ...
2) Provider=SQLOLEDB; Data Source=DBSERVER;Initial Catalog=DATABASE; User
Id=UID; Password='PWD'
Turns out that our ASP.NET pages were using #1, and ASP #2. However,
someone just changed our ASP pages to use #1, and we've been noticing some
strange issues (one of our clustered database servers went offline yesterday
and didn't fail over).
We're using SQL 2000 on Windows 2000 Server, and some ASP and ASP.NET pages.
Thanks for the help.
WadeCheck out:
http://www.connectionstrings.com/
http://www.carlprothman.net/Default.aspx?tabid=81
Anith|||I've been to both places -- while they have a lot of examples, do they
really discuss the differences between the different connection strings? I
certainly didn't notice any discussion.
"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:eNz5$2N0FHA.3896@.TK2MSFTNGP10.phx.gbl...
> Check out:
> http://www.connectionstrings.com/
> http://www.carlprothman.net/Default.aspx?tabid=81
> --
> Anith
>|||The first one seems to be using an ODBC string while the second one uses a
OLEDB provider connection string.
Since ODBC is almost deprecated and its drivers not being updated these days
by MS, it is recommended that you favor OLEDB for your data access. Do a
search on MSDN or technet and you'll get all the information you need on
these API specs.
Anith|||Wade,
Might try here as well:
http://msdn.microsoft.com/data/Default.aspx
HTH
Jerry
"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:eNBwoBO0FHA.908@.tk2msftngp13.phx.gbl...
> The first one seems to be using an ODBC string while the second one uses a
> OLEDB provider connection string.
> Since ODBC is almost deprecated and its drivers not being updated these
> days by MS, it is recommended that you favor OLEDB for your data access.
> Do a search on MSDN or technet and you'll get all the information you need
> on these API specs.
> --
> Anith
>|||Thanks for all the help, guys!
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23LuF8DO0FHA.2792@.tk2msftngp13.phx.gbl...
> Wade,
> Might try here as well:
> http://msdn.microsoft.com/data/Default.aspx
> HTH
> Jerry
> "Anith Sen" <anith@.bizdatasolutions.com> wrote in message
> news:eNBwoBO0FHA.908@.tk2msftngp13.phx.gbl...
>|||In ASP.NET, the data access is very likely using ADO.NET SqlClient
namespace, which is specifically designed for SQL Server access. Therefore,
in connectionString you only need to specify database name and server name,
SqlClient.Connection object knows which PROVIDER to use. While #2 is used in
ASP, its data access could be ADO, ODBC... depending on the developer's
choice. Usually, "Provider" is specified in ConnectionString in this case.
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:e$DhJzN0FHA.2652@.TK2MSFTNGP14.phx.gbl...
> Hi all,
> Okay, a few questions. What is the difference between the following, and
> which should I use?
> 1) Server=DBSERVER;Database=DATABASE;uid=UI
D;pwd=PWD
> and ...
> 2) Provider=SQLOLEDB; Data Source=DBSERVER;Initial Catalog=DATABASE;
> User Id=UID; Password='PWD'
> Turns out that our ASP.NET pages were using #1, and ASP #2. However,
> someone just changed our ASP pages to use #1, and we've been noticing some
> strange issues (one of our clustered database servers went offline
> yesterday and didn't fail over).
> We're using SQL 2000 on Windows 2000 Server, and some ASP and ASP.NET
> pages.
> Thanks for the help.
> Wade
>