Lawson ENV 803 SP7, Financials 803 SP11. Recently migrated to SQL Server 2005 as a step toward LSF9. Since then, performance for the most part has been abysmal. A function like BR42 now times out. Once any load has been put on the system, response time degrades significantly. Pursued Lawson GSC about BR42 but we discovered ourselves that the wrong index (at least from our perspective) is being used. Checked all the usual suspects -- the MICROSOFT file, the SQL Native Client version matching the SQL server version. Lawson Financials S3 uses OLE DB but other than that I have no knowledge of what to look for. Didn't show in test probably because of volume of test transactions was low. Comments?
If you've narrowed it down to the wrong index in SQL, then you can fix that by doing some systems and/or db things. Looking at the MICROSOFT file and the SQL client version wouldn't really reveal much.
Have you done a analysis of the database using Lawson tools? Example: build and/or reorganize your database? I don't know if that's already been done on your system, or when/how the system became in that condition you mention. What about your ODBC connection? Tried turning off security to see if it's a security issue?
If you would like some assistance, contact me off line and we can discuss.
Roger
Posted By JY on 05/05/2009 10:11 AM Lawson ENV 803 SP7, Financials 803 SP11. Recently migrated to SQL Server 2005 as a step toward LSF9. Since then, performance for the most part has been abysmal. A function like BR42 now times out. Once any load has been put on the system, response time degrades significantly. Pursued Lawson GSC about BR42 but we discovered ourselves that the wrong index (at least from our perspective) is being used. Checked all the usual suspects -- the MICROSOFT file, the SQL Native Client version matching the SQL server version. Lawson Financials S3 uses OLE DB but other than that I have no knowledge of what to look for. Didn't show in test probably because of volume of test transactions was low. Comments?
Thanks for the replies.
When I said the wrong index for BR42, we used a test program supplied by the Lawson GSC to use index ATNSET8 instead of ATNSET4 -- the difference being that the former uses ATNSET8_SS_SW as the main key and the latter uses ATNSET4_SS_SW. The BR42 process calls ACTRANS depending on the value of ATNSET8_SS_SW. However it's true that this worked under SS2000 even if I think it uses the wrong index.
So right now we're on ENV803SP7, APP 803SP11, and SS2005. Our next step is to migrate to a new app server with LSF9. It's a staged approach.
Now we're getting time outs on back office transactions like AP20.1, AC40.4, etc. A restart of SQL Server alleviates the situation for a few hours and this is being done until the root cause is found.