Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
lkerznowski
Starting Member
22 Posts |
 Posted - 2014-10-17 : 11:36:39
|
It just came to my attention thousands of errors on one of our database servers. After researching, I found that the SQL Database is still trying to update transaction logs from a retired server.Basically, we use to have two DB servers DB1 and DB2. DB1 was shipping to DB2, but then we had an issue where DB1 basically broke and needed to be replaced.We ended up just creating DB3, and retiring DB1. Right now, DB2 ships over to DB3.Problem is, when looking at the log reports on DB2:It shows the successful shipping to* db3... but it also has latency errors as there is still a connection point to the old server (DB2 is still trying to act as a secondary server). Can someone help me drop that existing connection? |
|
|
lkerznowski
Starting Member
22 Posts |
Posted - 2014-10-24 : 16:04:17
|
| Any thoughts? |
 |
|
|
mariachi202
Starting Member
2 Posts |
Posted - 2014-10-25 : 05:51:46
|
quote:
Originally posted by lkerznowski
Any thoughts?
Right click the DB in question, go to Properties -> Transaction Log Shipping and then untick the Enable this as a primary database for... option. Click OK.EDIT - just read through your post.You should probably clear all the Secondary instance options under Transaction Log Shipping. |
|
|
|
|
|
|
Help Closing old Log Shipping Connection