×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Bill,
Thanks for the links. Already tried the backup which should have
truncated the log but it still wouldn't shrink. System had been rebooted
several times as well as taking the DB offline which should have
committed or rolled back outstanding transactions.
We had to get the current application going so the users could get back
to work, so left the "archive" DB offline and after copying the log file
to an external hard drive we deleted it. If we really have to we may
play with the file again. Either by pointing SQL to the log file on the
bigger external hard drive or seeing if the system can create an empty
log file without corrupting the data.
Roger Vicker, CCP
On 8/1/2011 1:38 PM, Bill arranged the binary bits such that:
On 07/28/11 8:36 PM, Roger Vicker, CCP wrote:
I am looking for an SQL 2005 expert.
Anybody got a way to preserve the DB contents and shrink the log back
down to a reasonable size?
I'm no expert, just did a DogPile search and came upon this:
http://support.microsoft.com/kb/317375
Maybe more helpful is this:
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=56434
Bill
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
