{
  "name": "SAS Dataset Combination Methods and Execution Characteristics",
  "description": "Comparative technical specification of SAS dataset combination methods, evaluating combination orientation, sorting prerequisites, Program Data Vector behavior, attribute collision resolution, and optimal use cases compiled from SAS Institute documentation and university statistical computing laboratories.",
  "page": "https://casrai.org/guides/combining-datasets-in-sas",
  "publisher": "CASRAI",
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "dateModified": "2026-11-19T11:40:00Z",
  "temporalCoverage": null,
  "spatialCoverage": null,
  "columns": [
    {
      "name": "Method",
      "unit": "",
      "description": "SAS combining syntax or procedure name"
    },
    {
      "name": "Combination Orientation",
      "unit": "",
      "description": "Direction of dataset growth: vertical (rows) or horizontal (columns)"
    },
    {
      "name": "Pre-Sorting Prerequisite",
      "unit": "",
      "description": "Whether input data must be sorted prior to execution"
    },
    {
      "name": "Variable Name Collision Behavior",
      "unit": "",
      "description": "How non-key shared column names are resolved in output"
    },
    {
      "name": "Program Data Vector Execution",
      "unit": "",
      "description": "Memory and execution processing mechanism"
    },
    {
      "name": "Optimal Use Case",
      "unit": "",
      "description": "Recommended application scenario in data workflows"
    }
  ],
  "rows": [
    {
      "Method": "Concatenation (SET)",
      "Combination Orientation": "Vertical (Rows)",
      "Pre-Sorting Prerequisite": "None",
      "Variable Name Collision Behavior": "Shared columns merged; attributes set by first dataset",
      "Program Data Vector Execution": "Sequential record reading into new table via PDV",
      "Optimal Use Case": "Stacking monthly transaction logs with identical schema"
    },
    {
      "Method": "Interleaving (SET with BY)",
      "Combination Orientation": "Vertical (Rows)",
      "Pre-Sorting Prerequisite": "Required (BY variables)",
      "Variable Name Collision Behavior": "Shared columns merged; sorted by BY values",
      "Program Data Vector Execution": "Sequential interleaving based on BY values via PDV",
      "Optimal Use Case": "Merging chronological records from separate sites"
    },
    {
      "Method": "Match-Merging (MERGE with BY)",
      "Combination Orientation": "Horizontal (Columns)",
      "Pre-Sorting Prerequisite": "Required (BY variables)",
      "Variable Name Collision Behavior": "Non-BY shared columns overwritten by last dataset",
      "Program Data Vector Execution": "Concurrent row matching with IN= flag tracking in PDV",
      "Optimal Use Case": "Joining patient demographic master to clinical visits"
    },
    {
      "Method": "One-to-One Merging (MERGE without BY)",
      "Combination Orientation": "Horizontal (Columns)",
      "Pre-Sorting Prerequisite": "None",
      "Variable Name Collision Behavior": "Shared columns overwritten by last dataset",
      "Program Data Vector Execution": "Row-by-row positional pairing based on sequential index",
      "Optimal Use Case": "Pairing fixed-length parallel vectors by index"
    },
    {
      "Method": "Out-of-Memory Appending (PROC APPEND)",
      "Combination Orientation": "Vertical (Rows)",
      "Pre-Sorting Prerequisite": "None",
      "Variable Name Collision Behavior": "Base dataset attributes retained; FORCE required for mismatch",
      "Program Data Vector Execution": "Direct block write to end of base table without PDV",
      "Optimal Use Case": "Appending daily records into massive historical warehouse"
    },
    {
      "Method": "Relational Join (PROC SQL)",
      "Combination Orientation": "Horizontal or Vertical",
      "Pre-Sorting Prerequisite": "None (Internal hashing/sorting)",
      "Variable Name Collision Behavior": "Tables aliased; duplicate column names preserved or qualified",
      "Program Data Vector Execution": "SQL query optimizer engine execution",
      "Optimal Use Case": "Multi-table relational joins with complex predicates"
    }
  ],
  "sources": [
    {
      "title": "SAS Help Center: Methods for Combining SAS Data Sets",
      "url": "https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lepg/p1pa3hnpchkgf7n1etensx665yxr.htm",
      "accessed": "2026-11-19"
    },
    {
      "title": "UCLA OARC Stats: Concatenating data files in SAS",
      "url": "https://stats.oarc.ucla.edu/sas/modules/concatenating-data-files-in-sas/",
      "accessed": "2026-11-19"
    },
    {
      "title": "UCLA OARC Stats: Match merging data files in SAS",
      "url": "https://stats.oarc.ucla.edu/sas/modules/match-merging-data-files-in-sas/",
      "accessed": "2026-11-19"
    },
    {
      "title": "UCLA OARC Stats: Match merging data files using proc sql",
      "url": "https://stats.oarc.ucla.edu/sas/modules/match-merging-data-files-using-proc-sql/",
      "accessed": "2026-11-19"
    },
    {
      "title": "University of Wisconsin-Madison SSCC: sas_table_lookup",
      "url": "https://sscc.wisc.edu/sscc/pubs/sas/4-1_SAS_Table_lookup.html",
      "accessed": "2026-11-19"
    }
  ]
}