Thanks, I looked this last week, stopped after I disabled the service, it's very odd that it started after the CU14 update but only on one SQL 2017 server, the...

I've had the same error since applying CU14 update a few days ago, before that this login failure wasn't there.

SP2 CU14 came out before SP3 but SP3 only contains SP2 CU1 to CU13, so CU14 is missing from SP3. My question is does anyone know what the consequences on...

Jeff, can you let me know what issues you have had with the striped backups, I would genually like to know so I can avoid any issues going forward if...

For backups I had similar, also things like CHECKDB, read the thread I posted, may have some answers for maintenance and backup:  https://www.sqlservercentral.com/Forums/1921328/Extremely-Large-Backup-Solutions 

Basically striped backups across multiple...

You mentioned it was clustered, Standard has a limitation on the number of nodes in the cluster so if it's a two nodes it's fine but any more and you need...

I have had none, best to install it on a test system first, test and also research it to see if there are any potential issues you may face as some...

I put the GDR patch on where I had installed only up to a service pack, so where I had SQL 2014 SP2 only I applied the GDR (General Distribition) patch,  where...

It's not one database so file groups wouldn't work, it's a Sharepoint farm with each content DB at the best practice limit of 200Gb, I'd rather have everything backedup all...

Fixed it, the whole thing needed to be on one line and not the way I broke it up into different lines like a SQL command.

There is, my copying it into here must have removed that somehow.  It executes fine as T-SQL outside of the sqlcmd wrapper, it's just when I try to put it in a...

I've managed to half the time the backups take by using striped backups, 10 different files, I have 5 mountpoints for the backup server so this figure seemed logical to...