November 13, 2014 at 9:31 am
I had a weird error on restoring a database this morning. We have some jobs set up in the early morning to restore copies off databases to use with Redgate compare tools. These jobs run nightly and have been running for x years.
This morning I awoke to a restore error on one of the databases.
SQL threw a Error 3165
Database was restored, however an error was encountered while replication was being restored/removed. The database has been left offline. See the topic MSSQL_ENG003165 in SQL Server Books Online.
We do not have any replication objects on this instance and was in a lost of what might have happened.
Anyone care to make a stab of what might of occurred?
November 13, 2014 at 3:51 pm
A little confused by what's going on. Red Gate (good choice) SQL Compare doesn't do backups and restores. It just compares databases to other databases, backups, scripts, source control, and then generates T-SQL. While you could automate this process and combine it with SQL Data Compare to move your databases and data between servers, it wouldn't be running a backup and restore operation.
But, the error you're getting sure sounds like a restore error, so I don't think it's related to those tools. Maybe you're using Red Gate SQL Backup?
Regardless, that error implies that replication may have been turned on or set up on that server, or, it's from a server that has it. Have you tried the information for the error message from the MSDN site?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 13, 2014 at 4:35 pm
Sorry to confuse you. This has nothing to do with red gate tools. This was just a restore of a database and we got this error. This was set up as a job in the early morning and I woke to the error.
There is no replication set up on the server.
The next time the restore occurred it was fine.
Just trying to find out what and why the error related to replication was thrown. I would like to find why it happen so I do not wake to the issue again.
November 13, 2014 at 4:57 pm
OK, that's weird. It just worked the second time? Huh... I'm stumped. That error is pretty explicit. It's not possible that someone has been mucking with the server?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 13, 2014 at 6:56 pm
No I'm the only one that manages them. I would have seen in the logs if replication was added as well.
It has me stumped. This is the first error like this one and we restore two databases nightly for couple years on this server.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply