<div>
The other part of their reasoning is making muti-table inserts easier. For instance, writing data in a foreign table and primary table without having to lookup the I'd columns max I'd number. They simply insert the part number in both tables I'd columns. I was not taught this way and it seems quite backwards.
</div>


The other part of their reasoning is making muti-table inserts easier. For instance, writing data in a foreign table and primary table without having to lookup the I'd columns max I'd number. They simply insert the part number in both tables I'd columns. I was not taught this way and it seems quite backwards.

<div>
<div class="content wysiwyg-content">
I work at a company IT dept that never used sequectial number ID columns in data tables. They insist on using unique data per row in the ID column because the data (part number) makes more 'human readable' than a secequence number.<br />
<br />
Q. What is the best practice?
</div>
</div>


I work at a company IT dept that never used sequectial number ID columns in data tables. They insist on using unique data per row in the ID column because the data (part number) makes more 'human readable' than a secequence number.

Q. What is the best practice?

SQL ID Column Uses Unique Row Data Vs Sequence Number?

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.