Reply to Re: torn page detection and auto shrink: performance?

Your name:

Reply:


Posted by Matik on 02/27/06 09:45

Erland,

So I've changed the database model, and it seems to look much better
than it was before. And I have up-to-time recovery possibility.

This has no influance on perfomrmance, what I've noticed, so I'm very
pleased :)

There is just one more question bothering me.

Curently, database size shows 18GB, but the used space shows 8GB.
For a log file, it shows 8GB but the used space is 34MB.

With my understanding, it is better not to shrink these files, because
during running processes, sql server will expand size of the files
anyway.
Shirinking files, will cause that by expanding files, sql server will
need more time, because of generation more io traffic (right?).

But, from the other side, I do not need to keep this files so big!
(This probably remains big anyway from my old model, where I've also
have had not optimized "delete old data" cleaning job).

The question then is: is it better to shring time-to-time, or let say
now, the database files, or leave it just in this way?

Gratings

Matik

[Back to original message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация