Re: Transaction log with huge proportions
- From: "Geoff N. Hiten" <sqlcraftsman@xxxxxxxxx>
- Date: Tue, 28 Jun 2005 16:58:05 -0400
Set your database to SIMPLE Recovery (Enterprise manager, Right click on
database name .. Properties | Options tab.)
>From Query Analyzer
Use <myDatabaseName>
DBCC SHRINKFILE (<LogicalLogFileName>,<desiredSize>)
You may have to run the command a couple of times.
See BOL for syntax and warnings. And read that chapter I mentioned. Twice.
Soon.
Geoff N. Hiten
Microsoft SQL Server MVP
"francisco - Portugal" <f_batista69@xxxxxxxxxxx> wrote in message
news:D8B2DD82-47FF-437F-B89A-0EEE62E29B55@xxxxxxxxxxxxxxxx
>I konw that i lack some skills, i'm still taking microsoft courses. But
>this
> is an emergency, the problem is that i don't have available disk to run a
> backup, do you have any suggestion?
>
> Please.
>
> --
> Francisco Batista
> Portugal
> f_batista69@xxxxxxxxxxx
>
>
> "Geoff N. Hiten" wrote:
>
>> Your problem is not cluster-specific. It happens on many SQL servers
>> both
>> clustered and non-clustered. You need to manage your transaction log.
>> First, read books-online and learn about SQL Backup and Recovery. You
>> need
>> to decide if you need point-in-time recovery or will a daily/weekly
>> recovery
>> work. If you want point in time recovery, you will need to set up a
>> regular
>> log backup process, otherwise you can set your database to SIMPLE
>> recovery.
>> Once you have the log settings managed correctly, you can use the DBCC
>> SHRINKFILE command to reduce the log down to a normal size. You will
>> need
>> to determine the optimum log size for your specific application. Again,
>> read the chapter on Backing Up and Restoring Databases under
>> Administering
>> SQL Server in BOL for a complete discussion of all the concepts involved.
>>
>> Geoff N.Hiten
>> Microsoft SQL Server MVP
>>
>>
>>
>> "francisco - Portugal" <f_batista69@xxxxxxxxxxx> wrote in message
>> news:884D5523-D0E7-4487-81F9-2E7C1628CBC4@xxxxxxxxxxxxxxxx
>> > Hi all
>> >
>> > My SQL Cluster, has a database with 13Gb, but the transaction log is
>> > huge.
>> > I
>> > already stopped the file from gowing more then it it's but is there a
>> > way
>> > of
>> > reduce this file?)already try to shrink the file without sucess). Can i
>> > for
>> > instance, detach the database an start it with a new log? Or there's a
>> > way
>> > of
>> > forcing the compression of the transaction (ldf) log.
>> >
>> > Best regards
>> > --
>> > Francisco Batista
>> > Portugal
>> > f_batista69@xxxxxxxxxxx
>>
>>
>>
.
- Follow-Ups:
- Re: Transaction log with huge proportions
- From: francisco - Portugal
- Re: Transaction log with huge proportions
- References:
- Transaction log with huge proportions
- From: francisco - Portugal
- Re: Transaction log with huge proportions
- From: Geoff N. Hiten
- Re: Transaction log with huge proportions
- From: francisco - Portugal
- Transaction log with huge proportions
- Prev by Date: Re: Transaction log with huge proportions
- Next by Date: Removing a SQL cluster node
- Previous by thread: Re: Transaction log with huge proportions
- Next by thread: Re: Transaction log with huge proportions
- Index(es):
Relevant Pages
|
