Minimize Deletion Stubs
In a database that gets archived frequently, or that has a large number of “temporary” documents that get removed on a scheduled basis, you can keep your database lean by reducing the number of deletion stubs it maintains.
You can use the “Remove Documents Not Modified in Last X Days” setting in the database replication options to minimize deletion stubs in databases with a lot of deletions. Deletion stubs get purged at about one half the number of days specified in this setting, regardless of whether or not the setting is active (normally you do not want this setting to be active, but the number of days affects the deletion stub purge interval regardless).
Read more…
Viewed 17379 times by 6062 viewers
I found this lotus notes tutorial in fwd mail and it will help someone for make decision.
MICROSOFT (NSDQ:MSFT)’S EXCHANGE SERVER really came of age with the release of version 2007. Exchange 2007 offers a solid and complete messaging platform. The beta release of Exchange 2010 serves up even more features and functionality and looks like it may be the most robust Exchange offering yet.
Exchange has long enjoyed the lion’s share of the business messaging platform market. Does this mean that it is the best e-mail platform offering out there? Some would argue that isn’t the case. Microsoft dominates in the business client/server software market, so it stands to reason that Exchange would be the “best fit” for an organization already running a Windows environment. Perhaps that fact accounts as a major reason Exchange is so widely deployed.
However, IBM (NYSE:IBM)’s Domino platform with Lotus Notes still has a strong following. Die-hard Lotus Notes fans cite stability and security as the primary benefits for eschewing Exchange for Notes. We took a side-by-side view at the two latest releases of each platform: Exchange 2010 and Lotus Domino 8.5 and each e-mail server’s respective clients: Outlook 2007 and Lotus Notes client 8. We assessed each in five key areas: installation and deployment, interoperability and customization, feature set, performance and pricing.
Read more…
Viewed 17129 times by 7210 viewers
It’s easy to develop simple applications in Lotus Notes and, if you have a few users and not too many documents, you’re unlikely to have performance issues. However, if your application is successful, you may accumulate lots of users and lots of data. If you haven’t designed it with performance in mind, your application will slow to a crawl.
This white paper discusses the main factors affecting Notes/Domino application performance and explains what you, as a developer, can do to maximize performance. This is not an exhaustive guide; rather, we focus on the design problems that are most common and most serious.
Read more…
Viewed 7113 times by 1905 viewers
The following are some tips for making applications/views that perform well even with reader access controlled documents:
- Embedded view using Show Single Category. This is the winner, hands down. If your data is structured so that users can see all the documents in a category, then you can display just the contents of that category very quickly to the user. In some cases, it may make sense to let the user switch categories, in which case you have to consider whether or not he can see the contents of the other categories. But in most cases, the view would be something like My Sales and would show all the sales documents for the current user. The caveat for this kind of view is that the user interface for the Notes client is not quite as nice as the native view display. For Web browsers, it is just as good, and we have never seen a reason not to use this kind of view for Web browser applications. In fact, the performance is so good that it’s faster to open one of these with reader access controlled documents than to open a native view without reader access controlled documents!
Read more…
Viewed 8897 times by 2207 viewers
Here are some tips about view performance, regardless of whether or not reader access controlled documents are present.
Time/date formulas
Using @Now or @Today in a column or selection formula forces a view rebuild every time the view is refreshed. Therefore, if you use this kind of formula, consider making the view refresh Manually or “Auto, at most every n hours.” That way, when users open the view, they will not have to wait for a view rebuild (or rarely so, in the latter case). The downside to this is that the view may be out-of-date because it opened without trying to refresh. Consider the contents of these views and how fast they change to determine whether or not you can use these indexing options safely.
Read more…
Viewed 7523 times by 2319 viewers
