Did you install SQL Server Express Advanced or LocalDB package (rather than "regular" Express)? They appear to be the only ones that actually install LocalDB.

On command line, what does

' A' is not equal to 'A' -- leading space in the in example):

SELECT * FROM #Results
WHERE 1=1 AND [Column1] in ('A') AND [Column2] = 'B'

What discrepancy?

Both queries should return nothing (if AnotherColumn is in SomeView), since AnotherColumn can't equal both 'XYZ' and '1'.

Is the leading space intended in 'XYZ'?

Negated/clarified by example

• This reply was modified 9 months, 1 week ago by ratbak.

The change in database focus only occurs within the scope of the dynamic sql session. Your "outer" session is still using whatever database you were using prior to executing sp_executesql.

You could use a parameter to let user choose server, & programmatically derive the connection string & dataset. See links below

Or -- not recommended -- you could embed all 100...

They are probably right. There is probably no value in that column (not to mention the ambiguous "ID" name) unless you are using an ORM or other tool/framework that insists...

What do you mean by "Update routine"? A stored procedure? A script? Or ORM or other C# code

If SQL code add something like

SELECT @@ROWCOUNT AS UpdatedCount

directly after...

• This reply was modified 11 months, 2 weeks ago by ratbak.

Just exclude first_name & last_name from the constraint -- per your new requirement, they are no longer part of the definition of unique.  e.g.,

CREATE UNIQUE INDEX ix_unique_email
ON...

4 versions of this post -- reply to https://www.sqlservercentral.com/forums/topic/between-datetime-statement-not-working-4 which seems to be the one being updated.

4 versions of this post -- reply to https://www.sqlservercentral.com/forums/topic/between-datetime-statement-not-working-4 which seems to be the one being updated.

4 versions of this post -- reply to https://www.sqlservercentral.com/forums/topic/between-datetime-statement-not-working-4 which seems to be the one being updated.

Just use UNION ALL between the two selects you're using for the inserts into the temp tables, and eliminate the rest.

Unintentional duplicate due to delay in save.

If it is truly indexed appropriately (and filtered indexes may be a part of that), then none of the other approaches may be needed to maintain performance at that level.

What...

@pitterson's response looked like it was ChatGPT-generated (especially given it was  a new user)