Yeah, I get that error more often than not. It drives me nuts.

I consider my SQL knowledge at an intermediate level, but my support team relies on me as their primary source when they need help, so who do I go to?...

Oh, the index defrag is done before 6am on Sat morning if that's what you were asking and all full backups are completed prior to 5am across the board. Nothing...

I do get a backup file despite it reporting a failure. The resultant problem was that because the job found a failure it had stopped deleting old backup files and...

The Saturday jobs run at 4:30 am and are done before 5am. The defrag runs at 5 am, and when it's done a full backup is done of just the...

I'm positive someone didn't run a manual backup, the server doesn't have space for more than the scheduled backups and the customer knows that. They wouldn't have hit this database...

I often have to go digging in system tables and in distribution to do cleanup when there are lingering pieces of replication that don't exist on the other side, therefore...

Ok, I finally got it. I had to stop every service in the SQL Service Manager to gain access to it.

The ODBC connections set up have no logging enabled at this point that I can tell. I only saw the one in there that had been pointing to that file,...

That did the trick, thanks!

I have a fully replicating set of servers, and I'm replicating the last 90 days of data to a tertiary server with merge replication. It's merge rather than snapshot, so...

I don't think it's a problem, I think it tallies from multiple sources and I'd just like to know what.

Thanks for the Profiler idea, that's a good one. I...

I'm referring to the conflict table itself, conflict_mydb_mytable. The process creating the conflicts isn't the issue, some are because a record was edited on one side, and deleted on the...

We have a second process outside of SQL that the records will go through that passing more than 10K records to can interfere with so I can't do more than...

Order of rows updated. And I understand SQL normally works oldest to newest rows. I'm curious why I've been told to do it opposite and can't find a good reason...