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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-09-29 : 08:03:46
|
| Innes writes "I need to remove replication from my SQL7.0 Server. The automatic deletion process has failed, but done most of the job, leaving me with a problem..There is one merge article left, a table with 1.5m records in it. This is blocking the deletion of replication, because it is unable to remove the article. The reason it gives is that the transaction log is full. I have increased the available size of the log to 5Gb, for a database that is only 8Gb itself. It still fills up. I have no additional capacity to provide, so am trapped in a vicious circle! I have truncated the transaction log prior to attempting deletion, still runs out of space. There must be a 'manual' way of dropping this article, but i can't figure out how. All system methods fail as does the sp_dropmergearticle procedure.Any help very much appreciated!Innes" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-09-29 : 11:12:42
|
| You might have to delete the records from the actual tables instead of using the system stored procedures. Replication tables can be found in the destination database, distribution database, and in the master database. The tables that you are interested in are the ones that start with MS*. I once had to manually delete replication as well, and I was able to figure out which table to delete from in about 5 minutes, so it wasn't that difficult to find. I don't know the exact table to delete from to fix your problem, but I am sure that you can find it given the information that I have provided.Tara |
 |
|
|
|
|
|
|
|
Removing Replication