|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, October 26, 2012 7:12 AM
Points: 3,
Visits: 6
|
|
Hello, hope someone can sort this out..
I have this strange issue in my setup. In my connection string I cannot connect with "SQL Server" driver but I can connect with "SQL Server Native Client 10.0" Both drivers are visible from within ODBC Administrator
"Driver={SQL Server Native Client 10.0};Server=dbMirror1,777;Failover_Partner=dbMirror2,777;Database=MyDB;Uid=dbuser;Pwd=password;Network=dbmssocn"
Setup: I have three Windows 2008 R2 servers All servers are in a workgroup 2 servers are running SQL 2008 R2 and have database-mirror setup 1 server running as withness
I want to be able to use the "SQL Server" driver.... Where should I start looking to solve it?
/Ole
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 3:08 AM
Points: 5,203,
Visits: 11,157
|
|
ole 8332 (10/11/2012) Hello, hope someone can sort this out..
I have this strange issue in my setup. In my connection string I cannot connect with "SQL Server" driver but I can connect with "SQL Server Native Client 10.0" Both drivers are visible from within ODBC Administrator
"Driver={SQL Server Native Client 10.0};Server=dbMirror1,777;Failover_Partner=dbMirror2,777;Database=MyDB;Uid=dbuser;Pwd=password;Network=dbmssocn"
Setup: I have three Windows 2008 R2 servers All servers are in a workgroup 2 servers are running SQL 2008 R2 and have database-mirror setup 1 server running as withness
I want to be able to use the "SQL Server" driver.... Where should I start looking to solve it?
/Ole The sql server driver does not support the failover partner parameter
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, October 26, 2012 7:12 AM
Points: 3,
Visits: 6
|
|
Hi Perry, This is strange because I have another environment that is 90% similar to this setup. There I am using the "SQL Server" driver!
I'll now try change to the native driver on the similar system in order to have those system indentical
Thank you  /Ole
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 9:55 PM
Points: 6,720,
Visits: 11,759
|
|
The driver named as "SQL Server" was released with SQL Server 2000. It's best to use a driver version consistent with the version of the SQL Server instance, else you cannot take advatage of newer features, including data types. The Native Clients are advertised as being backward compatible so you could get ahead of the curve and implement the SQL Server 2012 Native Client (11.0) and that should support whichever version of SQL Server you're using.
__________________________________________________________________________________________________ There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Believe you can and you're halfway there. --Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy
|
|
|
|