The problem is that you multiplied the minutes difference by 60; just get rid of the "60*".

SELECT  CONVERT(CHAR(5), DATEADD(MINUTE, (DATEDIFF(MINUTE,CAST(@hFrom +':'+@mFrom AS TIME), CAST(@hTo +':'+ @mTo...

> Missing the point on this last one - you have multiple joins, not just 1 join. <<

It depends on how you look at it.  The view itself has only...

DECLARE @job_name nvarchar(128)

SET @job_name = 'JobA'

SELECT
    job_name AS name,
    COALESCE(CAST(j.enabled AS varchar(1)), 'Job not present') AS enabled,
    CASE...

For SQL Express, you'd need to use the task scheduler in Windows directly, instead of using SQL Server jobs.  It's more of a pain, but it should work.

You should explicitly...

That's why I put the note: my EXISTS example does NOT reference an outer table.  A rare situation perhaps, but not impossible, more likely:

WHERE EXISTS(SELECT 1 FROM sys.tables WHERE name...

Wouldn't that count every reference as a "join", including a select from a single table?  And any other single select from a table.

SELECT ...

FROM dbo.table1

SELECT ...

FROM dbo.table1

WHERE EXISTS(SELECT 1 FROM...

I think should be pretty accurate, at least without going to a lot more trouble to write.  Yes, it uses recursion, because we need to find every JOIN.  If somehow...

When using NOT IN, you should make sure a NULL value does not appear in the results.  For example, like below.  Try that first and see if it cleans up...

SELECT T1.DocumentNo, T2.LongSentence

FROM Table2 T2

INNER JOIN Table1 T1 ON T2.LongSentence LIKE '%' + T1.DocumentNo + '%'

Yes, yes and yes, as long as the proc not being EXEC'd by each other.

That is, this should work fine:

--ok

EXEC sp1

EXEC sp2

EXEC sp3

because SQL will clear temp tables created within...

Here's my version, also no recursion, with added alias names for more clarity:

SELECT 
    start_date, end_date,
    full_weeks * 2 +
 ...

Sorry to the OP for this bit of a side issue.

As noted by others, there's no easy, sure way to know which tables are / aren't being used.  Periodically capturing...

Since it's based on name, I just exclude tables that start with 'tmp_', 'temp_', 'work_' or 'wk_'.  Seems just as easy as excluding schemas to me.  And I don't have...

I don't use separate schemas (nor would I personally recommend it, given the general hassle of it -- different approaches for different folks).  How does one resolve it when the...

Again, as I stated, it took only 1 more byte to store YYYY vs YY.  Dates were stored as numeric and not char, also to save space.  YYMMDD...