In feature 1 of this series I described a surrogate key architecture and explained how and why to use it. I also provided several tools to support the proposed architecture. In feature 2, I expanded on this theme with a collection of standard table columns and table-specific objects to support the framework. I also provided several tools to generate and manage CRUD routines.
This article offers some additional commentary about the use of SQL Server IDENTITY values as surrogate keys. I will describe several utility routines to help maintain a surrogate key database. I will also provide six stored procedures to implement the utility functionality.
Brian Walker Brian Walker is a senior database architect in an IS department that uses SQL Server 2000 and the .NET Framework. He has more than 25 years of experience in the IT industry with the last several years focused on databases and SQL Server. Walker is a software developer, database developer, database administrator and database consultant. He develops utility software as a hobby, including a large collection of SQL Server utilities. Copyright 2006TechTarget
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.
Home: Introduction
