...
(
SELECT 
EPName,
NTUserName,
ParsedUserName,
CAST(FileSize AS decimal(35,2)) AS FileSize, --<<--
SUBSTRING (NTUserName,0,CHARINDEX('\',NTUserName)) AS Domain,
...

SELECT DISTINCT GRPID, PLNCD, XPLNE, EXTNO, EffDate, TermDate

FROM History

WHERE MBRNO IN (SELECT MBRNO FROM dbo.Member_MRN_lkupAllMBRNOs(@strMBRNO))

ORDER BY EffDate ASC

How large (MB/GB) is the "History" table?

How is it clustered?

If it's a (very)...

In SQL Server, you can use DELETE from a table using a JOIN.  Just be sure to alias the table you're deleting from and DELETE from the alias, not the...

Sound like this to me?:

;WITH cte_pat_ordered_by_fac AS (
    SELECT *, ROW_NUMBER() OVER(PARTITION BY p.patient_id ORDER BY p.facility_id) AS row_num
    FROM patient...

--First, I'd strongly urge you to separate the binary data from the main table, which you can do using sp_tableoption.

--Page-compressing the main table will save considerable space, although it may...

Oops, quite true, since I did a combined trigger.

I suggest separating the INSERT and UPDATE triggers.  Then you can use INNER JOIN and not have to test for INSERT vs...

SET ANSI_NULLS ON;
SET QUOTED_IDENTIFIER ON;
GO
CREATE TRIGGER tblTriggerAuditRecord
ON dbo.tblOrders
AFTER INSERT, UPDATE
AS
SET NOCOUNT ON;
INSERT INTO dbo.tblOrdersAudit 
  ( OrderID, OrderApprovalDateTime, OrderStatus, /*...,*/ UpdatedBy, UpdatedOn )
SELECT i.OrderID, i.OrderApprovalDateTime, i.OrderStatus,...

The most flexible way is to use CROSS APPLY:

SELECT d.ID, ca1.Amt, ca1.AmtReason
FROM #data d
CROSS APPLY (
    SELECT TOP (1) Amt, AmtReason
   ...

Read uncommitted (RU) simply doesn't take out some locks, allowing for reads as data gets changed. This can result in incorrect data, missing or duplicate data. Honestly, a scary...

You could probably use TRIGGER_NESTLEVEL to do that.

I tend to use session context values instead, set via sys.sp_set_session_context and SESSION_CONTEXT(N'<key_name>').  If you want more info on this method, let me...

Do you have an index on table_a that covers the UPDATE query?  That could help prevent some contention.

You could also try to "help" SQL by explicitly "telling" SQL about the...

I agree with Steve.

Also, wouldn't you want the MIN() time for the LogOn?

The customer would have an identifying customer number and account number, and the ATM would have an identifying ATM number.

Therefore, the transaction would broadly only need to capture cust#, acct#,...

That join is not needed.

are the data changes made by a trigger included in the transaction, so that they are rolled back if the INSERT or UPDATE on the table...

The first big difference is that the second command is not valid, and thus won't run and therefore won't do anything.