Damian

Does this help?

John

If I've seen correctly through your illogical naming convention and the fact that your column headings are in the wrong order in your desired results, this should work.  But only...

That will only show the most recent plan for the stored procedure in the plan cache.  Query Store in SQL Server 2016 and above may help.  Otherwise, you'll need to...

Or just put it in the SELECT:

DECLARE @ReturnString nvarchar(max) = 'Flat 24 Loddon House';
SELECT @ReturnString = SUBSTRING(
        STUFF(LTRIM(@ReturnString),1,LEN(Candidate),'') -- part
    ,   PATINDEX('%[A-Z]%',@ReturnString),LEN(@ReturnString) -- number
        )

If all you want to do is remove the cursor from your function, this should work.  It assumes that (apart from the number) there is no more than one "Part"...

I don't think so, no - that's the amount of space the plan takes up in the cache.

John

Default fill factor doesn't matter too much provided that you consider the fill factors individually for each index you create.  0 is fine for indexes with a monotonically increasing key,...

Yes, I chose option 4 for that reason.  It's correct, and although it entails more steps, it's less disruptive since you don't have to take the database offline.

John

Does the Index Optimize job keep a record of what indexes it's rebuilt?  If it does, there's your smoking gun.  If it doesn't, content yourself with having found the most likely...

Not much you can do after the fact.  Look at the time that the log last grew (it will usually be the last modify time of the physical file).  Where...

How about this?  It's probably possible to tidy it up so it only does one table scan, instead of two, but I'm afraid I ran out of time

Don't run DB tuning advisor.  Use the missing index DMVs instead.  Query tuning isn't easy - I hope you don't mind my saying that I think you might be in...