Performance progressively degenerates when closing alerts in SAS^® Money Laundering Detection as the volume of alerts, both active and closed, grows within the FSK_ALERT table.

This is due to use of the SCL method _findRow, which does not use the index for FSK_ALERT. To resolve this performance issue, the _findRow method is replaced with a DATA step and MODIFY command which will use the index for FSK_ALERT.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Money Laundering Detection	Microsoft® Windows® for x64	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows 2000 Advanced Server	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows 2000 Datacenter Server	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows 2000 Server	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows 2000 Professional	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows NT Workstation	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter Edition	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise Edition	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Standard Edition	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows XP Professional	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Windows Vista	1.4	1.4	9.1 TS1M3 SP4	9.1 TS1M3 SP4

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

A fix for this issue for SAS Money Laundering Detection 1.4 is available at:

http://www.sas.com/techsup/download/hotfix/mld14.html#034800

---

The time taken to process closed alerts in SAS® Money Laundering Detection increases as the FSK_ALERT table grows larger.

Type:	Problem Note
Priority:	high

Date Modified:	2009-02-16 13:14:26
Date Created:	2009-02-13 15:01:11