Hi - here are some details about these options:   BULK_ROW_COUNT - This allows you to process a set number of rows at a time. Enter the number of rows to be processed in the Property Value field when you have thousands of records. This option will help your system run more efficiently. The default value is 10,000. Bulk row count is supported on databases such as Oracle SQL Server and DB2. There is no need to activate a bulkload option at the driver level in the data connection for the table.   MAX_ERROR_COUNT - This allows you to set a threshold for maximum errors. If set to -1, infinite errors are allowed. If you want to ensure that no data rows are left out of the commit to the database, you should set this to 0.   COMMIT_EVERY - This sets how often a commit command should be sent to the data source.   In some cases where many rows of data need to be loaded or updated into a database, you can use a bulk loading feature built into the “Data Target (Insert)” node to drastically improve performance. For example, you can set the maximum number of rows to bulk load to “50000” and set the commit interval to “1.” This will bulk load batches of 50000 rows of data into the database very quickly because the frequent communication with the database server as would happen with smaller packets of data can be avoided.   Experiment with the commit level setting. As a general rule, committing every row to the database will be slower than committing a group of rows except in this special case: use the bulk count and commit level together (setting commit level to 1 and the bulk number to 50000 for example) to achieve superior load/update times.   Ron ... View more

I think I understand now what you are seeing. Some hints:   You can certainly apply individual standardization schemes but many of them are used in specific ways inside standardization definitions. Standardization definitions incorporate things like casing, parsing, and regular expressions in addition to standardization schemes to correct your data. If a definition exists for the data type you are working with, it's generally better to use a definition over a scheme. In the case of your example, becuase you are attempting to standardize just given name information, you will want to use the Standardization (Parsed) node. In it you can map your given name to the expected Given Name token and then appropriate standardization will be done for the given name. In some cases, when you send just a given name into the "Name" definition (which is really built for full names), the definition will reorder compound given names, thinking a surname is involved somehow.   I attached some screenshots to show how using a standardization definition with the Standardization (Parsed) node will get you the results you are looking for. Ron ... View more

The import/export functionality will let you move Quality Knowledge Base (QKB) definitions into and out of QKBs. In your situation though, unless the QKB on Linux is accessible to your Windows DM Studio environment through a network share of some kind, you'll probably need to copy the QKB on your Windows environment where the edits were made over to the Linux environment. Some important points:   t's always a good practice to make backup versions of your QKB directory before edits and copy/paste activities Only replace the entire QKB on Linux if you're sure it's the same as your DM Studio environment. If you're not sure, you can copy the Linux-based QKB over to Windows, register it, use the export command to export the definition from the Windows-based QKB, use the import command to bring the definition into the Linux-based QKB, and then move the Linux-based QKB back out to the Linux server. If you are copying the entire QKB, you'll want to copy all the files and directories from the version number on. So for example, all the directories and files starting here on a default QKB installation on Windows would need to be copied to your Linux-based DM Server environment: C:\ProgramData\SAS\SASQualityKnowledgeBase\CI\27 If you already have run jobs/process on DM Server that use the QKB, they may still be loaded into memory along with the QKB. Use the "unload" feature in the DM Server manager component of DM Studio to unload the jobs from memory. If you find that your changes are not being picked up, you may need to restart your DM Server before attempting to run the job again. Ron ... View more

Yes, that's it. Use Customize to open the Quality Knowledge Base (QKB) and navigate to the match definition you want to use. Once you open the match definition, you can see the various files that it employs to match data. The product documentation describes how to use the Customize application. Consider making a copy of the match definition first using Customize before you start making changes.   Ron ... View more