When you connect using Driver={SQL Server} you are using the SQL Server 2000
version of the SQL Server driver. SQL Server 2005 does accept such
connections. When you use Driver ={SQL Native Client} you are using is the
version that shipped with SQL Server 2005, and it understands all the new
features in SQL Server 2005. For instance, the older driver doesn't expect
to see an XML index (a feature added in SQL Server 2005), so if you connect
to a table that contains one, the XML index could confuse the driver. Since
there are many new features in SQL Server 2005, the newer SQL Native Client
is a safer choice.
Also, in many cases, the SQL Native Client will perform better. For
instance, it knows to use a shared memory connection when connecting
locally. The old driver will try to make a TCP/IP connection even when
connecting locally and that just slows performance.
To sum up, you can use the old driver if your database only has old
features. You are better off using the newer driver.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view] "ilkaos" <12wre12wq2@katamail.it> wrote in message
news:OCVtwQdyHHA.1168@TK2MSFTNGP02.phx.gbl...
> hi all,
> I have a vfp8 application that works with sql2000.
> now we have to use it with sql2005.
> the actual connestion string is lik
> Driver={SQL Server};
> Server=myserver;
> Database=mydb;
> Uid=myuser;
> PWD=mypwd;
>
>
> I have read in the books that for sql2005 I have to use
> Driver={SQL Native Client};
>
> and install the component from the sql2005 cd in the client pc.
>
> so i did and it works.
> But a person that uses the same program told me that there was no need of
> doing this and just keep
> using the connection string
> Driver={SQL Server};
>
> I could not believed him but I tried and...it works.
> so my questions are:
> - do I need to change the connection string or is it the same using the
> old one?
> - is there a difference in using one or the other...i mean if using SQL
> Server} on 2005 is
> less performant or with less possibilities?
>
> tia
>
>
"Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> ha scritto nel
messaggio news:75B1ACC5-8FFB-4AF4-AF83-E0832749B442@microsoft.com...
[quoted text, click to view] > When you connect using Driver={SQL Server} you are using the SQL Server
> 2000 version of the SQL Server driver. SQL Server 2005 does accept such
> connections. When you use Driver ={SQL Native Client} you are using is the
> version that shipped with SQL Server 2005, and it understands all the new
> features in SQL Server 2005. For instance, the older driver doesn't expect
> to see an XML index (a feature added in SQL Server 2005), so if you
> connect to a table that contains one, the XML index could confuse the
> driver. Since there are many new features in SQL Server 2005, the newer
> SQL Native Client is a safer choice.
> Also, in many cases, the SQL Native Client will perform better. For
> instance, it knows to use a shared memory connection when connecting
> locally. The old driver will try to make a TCP/IP connection even when
> connecting locally and that just slows performance.
> To sum up, you can use the old driver if your database only has old
> features. You are better off using the newer driver.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
thanks a lot fory your answer.
it is very illuminating for me.
p.s.
what does MSFT stand for?
