The best way to work around that is to delete the unused content from the report server using Report Manager or programmatically using the web services methods. These methods would...

Glad to hear it went well! I liked how you really worked to understand what replication was actually doing at different points and how things worked - that probably helped...

Without the specific error from the SQL Server log when you get the login failure it's hard to say. I would check the logs for the details of the login...

Two different views where sys.databases status has the database status and sys.master_files status has the file status.

Detach doesn't do anything to lock files. With a lot of the posts, the...

It does lock some things up briefly and can take awhile due to that. And the number of articles definitely impacts things where the more articles, the slower the process....

One use would be for synchronization purposes - merge replication being an example. This article has an explanation of this and mentions some of the performance issues with this:

Primary...

One option would be to concatenate the values of the rows using for xml path and stuff - along the lines of:

SELECT DISTINCT ID, 
STUFF((
  ...

From the error, it looks like in Active Directory the default Read permission for the Active Directory Users and Computers container has been changed. You may want to check that...

Sometimes you can get around that error by running Setup.exe as Administrator - right click and select Run As Administrator.

Sue

I am having the exact same issue getting pronest to connect to the shared db on a windows 2016 server. I added the computer name/pw as a user on...

In any case (backup or snapshot) it's the same type of process which is really the same process for transaction replication in general. The log reader picks up the transaction...

That would make it simpler wouldn't it? But no it doesn't have to be static but the transactions since the last full backup would need to be in the distribution...

We are experiencing memory issue in one of the server  where we observed LATCH_EX is being caused by ACCESS_METHODS_DATASET_PARENT latch type and also CX wait type . I checked...

Oh I missed it was the log duh...thanks for following up Anthony.

Sue

Yeah it doesn't make sense. The only way I can see that happening is if the primary and secondary aren't communicating with each other when you execute the backup. Maybe...