SQL Server 2000 size maintenance

0 pts.
Tags:
Desktops
Management
Microsoft Windows
OS
Security
Servers
SQL Server
Hi, how are you? I have a question and would like to get help with. There is an article in this website called SQL Server 2000 size maintenance. In the article, the author mentioned that regardless of your hard drive size, having an unmanaged and large log file size would cause problems. Do you know what kind of problem that we would have besides running out of hard drive space? You can refer to the article at http://searchwinsystems.techtarget.com/tip/1,289483,sid68_gci1033401,00.html Thank You Very Much!
ASKED: September 3, 2005  9:41 PM
UPDATED: September 18, 2005  11:37 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Another thing to consider is the performance of any application when it has to read/write from/to a buffer (in this case, data and log files) that has grown extremely large. When they get too big and have to be pulled into system memory just to be “read”, they can cause some serious slow-down. On a not-so-sidenote, this is another reason to design and run efficient maintenance jobs.

At any rate, you’ll almost always see an option for just about any serious application that allows you to manage size and growth of these important application files.

HTH,

Harlin Seritt
Internet Villa: www.seritt.org

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • BrianSelzer
    Allocating disk space is expensive, and can cause fragmentation of the log file. If the log file is physically contiguous on disk, then the write performance is optimal for the disk subsystem. Fragmentation causes additional head seeks between nonadjacent tracks which are much more expensive and can severely degrade performance. You want to make the transaction log file large enough to prevent auto-growth between transaction log backups.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following