|
|
Posted by tlyczko on 09/27/06 13:09
Hugo Kornelis wrote:
> Seperate locations for data and log files are always good.
> The data file requires lots of random access, i.e. lots of head
> movement. Luckily, SQL Server buffers data read from the data file, so
> recently used data doesn't have to be read from disk again. Writes are
> buffered as well.
> The log file is mainly written to. These writes have to be completed
> before SQL Server will signal the client that an operation is finished.
> So write performance on your log file is critical to performance. Since
> all log writes are sequential, you can gain a lot of performance if you
> have the log file on a dedicated disk - the heads hardly have to move
> and you write performance is it the highest possible rate - increasing
> the time to completion for yur transactions.
Thank you for explaining...particularly to people like me new to this
software.
However, this test DB is only a few meg for now...it'won't grow very
fast.
We do however have a production SQL server though with Great Plains and
perhaps later another SQL-based app.
Is there any sort of general guideline as to what database size(s) that
this sort of thing becomes particularly important?? Such as DBs over 4
GB or over 6 GB for example??
Thank you, Tom
Navigation:
[Reply to this message]
|