Database files never reduce in size automatically.

Don't run that backup with truncate only. That's just a log backup which doesn't write the backup file, no special magic in it. However...

Nothing to do with the ORDER. Derived tables always need an alias.

Edit, and...

Database files never reduce their size automatically.

And I would strongly recommend against going and putting page compression on all tables. Have you tested the performance? Is the CPU overhead of...

Without seeing the execution plan, vague guess. Index is not covering and too many rows are being returned to make index seek + all the key lookups efficient.

SQL doesn't have block scope for variables.

From Books Online (DECLARE)

Why?

MSDB shouldn't see heavy usage, not to the point of being a concern around size of cache plans.

Very first sentence in the section "Include columns"

http://www.sqlservercentral.com/articles/Indexing/68636/

It does not. That's generally something that you do in source control.

Don't flush the plan cache. All you're doing with that is forcing SQL to do more work to recreate the plans. You're going to be hindering performance by doing that,...

The reason is right there in the message.

'Failed to open a file. Access is denied'

Whatever user is trying to access the file does not have permission on either file or...

In that case, why are you even bothering to do the checks? Just do the insert and then run the select.

Generally, when someone writes code that:

- Checks if a row...

Yes

Not of includes

Note : If these indexes have been automatically created by DBA based automatic analyser suggestions and...

Set the log to the size it needs to be for regular operations, configure a sensible autogrow, then leave the file alone. Stop shrinking it and forcing it to regrow.

Hence will be failing,...