NO!

If you mean a file backup of the log, that will trash your database. DO NOT ever restore database files from a file backup unless you know exactly what you're...

Well that would explain why the log isn't growing.

Looks like problems with drive or file system. Got a system admin there?

So you have an open transaction that's preventing log reuse. Could be that the autogrow increments are too small and the log isn't growing fast enough. Could be that the...

Can you post the exact error you're getting?

Stop shrinking your log file!

You're just wasting resources, both in the shrink and when the file regrows (which it will have to do), as well as slowing your app down...

Either you've also got transactional replication that's not running, or the CDC jobs are not all running properly. Only two ways you'll have long-lasting REPLICATION log reuse waits and a...

Please post the involved queries and the deadlock graph

lilywhites (12/4/2014)

---

its gone from checking out a work task until its completed to something that can track the user logins, task assignments, task start, task end, task timeout, task reassignment,...

If they're not running, yes.

Do note, by running the repldone commands, you're invalidated the CDC stuff and lost...

You have a transactional replication publication? Is the log reader agent not...

No, it can not. Full recovery model and no log backups results...

Page latch, don't know, would need to see the exact resource.

The latch wait is related to parallel table scans. Tune your queries to avoid large table scans running in parallel

ASYNC_NETWORK_IO...

Partitioning is not a query optimisation technique. It's for data management. If you're trying to make queries faster, stop looking at partitioning.

https://www.simple-talk.com/sql/backup-and-recovery/the-sql-server-instance-that-will-not-start/