Usage Note 54673: Using the datastore cleanup utility when the SAS Marketing Optimization data store increases in size and decreases performance
SAS Marketing Optimization functionality writes to various SAS® data sets that are stored in a data store. As a result, there are times in which you might want to clean up orphaned or rogue entries in the data store, particularly if you see a decrease in performance.
To clean up the data store:
- Run an interactive SAS session on the SAS compute-tier machine.
- Run the SAS Marketing Optimization autoexec file. When you are prompted, use an external user account (for example, sasdemo) to authenticate.
- Submit the following LIBNAME statement:
libname mometa "&mometa" server=&moshare authdomain="&modatausr_authdomain";
- Then submit the following statement:
%mo_datastore_cleanup();
These steps do the following:
- automatically make a backup copy of the data store in the .../datastore/backups directory.
- keep the data store locked down
- rewrite the tables to eliminate deleted observations from the tables
Note: The cleanup tool is safe to run. It only removes orphaned rows to reduce the size of data-store tables.
The more scenarios and constraints you have, the longer the upload process takes. Part of the upload process is to copy the associated scenarios and update them based upon new incoming information from the new refreshed input data.
As a best practice, always remove scenarios that are no longer used. This action makes the upload process is faster.
Operating System and Release Information
SAS System | SAS Marketing Optimization | Microsoft® Windows® for x64 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8 Enterprise 32-bit | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8 Enterprise x64 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8 Pro 32-bit | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8 Pro x64 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8.1 Enterprise 32-bit | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8.1 Enterprise x64 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8.1 Pro | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8.1 Pro 32-bit | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Datacenter Edition | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Enterprise Edition | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Standard Edition | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 for x64 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2008 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2008 R2 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2008 for x64 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2012 Datacenter | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2012 R2 Datacenter | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2012 R2 Std | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2012 Std | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows XP Professional | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Enterprise 32 bit | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Enterprise x64 | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Home Premium 32 bit | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Home Premium x64 | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Professional 32 bit | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Professional x64 | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Ultimate 32 bit | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Ultimate x64 | 6.1_M1 | | 9.3 TS1M2 | |
Windows Vista | 6.1_M1 | | 9.3 TS1M2 | |
Windows Vista for x64 | 6.1_M1 | | 9.3 TS1M2 | |
64-bit Enabled AIX | 6.1_M1 | | 9.3 TS1M2 | |
64-bit Enabled HP-UX | 6.1_M1 | | 9.3 TS1M2 | |
64-bit Enabled Solaris | 6.1_M1 | | 9.3 TS1M2 | |
HP-UX IPF | 6.1_M1 | | 9.3 TS1M2 | |
Linux for x64 | 6.1_M1 | | 9.3 TS1M2 | |
Solaris for x64 | 6.1_M1 | | 9.3 TS1M2 | |
*
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.
Date Modified: | 2014-11-25 10:06:43 |
Date Created: | 2014-11-19 13:09:34 |