Slow Logon Times to Business One

Question

One thing to look at when logon times get slower and slower in SAP Business One is your Business One inbox.   Especially if the logon takes longer before the add-ons are loaded.
If you are using Alerts in Business One then it is possible that the OAIB and OALR tables are growing larger and larger if your users are not deleting these Alert messages from their Inbox.   The OAIB table stores the messages in the inbox and are keyed by alert and user-id. The OALR table has a record for each time a alert is fired in Business One and are keyed by Alert ID.
If you have an Alert that is triggered (conditions are met) and that Alert goes to 5 users, then there will be 5 new records in the OAIB table. If that Alert is set up to run every 5 mins and the 'Save History" check box is marked on the Alert, then you get 5 records each and every min to the OAIB table.  5x60x24 or 7,200 records a day. A reason why it is better not to check the Save History option on your alerts. 
If your users are checking their inbox and deleting these messages then the users OAIB, and possibly the OALR record are being deleted. If they don't check their inbox or don't delete them both tables continue to grow.   (the OALR record will not be deleted until each user message referencing that Alert ID is deleted).  So 1 user not deleting their Inbox alert messages then B1 will be keeping the OALR records.
So how does this impact the logon time....  
Well when you logon Business One one of the things it does after validating your user id and password is check the OAIB and OALR tables. With SQL Profiler I saw many SQL Select statements against the OALR table.  One statement for each record in the OALR table.....   In one client database I saw over 12,000 OAIB alert records for 1 user that had never been viewed or deleted. This 12,000 OAIB records meant 12,000 + OALR records which meant 12,000 individual SELECT statements against OALR at each and every sign on to Business One.   Since the user had never been taught to check their inbox and the General Setting>Services option "Display inbox when new message arrives" was turned off they never new they were getting Alerts.   This was compounded by 3 other user with similar counts in OAIB and cumulative in OALR.   Also many of the Alerts were to "OLD USER IDs" (ones that users never logged on to anymore because they had left the company) but were still generating OAIB and keeping OALR records. Many Partners allways include Manager on a Alert list and this id may no longer be used on a regular basis or even have licenses assigned anymore.
So the remedy is to run this quick query to see if you have the problem.
SELECT count(T0.usersign), T1.u_name from OAIB T0 INNER JOIN OUSR T1 ON T0.usersign = T1.Internal_K  Group BY T0.usersign, T1.u_name
This should list a row fore each userid and how many records they have in the OAIB table.  If the counts are high then you should sign on to these users and delete their old Alert Messages from the inbox.   if you do this for all users then they OALR records should also be deleted. This should cut down the logon time if you have counts like this one user.
The other thing to consider going forward is to review who is getting these alerts (remove old users and those that don't need to be informed) Also make sure that you don't have the Save History option turned on if not really required.  Also deactivate the alerts if they are no longer valid or being used.
Hope this helps
Dan Love  SAP

Answer 1

Hi,
In addition to my previous opinion,  I think what you suggest here is correct only if we use the query alert frequency but the system alert seems have no frequency setting.
So, I think SAP makes it different because they want that the query alert must be restricted its frequency except system alert. This is quite confusing and can make us wondering why.
you could see if we want to create new alert management, there is directly available frequency field and save history check box meanwhile the system alert is not.
As a smart consultant, I think it will become a full concern why they are different.
Rgds,