Nice.  Don't feel bad, we have views that do this:

SELECT ...

FROM OPENQUERY(remoteserver1, '...')

UNION ALL

SELECT...

FROM OPENQUERY(removeserver2, '...')

UNION ALL

SELECT ...

FROM dbo.local_table

No way to match up all the sources to the destination for...

Does the function use schema binding?

Please provide the text of the function, naturally first obscuring any names you need to protect.

I don't see any way to do this.  A view could have columns from several different referenced entities and from no referenced entity at all (such as CREATE VIEW dbo.view_name...

SQL has an easy built-in way.  When the analysts are given SELECT permission, the DBA can add the "WITH GRANT OPTION" to their permissions.  That gives them permissions to grant...

No, that should do it, it must be something else.

Can you copy out the statements around where the error occurs and parse those directly and see if you can spot...

Or maybe you need this?!:

...

AND SOURCE_ID <> 100 AND ADDRESS <> 'NOT APPLICABLE'

Those statements look fine.  There must be one or more CREATE statements with some other syntax or name error which causes SQL to then misinterpret some SQL later on.

It's actually not a reserved SQL Server keyword.  [It is reserved in ODBC, but that's a...

You'll need to split the list of RelatedPlanNumbers, but that's easy enough:

AND PlanID IN
(SELECT
             ...

As I noted earlier, you could also pass values to the monitoring job to control the check time interval and/or the options for how many times to check on the...

Not exactly.

The first step in the main job is to start another job that will check on the first job, like this:

EXEC msdb..sp_start_job 'Automated Claim Closing Monitor'

The main job then...

Have the job you want to monitor immediately start a second job that will notify you if the run time is exceeded.  You could even have the main job pass...

Yes, I love the compactness and "slickness" of the code, but for large number of rows, performance-wise it can be a relative disaster.

Of course, in general, sorting is big overhead...

Idk why don't you give it a try and let us know

I never use IIF, so wouldn't waste my...

IIF is what leads to wordiness and complexity.  Here's a simple CASE, what wouldn't this take embedded IIFs?  [I admit this might be easier since I think(?), since I write...