Ehm, guys...I'm new to this SQL2000 thing, so please bare with me. I migrated oxle to the SQL2000 database, and everything is looking pretty crispy. However, I just spotted in the SQL EM that my database is using 160 MB on the SQL server, 50 MB of which is the db itself, and 110 MB is used by the transaction log. Yesterday the transaction log was 60MB. Should I do something to prevent this transactionlog growing too big?<
-edit- Just to be sure, here's what I'm seeing in the Enterprise manager. Does this all look ok?
BTW ; I just noticed that the 'free space' in the database grew from 19 MB to 100 MB once the first daily backup was executed (I created a daily full backup to disk schedule). Do I understand it correctly that the transaction log is cleared after every database-backup?<
You can also shrink your database to clean up unused space.
Instead of "By percent" grow-up, you can set shorter like 1MB or 5MB depending on your traffic or bulk inserts. On transaction log or DB files.
With simple model, you won't have transaction log. However, transaction logs are not very curicial for most databases set for websites. It is best for mostly banking, finances etc or non-backed up recovery models.<
Topic Locked
Posted - 23 December 2008 : 11:22:09
