To achieve the same operation in SAS that you described in R, you can follow a similar approach by first isolating LeBron James' statistics and then subtracting these values from every other player's corresponding values. Here's how you can do this step-by-step: Step-by-Step Solution 1. Identify LeBron James' Row: Extract LeBron's statistics and store them in macro variables. 2. Subtract LeBron's Statistics from All Other Rows: Use a DATA step to subtract these values from each player's statistics.   /* Step 1: Extract LeBron's statistics into macro variables */ data _null_; set player_traditional_usage_merged; if player = "LeBron James" then do; call symputx('lebron_pts', pts); call symputx('lebron_oreb', oreb); call symputx('lebron_dreb', dreb); call symputx('lebron_ast', ast); call symputx('lebron_stl', stl); call symputx('lebron_blk', blk); end; run; /* Step 2: Subtract LeBron's statistics from all other players */ data player_traditional_usage_merged; set player_traditional_usage_merged; similarity_to_lebron_pts = pts - &lebron_pts; similarity_to_lebron_oreb = oreb - &lebron_oreb; similarity_to_lebron_dreb = dreb - &lebron_dreb; similarity_to_lebron_ast = ast - &lebron_ast; similarity_to_lebron_stl = stl - &lebron_stl; similarity_to_lebron_blk = blk - &lebron_blk; run; /* Print the resulting dataset */ proc print data=player_traditional_usage_merged; var player team similarity_to_lebron_pts similarity_to_lebron_oreb similarity_to_lebron_dreb similarity_to_lebron_ast similarity_to_lebron_stl similarity_to_lebron_blk; run;   Explanation of the Code 1. Extract LeBron's Statistics: The first DATA _null_ step reads through the player_traditional_usage_merged dataset and identifies the row where player = "LeBron James". The call symputx function is used to store LeBron's statistics (like pts, oreb, dreb, ast, stl, and blk) in macro variables (e.g., &lebron_pts, &lebron_oreb). 2. Subtract LeBron's Statistics from All Players: The second DATA step iterates through the entire dataset again. For each player, it creates new variables (similarity_to_lebron_pts, etc.) that store the difference between the player's stats and LeBron's stats. 3. Print the Results: The proc print step outputs the final dataset showing each player's statistics subtracted from LeBron's statistics   Feel free to update logs if you get error. I have not tested the code. 🙂  ... View more

Can you elaborate your question? Is your dataset contains unique columns with keys? If you do not have duplicate data then may be possible to find using extract and join(using having min and max date value). ... View more

It looks like you're encountering an issue with the libname statement in SAS when trying to connect to Databricks using JDBC. The error message indicates that there's a problem with one of the connection properties. Here are a few things you can check and adjust to resolve the issue: 1. JDBC Driver and Classpath Make sure you have the correct JDBC driver for Databricks and that the path to the JDBC driver in your classpath is accurate. Verify that the JDBC driver file (.jar) is located in the specified directory.   2. Connection Properties The error message suggests that 'useragententry' might be an invalid property. Double-check the connection properties used in the URL. For Databricks, the properties should be correctly formatted and valid for the driver being used.   3. Correct URL Format Ensure that your JDBC URL is properly formatted. Based on Databricks documentation, your URL should look something like this: jdbc:databricks://<hostname>:<port>/;transportMode=http;ssl=1;AuthMech=3;UID=<username>;PWD=<password>;httpPath=<httpPath>; In your case, it should be: jdbc:databricks://servername:443;httpPath=/sql/1.0/warehouses/xxxxxx;ssl=1;AuthMech=3;UID=user@example.com;PWD=xxxxxxxxxx;   4. Check for Valid Properties Make sure that all properties in the connection string are valid. According to Databricks JDBC documentation: httpPath should not have single quotes around it. Ensure ssl is set to 1 if using SSL (which is typically required). AuthMech=3 is correct for username/password authentication. 5. SAS and JDBC Driver Compatibility Ensure that the JDBC driver version you're using is compatible with SAS Viya 4 and Databricks. Sometimes issues arise from version mismatches.   6. Debugging Steps Test the JDBC Connection Independently: Use a simple Java program or a JDBC client to test the connection outside of SAS to ensure that the driver and URL work. Check SAS Logs: Look for more detailed error messages in the SAS log which might give more context to the problem. Consult Documentation: Refer to both SAS and Databricks documentation for any specific configurations or known issues related to JDBC connections.   Example Updated LIBNAME Statement Here's how your updated libname statement might look:   libname brklib jdbc classpath="/opt/sas/viya/home/lib64/accessclients/jdbc" class="cdata.jdbc.databricks.DatabricksDriver" URL="jdbc:databricks://servername:443;httpPath=/sql/1.0/warehouses/xxxxxx;ssl=1;AuthMech=3;UID=user@example.com;PWD=xxxxxxxxxx";   Ensure that you replace servername, xxxxxx, user@example.com, and xxxxxxxxxx with your actual Databricks server name, warehouse ID, user credentials, and password. By following these steps, you should be able to troubleshoot and resolve the connection issue. If problems persist, post the complete logs. ... View more