Hey Shakti!   Have you tried using the Data Validation node? You can use that to filter your data. For example, you could filter on an expression like Profit > 1000. Let me know if that's the sort of thing you're trying to do. ... View more

One more suggestion looking at the job again-you might not need the Standardization node. When you generate match codes, a standardization is automatically applied. So if you're using the Standardization to clean up values before they are used to generate match codes, that's unnecessary. (Unless you want a cleaned version AND a match code.) ... View more

Hey Shakti!   I have two suggestions for you. First of all, you don't need the Branch node in your job flow. I don't know how much it will speed things up to remove it, but it can't hurt. The Branch node simply copies its input to one or more outputs. Since you're only using the Branch node to connect to one output, you can get the same result and skip a node if you connect the Surviving Record Identification Node to Data Validation 2 directly.   The other suggestion: do you have a DataFlux Data Management Server? Remember that DataFlux Data Management Studio is a client application, and is not really meant to process huge amounts of data. Ask your admin if you have a server, and if you do, here are some links on how to get access to it and deploy your jobs to it: Connecting to Data Management Servers (sas.com) Deploying Jobs to a DataFlux Data Management Server (sas.com)   A real server should run this much faster. Pay attention to the pre-requisites page: if you deploy a job to the server, you have to make sure it has everything it needs to run. The server might need copies of your business rules, macro variables, and QKB, among other things.    Let me know if that helps.  ... View more