I have experienced problems with performance using LEI to update my customer address database with billing- and visiting addresses, telephone No and so on. The MS SQL 7 table consists of about 100 000 rows and took ages to update by LEI, after 9 hours it wasn't finished. Then I rewrote the update to be made by an agent instead, using the lsxodbc, connecting to the SQL db. This update took 2,5 hours to do the exact same thing. When there are just a few changes it takes like 20 minutes using the agent. Do you have any idea if this is a configuration problem or is LEI this slow when handling large data volumes?
First, I'm going to assume you are using LEI Replication and that you are not using Timestamp Replication. That being said, LEI will compare every row on both sides (Notes and SQLServer) to weed out the deltas every time it runs. If you have a timestamp in the SQL table try using it and compare it to a field on the Notes document or use @Modified (see Connection Options-Field Selections on the Notes Connection document). Here are some suggestions that you should try regardless of timestamping:
Create an index on your SQL table based on the key column(s) that is used by the Replication activity; switch from using the ODBC Connector to the OLEDB Connector. If LEI is still being outperformed by your agent then; if they are not already, convert your agent(s) to work as LEI Scripted Activities and let LEI run it/them. This gives you the speed of the agents and the execution control of LEI (i.e. scheduled or triggered).
Dig Deeper on Lotus Notes Domino Administration Tools
Related Q&A from Scott Lemieux
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.