Cluster...

When you add the keyword, you're probably preventing the physical shrinking.  If you really want to shrink, just shrink:

DBCC SHRINKFILE (N'prod1', 0)

I wouldn't use 0 personally...

set ansi_nulls off 
I'm trying to find a way to avoid having to use isnull() or coalesce() everywhere in my script in order to avoid counterintuitive null comparison results...

I swear I posted this already (somewhere at least!, another SQL help site perhaps?), but I'll post it here too just in case:

SELECT EmployeeInformationID, COUNT(*)...

Although not considered "standard", I prefer this approach because (1) the FETCH only has to be written once (can't count the number of times someone changes only one FETCH when...

Rather than repeatedly having to identity the post code, add an AFTER INSERT, UPDATE trigger that finds the post code and then store its byte location and length in a...

The way I read it, you could have letters on both the front and the back of the string.  This CASE code handles that situation as well:

[code...

A tightly-written standard scalar function is another option.  I'll give you mine.  But you'll have to add the UK post code part to it, since this code was not written...

Did you verify that all the constraints are "trusted"?  If not trusted, perhaps that could cause an issue.

A cross tab will do it nicely.

SELECT
    MAX(CASE WHEN rowOrder = 1 THEN xImage END) AS xImage1,
    MAX(CASE WHEN rowOrder...

If the app/person/whatever doing the UPDATE is not a sysadmin, (or perhaps a dbo, not sure on that one), maybe you can just DENY UPDATE on that column:

            
July 10, 2018 at 11:43 am
            
#1997036

            
            
                                                
        

Another option is to create a proc in master named sp_<whatever> (the name must start with sp_), mark it as a system proc, then you can execute from any db...