Dear database designer

[dandymcgee]

This is not how you assign a primary key:

[Nokurn]

Mother of god. That's just asking for trouble. DId you fix it?

[dandymcgee]

Mother of god. That's just asking for trouble. DId you fix it?

I can't right now because my boss is on vacation and I don't know the details of what, if anything, accesses this table. It may just be a history table for our reference, as I don't know of any application that allows rolling back records. If that is the case, I'll remove all of the '_%TicketNumber%' suffixes from the pkBackupDate column and set (pkBackupDate, TicketNumber) to the primary key like it should be. There's a reason primary keys can span multiple columns and it's to prevent the need for this sort of silly "hashing" approach to creating a unique key.