Thanks Phil,

As you say, it's not elegant, but it seems to work for me. I was checking if there was a better way, but this does the job so i'll...

Phil, yes my ERP has the PK/FK information but D365 generates new ones when creating its records (my ones get saved into a separate field for reference). I think that...

Thanks Jeffrey,

Based on what you're suggesting I might have thought that since the logon process has to work through all relevant groups then it would do so in a set...

Random selection... that's what seems to be happening.

Do you know if Microsoft document that anywhere as I have been unable to find it?

Looks like I needed to amend the collation of the subscriber db (dbS) to match that of the publisher (dbP) as after I did that and reinitialised the snapshot the...

Michael,

I think that you're agreeing with me that the automatic download, deployment and installation is not a good idea for SQL updates. I like the sound of using SCCM though...

In my research I've seen a solution to what you describe posted by Adam Bertram. Essentially he verifies a CU or SP and drops it into a predefined folder...

I do indeed have multiple versions as some of these are dictated by my 3rd party vendors. There is a risk with any version though as not all CUs seem...

It's been a while since I last updated this thread and have to report that I was unsuccessful in recovering the corrupt database. The team responsible for it eventually ported...

Yes, this is a SharePoint content database and not the 8964 errors are not the only ones being reported from a CHECKBD.
Unfortunately I've already tried a DBCC CHECKDB ('SP_Teams_02',...

I typically don't do the PHYSICAL_ONLY checks on my db's - perhaps I should, but in the case reported this is another teams and they don't do checks at all.

I've attached a copy of the results after running 
DBCC CHECKDB ('SP_Teams_02') WITH NO_INFOMSGS, ALL_ERRORMSGS;
against the production server as that shows slightly different results to the 'test'...

Here are the results of running:
DBCC CHECKDB ('SP_Teams_02_Corrupt') WITH NO_INFOMSGS, ALL_ERRORMSGS;
against the 'test' SQL instance db having already had a REPAIR_ALLOW_DATA_LOSS action run against it.

Ok, you've convinced me - I'll switch back to registered servers.
I started using them a while ago and liked the ability to run a script on multiple servers in...