Hello @shrutiravi,   you have a couple of ways to tackle this.   1. You can extend the memory settings on SAS DI client, as of http://support.sas.com/kb/31/101.html    2. You can split your export on smaller export packages, then the memory used by the export will be lower. ... View more

@shrutiravi If your SAS compute tier is under Windows then I'd expect that you've got everything you need. ODBC will have some functional restrictions and performance will likely be lower as compared to using the native SAS/Access to Oracle interface.   From the docu:  "ODBC functionality is provided by three components: the client interface, the ODBC driver manager, and the ODBC driver. SAS provides the SAS/ACCESS interface to ODBC, which is the client interface. For PC platforms, Microsoft developed the ODBC Administrator, which is used from the Windows Control Panel to perform software administration and maintenance activities. The ODBC driver manager also manages the interaction between the client interface and the ODBC driver. On UNIX platforms, a default ODBC driver manager does not exist and SAS does not provide a driver manager with SAS/ACCESS to ODBC. For UNIX platforms, you should obtain an ODBC driver manager from your ODBC driver vendor." http://support.sas.com/documentation/cdl/en/bidsag/65687/HTML/default/viewer.htm#p0r68n8gtyzjqen1ddl4r2q3eh4v.htm   If you need certainty then contact SAS TechSupport. ... View more

Hi @shrutiravi   The answer you're looking for is part of the SAS® Marketing Automation 5.4 Administrator’s Guide documentation, available from the SAS® Customer Intelligence page (if you need the user/password to access the documentation, please contact your SAS Technical Support).   Starting page 197 of the documentation, you'll find details about Backing Up and Restoring Data. This is what you can find from that chapter.   Hope that helps.   Cheers, Damo ... View more

Hi Anja,   We are using SAS 9.3 and SAS Market Automation 5.41     ... View more

You have two choices - have two subjects or have two business contexts.   For the easy approach (assuming you don't really need separation, just a different source), just add the Inactive Subscribers table in your current data model and put it in your current information map as a new subject. That would also require a new contact history table in your CDM (like CI_CONTACT_HISTORY_INACT), and would allow you to use your current configuration but choose on a node-by-node basis whether you want to work with Active Subscribers or Inactive Subscribers.   If you want them fully separate (entirely different sets of data, separate users, separate storage areas for campaigns, separate CDM reporting tables & history tables), then the answer would to create a second business context. That means you'll need a new information map, new libraries (for your customer data, CDM and MATables), a new root folder in your Metadata, new user groups (probably), and then a new business context to pull it all together. ... View more

Hi,   Thanks for your Reply. I am sorry, But this is not what I asked for, I need rule based on the Value of Status Column.   If Value of Status is "Active" then, The rule should be different i.e. if ratio is greater than 1 then it should be green else red. If Value of Status is "Grace" then, The rule should be different i.e. if ratio is greater than 1 then it should be red else Green.   as so on for other values of Status Column.   Thanks,   Ravi     ... View more