The tools are quite different. AS/DI (ETL) and Miner are behaving technicallly completely different and are for a different type of usage. Altough ETL is needed to get data delivered data that is possible to be used by Miner. Differences:
- ETL is thougt to be a planned process that will become into scheduled operations.
- The miner part can cause a heavy load some parts can use mp-connect options aside threading. All is user inititated and not being planned/scheduled. That is how mining behaves it is the functional job. It can have basic fucntionality being solved by using Eguide.
Segregations options:
1/ users/operations
It would make sens to use SAS/DI in a classic development approach. Develop Test Accept and Production. By that you are getting segregated environments (D,T,A,P).
Mining is not applicable to that classical approach as it just makes sense having real data not faked data. You will always use "production" (shadowed) data. When deploying the models (the result of mining) it will need the real "production" connection.
2/ App-servers
As the hardware should be designed for the expected usage http://support.sas.com/rnd/papers/sgf07/sgf2007-iosubsystem.pdf The IO part shoud be well evaluated. With Unix there is a lot do with filesystems and mounts. GRID-computing is the ultimate.
Segregation by app-servers (See Paul Homes) is the first option to segregate usage ub user groups.
It is quite normal (see all the examples) too have many of those appservers. The default installation configurationstep however is for just 1.
Each appserver context can be set up with different settings each WS or Sp server can be tuned with differnt settings. DI and Miner both use a WS (part of app-server context) by default. Your platformadmin should help you with that... (if it is not you).
With 9.3 there are many ".._usermod" files at the OS-level to achieve that. These are manual changes (editting).
---->-- ja karman --<-----