I'd suggest not disabling a trigger unless it's absolutely necessary, and it almost never is.

You can instead use CONTEXT_INFO() to pass a flag to the trigger to "tell" it whether...

In the future, actual SQL statements to create the tables and insert rows would be required. But, for this request, the code should do what you're trying to do,...

SELECT rtmi.ItemID

FROM tbl_RF_Tags_Map_Items rtmi

WHERE rtmi.TagID IN (1, 8, 62)

GROUP BY rtmi.ItemID

HAVING MAX(CASE WHEN rtmi.TagID = 1 THEN 1 ELSE 0 END) = 1 AND

MAX(CASE WHEN rtmi.TagID...

Also look at sys.sql_expression_dependencies (or, if SQL 2005 only, at sys.sql_dependencies). Naturally that view is only for non-dynamic SQL references.

Or just right-click on the table name in SSMS and...

In general, you can use an approach like below to efficiently determine if specific, multiple tags match for the same item. Naturally we'd need more details to get any...

So I guess the tblCall table has only one row? Otherwise @Call_Date could be set to any row value from that table. That would make it almost impossible...

You need to be aware that recursion will be much, much slower, and much, much more CPU and memory overhead, than a tally table.

You must cluster the table properly to get good performance from large tables. You can instead try creating gazillions of covering indexes, to cover each (major) query, but...

Just to clarify, a database backup does not fully back up the log. It gets only the active portion of the log necessary to bring that full backup to...

Assuming the login doing the table mod has authority to run sp_send_dbmail, it should work. If not, you might need to look at additional permissions or using EXECUTE AS...

SELECT UniqID

FROM #SampleData

GROUP BY UniqID

HAVING MIN(Code) = 'ABC' AND MAX(Code) = 'ABC'

As additional background, SQL estimates the memory it will need to do the sort ahead of time, based on its estimated row count and row size. If you end...

As has been noted, the tables are definitely wrongly clustered, and that is causing the bad performance. Because, as has also been noted, of the "junior error" of assuming...

Or this:

SELECT

OBJECT_NAME(fkc.parent_object_id) AS [Referencing Table],

fkc.parent_object_id AS [Referencing Object ID],

OBJECT_NAME(fkc.referenced_object_id) AS [Referenced Table Name],

fkc.referenced_object_id...

Maybe as below? I think you've overly complicated the date selection and caused the duplicates.

For best performance, the Diskspace_Global table should probably be clustered either on Date_ (with the...