connection problems
connection problems
I'm still having a problem with the SQLNCLI.1 provider. On some stations, I cannot connect with this provider to sql server, I only get a message "ms sql not found". Such message does not say much to me. Do you have an idea, what should I look for to make this provider work? With sqloledb.1 I get the connection without any problems...
This message means that the SQL Native client is not installed on that workstations. You can download and install it from the Microsoft site. This client is also included into SQL Server installation.
In SDAC 4 you can set the Provider option of TMSConnection to prAuto. In this case SDAC will try to use SQL Native Client only if it is possible, otherwise it will automatically switch to the OLE DB provider.
In SDAC 4 you can set the Provider option of TMSConnection to prAuto. In this case SDAC will try to use SQL Native Client only if it is possible, otherwise it will automatically switch to the OLE DB provider.
Setting this "provider" option to "prAuto" is equivalent to omitting the "provider=...." part of the connection string, right?
With this provider option set to prAuto - is there a way to detect the actually selected provider (after the connection is opened)? This could be very useful for debugging - to know, what is the actual provider.
For the sql native client i have to specify the "autotranslate=false" option, whereas with sqloledb i don't (i have never tested sqloledb with autotranslate=false). Do you think, is it safe for me to use the prAuto provider with the autotranslate=false option?
With this provider option set to prAuto - is there a way to detect the actually selected provider (after the connection is opened)? This could be very useful for debugging - to know, what is the actual provider.
For the sql native client i have to specify the "autotranslate=false" option, whereas with sqloledb i don't (i have never tested sqloledb with autotranslate=false). Do you think, is it safe for me to use the prAuto provider with the autotranslate=false option?
You can check the version of the current provider using the TMSConnection.ClientVersion public property. For SQL Native client it starts with 9.x, for OLE DB provider i starts with 8.x.
Yes, there should not be any problems using this combination.Ludek wrote:Do you think, is it safe for me to use the prAuto provider with the autotranslate=false option?