It is preferable to use SCOPE_IDENTITY() instead of @@IDENTITY

SCOPE_IDENTITY() returns the last identity value generated within the same scope (i.e. within the stored procedure)

CREATE procedure GetCounter @tableName...

deleted duplicate

• This reply was modified 2 years, 1 months ago by Jonathan AC Roberts.

Using UPDLOCK and HOLDLOCK

This approach allows you to acquire the necessary locks to ensure serialization without using the SERIALIZABLE isolation level.

CREATE PROCEDURE dbo.sp_GenerateNextNumber (
@SequenceKey nvarchar(10),
@ReferenceNumber nvarchar(25) =...

The first 3 rows out of...

Install this TVF.

Then this SQL will do the job

select x.value value1, x.value+1000001 value2
  from dbo.GENERATE_SERIES(-999999999,+999999999,1) x
;

Heh... Ok... since you brought it up, what prompt(s) did you use?

The key here is, again, the folks answering the questions shouldn't have...

Here you are courtesy of ChatGPT

-- Create TableA
drop table if exists TableA 
drop table if exists TableB 
-- Create TableA
CREATE TABLE TableA (
    JoiningID...

• This reply was modified 2 years, 1 months ago by Jonathan AC Roberts.

And yet it's still absolutely stupid about certain "simple" things...  In the example below, this is NOT the right way to solve the given problem.  Even the note in...

It's faster to rebuild indexes offline.

You might also be able to get it to rebuild in parallel which will be faster: https://learn.microsoft.com/en-us/sql/relational-databases/indexes/configure-parallel-index-operations?view=sql-server-ver16

But I think the question needs...

Is this what you are looking for?:

https://learn.microsoft.com/en-us/sql/relational-databases/showplan-logical-and-physical-operators-reference?view=sql-server-ver15

.

• This reply was modified 2 years, 2 months ago by Jonathan AC Roberts. Reason: deleted duplicate post

Why would you want to do it without a union and in...

It already is one query.

I'm not sure if this will fix it but the first thing I would try is to make sure the statistics have been updated:

UPDATE STATISTICS...

I'm not sure if this will fix it but the first thing I would try is to make sure the statistics have been updated:

UPDATE STATISTICS dbo.mytable WITH...