Hi, We have number of SAS 9.4 modules deployed on our SAS implementation e.g. enterprise guide, DI Studio, Metadata repository etc. We are looking to deploy SAS visual analytics and visual statistics. Just want to check the best deployment method. The options we are considering are. Deploy 9.4 VA/VS co-locating with existing SAS 9.4 installation. i.e. sharing the common modules like metadata repository, mid/web servers etc keeping the SAS VA/VS compute nodes separate to SAS compute nodes Deploy 9.4 VA/VS as a separate SAS instance i.e do not share the common modules. SAS VA/VS will have its own version of metadata repository server, mid/web servers and compute nodes. Deploy Viya VA/VS which is a new SAS ground up technology and is not compatible with existing SAS 9.4 product suite. Option 3 may not fly and may take long time to decide as we have fairly large user base. So it is the choice between 1 & 2. Trying to identify the pros and cons of these options. Option 1 seems to have following pros. But do they also become bottleneck and having a seperate instance will have flexibility? Just want to understand the best practices in SAS deployment. Do you go down seperate instances route for new modules or try to build on top with exisiting SAS estate. Single place for user administration & access control. Software patching will be simpler. Single integration point to LDAP Less cost for hardware required for common modules e.g. metadata repository & mid/web server. Can developers benefit from having a shared metadata repository? Many thanks for your help. Cheers, Kiks.
... View more