No.  SQL doesn't really care which proc is using the index, and even trying to capture that kind of data about index usage would be huge overhead.  Indexes need tuned...

Do you pre-restore the full backup each time to speed up the next restore? (Assuming you have the disk space available -- and if not, you can get the space...

@@TRANCOUNT itself is fine, I think.  Does UPDATE increment and decrement @@TRANCOUNT as it processes?!

CREATE TABLE #foo (i INT NOT NULL);
INSERT INTO #foo(i) VALUES (0);
SET NOCOUNT ON;

SELECT...

How large is the log file?  The disk area for a log file must be preformatted, whereas data files do not (assuming you have IFI activated, which is standard now).

Do...

You would do that with view(s).  The ENCRYPT / DECRYPT would be only within the view(s).

The users don't have to query anything different, as you can make the original table...

You're welcome!  I'm glad it helped.  Interesting q to play with.

Maybe something like this?:

SELECT Item, Date1, Date2, Date3
FROM @headerTable
UNION ALL
SELECT
    Item,
    CAST(MAX(CASE WHEN week# = 1 THEN Quantity END) AS varchar(10)),
...

Yeah, this can be definitely done in a standard SELECT.

Do you want to show only the weeks that had a match or do you want to show all 52 weeks,...

I'm confused about a couple of things.

First, why do you only want to INSERT "field3" (really column3)?

There's no link or association to #FieldValues.  Surely there must be some columns missing...

SQL provide missing index info that you can use to help determine whether you need other index(es) or not, or even whether you need to change the clustered index to...

OK, technically, other queries in the same transaction that did the UPDATE could see it before committing it, in something like this:

BEGIN TRANS

UPDATE

SELECT

COMMIT TRANS

But not within the context of a...

Actually you'd get an error, since alias "s." is not defined.

The old value.  The new value can't be seen by a transaction modifying that table until the transaction's been committed.

You really need to provide directly usable table structures and data.  That is:

CREATE TABLE and INSERT statement(s)

CREATE TABLE #df1 /*or just df1*/

( version varchar(10) NOT NULL, host ... )

INSERT INTO...

SSMS is not great about how best to define indexes.

Would you be able to post the query and the DDL for the table, including the indexes?

And please confirm, are you...