Home/ Questions/Q 439015
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T20:44:04+00:00

I am working on a legacy database. I am not able to change the

  • 0

I am working on a legacy database. I am not able to change the schema 🙁 in a couple of tables the primary key uses multiple columns.

In the app I read the data in each row into a table the user then updates the data and I write the data back into the table.

Currently I concatenate the various PK columns and store them as a unique id for when I put the data back into the table.

Now I was wondering if there is a more efficient way to do that. Coming from a mySQL background I am not aware of any but thought SQL Server 2005 may have a function

SELECT PRIMARYKEY() as pk, ...  FROM table WHERE ...

the above would select the key that the database engine uses as the primary key for the given record

I searched and couldn’t find anything. Its probably just me being fussy but I don’t like the concatenation trick.

DC

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In SQL Server, there is no equivalent of PRIMARYKEY() that I would be aware of, really. You can consult the system catalog views to find out which columns make up the primary key, but you can’t just simply select the primary key value(s) with a function call.

    I would agree with StarShip3000 – what do you concatenate your PK values for? While I don’t think a compound primary key made up of several columns is necessarily a very good idea, if it’s a legacy system and you can’t change it, I wouldn’t bother concatenating the PK values on read, and then having to split them apart again when you write your data back. Just leave the structure as it is – compound keys aren’t generally recommended, but they are indeed supported, no problem.

    • 0