|
[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 Sigh_Man in SQL Server 2005
I have a user whose SQL Server 2005 Express is growing out of all proportion to the amount of data actually being stored. On all other machines the mdf file is no more than 20MB and the log file perhaps a few hundred KB. This user's MDF file is in the hundreds of MB and the LDF is 40MB!
Now the backup has started to fail due to timeout.
1. What are the possible causes of this abnormal growth rate, and
2. What are the possible solutions
3. Short term fix (apart from shrinking the files in SQL) how can I extend the timeout so that the backup at least runs
20091111-EE-VQP-89 / EE_QW_2_20070628