Does connectionString support SQL Server Database mirroring?

In the "Getting Started"http://www.entityspaces.net/documentation/getstarted.pdf. it is said:
"The connectionString is the connection string for your database. ... EntitySpaces does not use OLEDB"

What are the differences with OLEDB connection string ? 

In particular, will it support  "Failover Partner"?

In normal connection string we are using the following:

    <add key="ConnectionString" value="Data Source=IPAddress1;Failover Partner=IPAddress2;Initial Catalog=DBName;Trusted_Connection=Yes;" />

We use ADO.NET providers, they do not use OLEDB, OLEDB is basically an out-dated approach. MyGeneration uses it because OLEDB providers provide good meta data.  You really don't use OLEDB with EntitySpaces (except for Microsoft Access).

I'm not that familiar with mirroring.

http://www.mssqltips.com/tip.asp?tip=1289

But, what I take away from that article is that, since EntitySpaces uses ADO.NET, simply having "Failover Partner" in your EntitySpaces connection string should work. There is nothing our code needs to support. The driver does the redirection.

Since I do not see "Provider=SQLOLEDB.1;" in your connection string, I'm not sure where OLEDB comes in to play.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=421936&SiteID=1

Thanks, Mike and David.

Mike.Griffin:

We use ADO.NET providers,

After reading the phrase "EntitySpaces does not use OLEDB.", it was not clear for me, what do you use.

It will be good to add the clarification to "Getting Started" http://www.entityspaces.net/documentation/getstarted.pdf.  and provide link to http://msdn2.microsoft.com/en-us/library/ms254500.aspx (and may be in particular for SQL Server http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring.aspx.)

If you are connecting to Microsoft SQL we use their SqlClient ADO.NET provider.  OLEDB is an obsolete standard at this point.