The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
OLEDB and SQL NATIVE CLIENT (SQL 2005 database instance)
Posted: 21 Oct 09 9:13 AM
|
Hi there, i have a question. I've been working with SLX V6 for a long time, now it has been the time to move to version 7.5
I found a extrange thing, that maybe you can explain me better..
After the install of the SLX, i have the EVAL and EMPTY databases attached in the "Saleslogix Connector Manager" using SQLOLEDB.1
BUT if want to create a new connection, the only available connections are SQLNCLI.1 (SQL native client)
No other OLE DB provider is shown on the list.
I installed directly fro the install CD the SLX OLEDB client, but still it doesn't appears on the list..
Question is: is that OK?, version 7.5 SP1 of SLX running against an SQL 2005 server as it's data base only works with SQL native client?
Someone told me that SQL2005 needs that to connect to it, so whatever application that tryes to connect to SQL 2005, should use that provider and no other..
Is that OK?.. or i have something wrong on my system?
Thanks and best regards |
|
|
|
Re: OLEDB and SQL NATIVE CLIENT (SQL 2005 database instance)
Posted: 21 Oct 09 9:45 AM
|
The server connection to the database (as configured in Connection Manager) can be either SQL OLEDB or SQL Native Client, though I think I read somewhere that SQL Native Client is preferred for performance reasons.
The SLX OLEDB provider is used for the connection between the client and the SLX server, as configured in the Data Link Manager. |
|
|
|
Re: OLEDB and SQL NATIVE CLIENT (SQL 2005 database instance)
Posted: 21 Oct 09 11:54 AM
|
Thanks Phil,
I also read in other posts, that OLEDB is NO LONGER SUPPORTED (Server to SQL connection) in 7.5 SP1 ...now it's going to be SQL native client to do that connection between SLX SERVER and SQL SERVER.
Regards |
|
|
|
Re: OLEDB and SQL NATIVE CLIENT (SQL 2005 database instance)
Posted: 21 Oct 09 12:40 PM
|
Also, keep in mind that you will need to install the SQL Client on each machine that connects to SLX.
A Network user will instantiate the OLEDB Provider, which will open a Native Connection to the Database using the same properties as defined on the Server, and since the connection utilizes an specific SQL Client, you need to have that SQL Client on each client machine. |
|
|
|
Re: OLEDB and SQL NATIVE CLIENT (SQL 2005 database instance)
Posted: 15 Jun 10 3:36 PM
|
Sorry to revive an old thread, but this seems closest to my problem.
Sql 2000. I have a production and test database on the same server. Different attachment/logging paths. Upgraded the server from 6.2 to 7.5 SP2.
The existing oleDB connection used for live works. I created a new data link in the connection manager for the test environment as sql native client. Everything seemed to connect ok from this screen. Now whenever I try to create this connection from a client I only see the slxoledb as the connection provider (installed sql native client on client machine). If I put in the connection details anyway and select the test connection in the saleslogix database name, I get an "unable to initialize data directory" error when I test.
Does anyone have any ideas?
Thanks, Jim |
|
|
| |
|
Re: OLEDB and SQL NATIVE CLIENT (SQL 2005 database instance)
Posted: 15 Jun 10 3:48 PM
|
I realize that it isn't officially supported, but when I spoke w/ Saleslogix support they stated the main reason it wasn't supported was that MS was no longer supporting Sql 2000. I've actually done the upgrade and we've been running fine on Sql 2000 for months now in 7.5 SP2. The problem seems to be adding a second connection to the existing database server.
Are you telling me sql native client doesn't work on Sql Server 2000? |
|
|
| |
| |
|
Re: OLEDB and SQL NATIVE CLIENT (SQL 2005 database instance)
Posted: 15 Jun 10 3:59 PM
|
| Ok thanks Phil and Raul. I see I'm going to have problems now that I'm at a version that SLX is forcing me to use the sql native client to build new connections. I'm assuming the connection information is in the registry. Do you think it would be possible to copy the live connection's registry key(s) and modify it for the test environment without introducing other problems? Is there any place other than the registry where server-side connection information is stored? |
|
|
|
Re: OLEDB and SQL NATIVE CLIENT (SQL 2005 database instance)
Posted: 15 Jun 10 4:09 PM
|
The connection Information is stored on File: SlxOleDbConfig.dat.
The location of the file depends of your OS. On older machines it would be under Documents and Settings\All Users\Application Data\SalesLogix
However, the String is encrypted.
I have however in the past copied the string across computers and SLX decrypted it ok, so you may be able to clone the connections that way. |
|
|
| |
|