Mu DB Log Shrinking

|| Database Log Shrinking ||

Well, i was searching for a way to reduce logs, coz my server logs grew more than 10 gb and my machine was getting slow, but i didn't find any explanation wich worked, so i did this:

http://img220.imageshack.us/img220/6228/logfilede1.jpg
EDIT: that spot with the number wont be the max file size, it will be the final log file size (sorry guys)


the code is :

Code:

---

BACKUP LOG MuOnline WITH TRUNCATE_ONLY DBCC SHRINKFILE (MuOnline_log, 50)

the number 50 in there is where you have to put a number (in mb's)
that will be the log file size after you ran the query

---

also dont forget to do this after you shrinked your logs:

http://img522.imageshack.us/img522/3259/logfile2na9.jpg


thanks, 0dark

Note: if this is in the wrong section PLEASE MOVE IT !!!

sounds good. how much will it shrink it by?

by the number of mbs you put in the spot shown in image1 (i think i explained wrong in the first image, that number wont be the max file size, it will be the log file final size :P)

im really sorry for the mistake guyz

lol man when i used ur guide my database file size now 53MB before 13MB waaaa is it normal? what a, i want to shrink database to shorter the file size not to add more and more omg...man tell me how to put it back to original size...damn this guide is not good for me =( sorry

i think its normal, its like empty spaces in the db wich use that space, but when it logs, it overwrites those empy spaces, so it wont grow, it will remain like this...

i could be wrong tho :P

looool, so put a size that is smaller than your file actual size on the final log size spot, not a bigger one

when you are truncating data, lines are ereased to give space to new ones, so, when i shrink the data of the db log, the older lines are ereased to give space to others, thats how the db log size limit works, it automatically truncates the log files when it grows more than the max size. but when you put a higher number on the final sise (BACKUP LOG MuOnline WITH TRUNCATE_ONLY DBCC SHRINKFILE (MuOnline_log, 50)), new blank lines with the null value are added to bring the file to the expected size, so, if you shrink your files to a higher number than it actually is, youre doing nothing more than adding unusefull data to the log (wich isnt really smart

nvm, i think my serverfiles already has a script for shrinking databases, my muonline_log now 502kb, i just turn off the service manager then delete the file, and then when i turn it on, it makes another muonline_log wif 502kb without lossing any data.

its not good for the mssql deleting log files, coz if you have any problems with the database, you dont have the last logs you had and you wont be able to restore it, when you shrink it you keep the last logs. also, if your mssql get unable to create the log file(missing dlls or smth like that) your db will crash and you won't be able to save it, coz mssql dbs dont work without log

Does this thread need to be moved on guide section?.. btw you can also do shrink using mueditor 2.1 backup your files first before doing so, thats what im using in my server

if you want to move ..
if its wrong here, id be glad if you could do this for me :P

Quote:

---

ts not good for the mssql deleting log files, coz if you have any problems with the database, you dont have the last logs you had and you wont be able to restore it, when you shrink it you keep the last logs. also, if your mssql get unable to create the log file(missing dlls or smth like that) your db will crash and you won't be able to save it, coz mssql dbs dont work without log

---

oh...ok i will shrink the database from now on ^^, btw i got a simple script before for shrinking database, its about 3 lines i think...so easy...just a script no anyother...but when i go back to the thread section the guide gone =( i want to use those script for my server =(, if u still got those 3 lines pls post i want to copy ^_^

me? three lines? i dont remember that man the only script i posted here after re creating myaccount was this one..

no, its someone who posted it and dunno who, i just copy his script and run into my sql query and it works...i am searching for the old-server-help guide coz i found it there...i think the thread now gone =(

nice

Nice man, it sure works?

offtopic: font name? :D

I suggest you do a little bit of researching before posting such "releases" /mods, you slackers, this ain't a release of nothing - or @least i don't see any files :P/

Okay people here's the deal:
Restricting the file growth of the Data or TL will result in your database becoming read-only once the limit is reached. Which means that the players won't be able to make ANY changes at all to their characters/accounts or anything that is located in the database you targeted.

If you want a simple method to clear a transaction log, write this down.

Code:

---

use master;
GO
backup log [MuOnline] with truncate_only
dbcc shrinkdatabase([MuOnline],0);

---

You will get a result chart from the shrinking, this query does not require your server to be offline and does not have any negative effects that you won't like, it shrinks the log to its minimum (blank) condition = 512KB or 1024KB (not sure). Sue me for 512K lawl!
You can create an scheduled task using t3h mssql server agent.
The query is executed in a short amount of time depending on the log size and your PC specs.

- Savoy.

its ok to shrink it, but if you restrict its growth, ur server wont store stuff... will be like rolling back again and again...

Quote:

---

Originally Posted by melo_yello

its ok to shrink it, but if you restrict its growth, ur server wont store stuff... will be like rolling back again and again...

---

wow, you think ?

is there an echo in here ^^

Wrong Section guy...
mods move it.

Good guide 10/10 ! its very helpful