You have a database named DB1. You plan to create a stored procedure that will insert rows into three different tables. Each insert must use the same identifying value for each table, but the value mu

A SQL Server SEQUENCE object is an independent database object that generates numeric values in a defined order, incremented by a configurable amount, and can be reset to its starting value at any time using ALTER SEQUENCE with RESTART WITH. Because it exists independently of any table, a single sequence can supply the same value to multiple INSERT statements within one stored procedure invocation, satisfying the requirement for a shared identifier across all three tables.

Choice B is identical in wording to Choice A and is a duplicate option; A is selected as the canonical best answer, making B redundant rather than a distinct solution.

A fourth table could store the next value, but it introduces concurrency risks (e.g., dirty reads, update anomalies) and requires additional locking logic that a native SEQUENCE object handles automatically and more efficiently.

An IDENTITY column is scoped to a single table and auto-increments independently per table, so the three tables would generate different, unsynchronized values; additionally, IDENTITY values cannot be easily reset without truncating the table or using DBCC CHECKIDENT, making it unsuitable for a shared, resettable identifier.