SAS 7.1 - SAS 8.2 VIYA 3.5 CORE DATABASE

[Santt0sh]

Hi All,

We are upgrading to SAS 8.2 AML with SAS Viya3.5 from SAS 7.1 AML.

I have a couple of questions, the experts here can Answer or provide me some guidance.

As mentioned we are upgrading from SAS 7.1 to the above-mentioned version, in previous versions, we used to read files into Staging is and then load them to CORE now do we

1. need to upload all the files for ex. from 2000 or do we need or have an option of taking the Backup of CORE from SAS 7.1 and try to use it with 8.2

2. As I am aware that SAS 8.2 AML on our system has no SAS DI Studio, or maybe it doesn't come with SAS DI studio instead needs to use SAS Studio. Do we need to rewrite the ETL SAS  DI jobs in SAS Studio or use the SAS DI jobs created for the ETL process?

Please suggest!!!

Regards,

[Maarten_at_SAS · Accepted solution]

Hi 

Re your first question, there are multiple ways to get historic and ongoing slowly changing dimension data into the new versions core db. There are a few considerations.

1. Assessing the delta between the old and the new core data model (there are some differences) as per the actual usage of the AML7.1 core, do the mapping and use that to copy over the historic data. (Assessment should be completed first)
2. Historical data can be copied from source database to target database using SAS or other tools. The process will need changes to account for database differences. In most cases, this will not be  a simple copy. It is advisable to eliminate data past a certain age and store it in outside the current core database. Ex: Do not load customers who are no longer banking with the FI, and/or closed accounts.  (Note: This process should comply with local regulatory/archival policies) 
3. VI also allows you to directly connect to the AML7.1 or older db if that is on Oracle or Postgres (or SQLServer for AML 8.3). Also, in that case you have to accommodate the (minor) delta between the AML7 and AML8 standard data models. You can do this…
• On a temporary basis as part of a transition phase where ultimately the new data is going to be loaded/updated into core as per a new process
• On a more persistent basis where you have a hybrid architecture where the core db resides on the SAS 9.4 platform and you can then continue using SAS DI Studio.

Re your second question, indeed SAS Data Studio on Viya 3.5 may not have sufficient ETL capabilities to support the ETL process for AML8. These are the options you have:

1. Rewrite the ETL code in SAS SPRE (or base SAS). We do not currently have a baseline code available for AML 8, but I can get you in touch with an implementation partner who is currently working on this
2. … or we can give you the baseline code for loading AML core on legacy solution (SAS 9) which may serve as a starting point but will need additional work requiring in-depth technical expertise.
3. Maintain the SAS 9.4 environment with and continue to use DI Studio to load the  data into the database on the Viya 3.5 platform … or keep the current core db on SDAS 9.4 as well and make any changes needed to remap to AML8, and then connect VI to the ‘old’ db (remediate database differences) on SAS 9.4.

As you will understand, none of these options provide an ideal solution and each come with its own pros and cons which are dependent on:

• The customers appetite and budget
• The teams expertise and skills
• The customer strategic plans (e.g. are they considering pushing through to AML11 on Viya 4 in a number of years)

Hope this helps

Maarten van Dijck Nemcsik and Ashok Mirchandani

SAS Global Fraud Security & Intelligence Business Unit, Enablement & Domain Delivery Team

[Santt0sh]

Thanks Maarten and Ashok for your guidance and suggestions!!!
I would be Thankful if you can help me with a base line code to baseline code for loading AML core on legacy solution (SAS 9) which may serve as a starting point for us.

Thanks
Santtosh

[Maarten_at_SAS]

Hi Santtosh

Please send an e-mail to maarten.van.dijck@sas.com and ashok.mirchandani@sas.com and we will send you the legacy artefacts, which you cn use as a starting point. 

[Erik_Zencos]

Hi, 

Regarding question 2, I have been working on both 7.1 and 8.2. 

The simplest way is to take your deployed 7.1 code and rewrite to fit the 8.2 data model. There are some changes to the data model, and you will need to go through a mapping / design 'exercise'. The drawback with this approach is that the code might not perform optimally. For 8.2 we use DS2 code (threaded processing) for our AML 8.2 projects, this gives very good ETL processing times. Feel free to reach out if you want to know more, we can help you with either approach and are currently working with several clients on AML 8.2. 

Regards,

Erik Meyer

Zencos