Suppose a global, mid-sized company is considering a document control management solution that is backed by a SQL Server database and allows developers to create document form types using a form creation tool. Each form type created using the tool is represented in the database by a table with a primary key of datatype
What impact would the requirement to use
VARCHAR(50) primary keys have on system performance vs. a system using a more conventional design approach, e.g., this? Assume the core audience for the answer is mostly non-technical, i.e., C-Level Executives making a go or no-go decision on the solution.
The document control management system needs to perform typical document control management system tasks for a global mid-sized company for many years (at least two decades).
This is a canned solution and the primary key data type cannot be altered.
VARCHAR(50)data type maps to the company's serial number for products. The serial number format is alphanumeric and can contain dashes.
The system is web based and uses SQL Server 2014 and the .NET Framework (C#) technology stack.
Questions researched before creating this question, all of which don't align with the technology stack and/or have answers too in the weeds for a non-technical audience: