|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by ankitmathur in MS SQL Server
Hi All,
A few questions about Log File usage in MSSQL Server 2000.
Q1. Does providing a table with Clustered Index causes Log File Space to grow ?
Q2. How can I reclaim OS Space from log file ?
Now a lil' insight on the system am working upon.
I have a database which has records in millions in some of its tables. So much so, the DB size has grown to above 80GB and Log file grown to 40GB+. This is after I recreated a new log file only recently. But the speed at which log file is growing is amusing me and leaving me with a lot of issues like unable to restore the database on any other machine as combined the DB is using such a big space that I get into a space crunch issue on my test servers.
My transaction log backups job is being run every 15 mins successfully. Transaction log size is also at a manageable 15MB avg size. But still log file is growing in bounds. Earlier it used to remain aound 20GB. But after I executed a clustered index on one mof the biggets tables of all I'm facing this issue.
Can someone help me decipher my two questions above and steps to manage this DB keeping the size in check ?
Thanks
Ankit Mathur
20091111-EE-VQP-91 / EE_QW_2_20070628
