mutley1
MIS
- Jul 24, 2003
- 909
Hi all,
SQL 2000
I've got a replicated database that we restore to our DEV server nightly, and recently I have been looking for space to clear off to create a new test DB (temporarily). One of the main items I can regain space from is the restored distributed database log file by shrinking it down. I get the usual "cannot shrink the log file because there are distributed transactions at the beginning of it" message, so I run
This returns "The database is not published". We do not have distribution set up on the DEV server - is there a flag I can tinker with to fool the DEV server into thinking it is published, then run the repldone so I can shrink the log file?
TIA.
Rgds,
M.
SQL 2000
I've got a replicated database that we restore to our DEV server nightly, and recently I have been looking for space to clear off to create a new test DB (temporarily). One of the main items I can regain space from is the restored distributed database log file by shrinking it down. I get the usual "cannot shrink the log file because there are distributed transactions at the beginning of it" message, so I run
Code:
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
TIA.
Rgds,
M.