11/29/2024 5:28:04 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
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!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
| |
| |
|
Re: SLX OLEDB Provider vs Linked Server
Posted: 26 Apr 07 11:33 PM
|
fiogf49gjkf0d Hi Vladimir - it's obvious that your 1st language isn't English - and I'm doing my best, but I can't quite understand what's going on here. Why are you trying to create a 'linked' server. I'm not even sure I know what you mean - are you talking about 'linked server' in the SQL Server sense?
Can you explain a bit more about the problem that you are facing that led you to think that a linked server was the answer? Maybe there is another solution.
Phil
|
|
|
| |
|
Re: SLX OLEDB Provider vs Linked Server
Posted: 27 Apr 07 11:24 AM
|
fiogf49gjkf0d May I ask your need for using stored procedures on a remote enabled implementation of SalesLogix?
Assuming that all database update requests are instigated by the SalesLogix application and not an external application (i.e. Company Web Site), one should not use stored procedures on a remote enabled implementation of SalesLogix, but rather use SalesLogix internal coding solutions. If an external application is instigating the update requests, there are other ways to accomplish the updates, within the parameters of the SalesLogix provider. Such as writing the information to a temporary table, which SalesLogix could scan and process. Another way would be to enable to the external application to use the SalesLogix provider and write directly to the database.
It just sounds like you may be trying to reinvent the wheel, by creating your own synchronization method and it may be more headache than it’s worth.
|
|
|
|
Re: SLX OLEDB Provider vs Linked Server
Posted: 28 Apr 07 1:46 AM
|
fiogf49gjkf0d One way to do this in DTS is to perform all of your INSERTS, UPDATES and DELETES explicitly, via an SLX OLEDB Provider connection.
These SQL statements will run on the main database and then synchronise out to your remotes.
Bear in mind that you need to be careful if you are using data that exists only on the main SQL Server to update the SLX database. A (pseudo) statement such as
update account
set userfield1 = externaltable.field1
from account
join externaltable on account.accountid = externaltable.accountid
may run fine on the main db. But when it is synced out to remotes, it will not run, because the external table does not exist on the remotes' SQL Server instances.
In this case, what you need to do in your DTS is create a recordset containing the data that you want to update in SLX and then loop round the recordset, performing the updates explicitly:
create recordset
do until recordset.bof or recordset.eof
update account
set userfield1 = recordset.fields("field1").value
where accountid = recordset.fields("ID").value
next record
loop
etc. Obviously, this is not actual code.
When these statements get synced out to remotes, they execute fine, because there is no dependence on external data.
But if there's a lot of updates to be done, the length of time it takes to sync could increase hugely.
Good luck. |
|
|
|
Re: SLX OLEDB Provider vs Linked Server
Posted: 25 Jul 07 12:13 PM
|
Hi, Vladimir!
I hope you was able to solve your problem with linked server....
But any way I want to share with you my solution:
1.select "SalesLogix OLE DB Provider" as "Provider Name:" for linked server;
2.click on "Provider Options" and make sure that only "Allow InProcess" is only option checked;
3.Enter "Provider String:" as
Provider=SLXOLEDB.1 assword=pwdersist Security Info=True;User ID=admin;Initial Catalog=saleslogix;Data Source=SLXPROD;Extended Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1"
where "Initial Catalog" is equal your SLX alias name;
"Data Source" is equal name of your SLX server....
4.On security tab select "Be made using this security context" and enter Saleslogix username and password;
5.On the "Server Options" tab I have "Data Access"/"RPC"/"Use Remote Collation" checked.
--------------------------------------------------------
I was able delete/update SLX data with remote syncronization thought this server (using OpenQuery). One problem I found with access to [text] fields.
Thank you,
Sergey |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|