Advertisement

10.07.2008 at 02:46PM PDT, ID: 23795481
[x]
Attachment Details
[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!

9.3

How to take advantage of lots of memory with SQL Server 2000

Asked by fischermx in MS SQL Server

I recently upgrade the hardware for a SQL Server installation to an 8 CPU / 16GB of memory (prior was 4CPU /  8GB). The database it use is about 70Gb, it is an accounting db. It uses Windows 2003 Server Enterprise Edition and SQL Server 2000 Enterprise Edition.

I'm not sure if I'm taking full advantage of the 16GB.
The reporting works a lot faster, and seems everybody is happier, but I think it may go faster.
For example, if I get a report "X" on a range of date, it take about a minute on the first run, the on second run it takes 5 seconds, so, on 3rd and 4rd and consecutive runs. I understand that this has to do with SQL Server cache. But I wonder, why not make it 5 seconds since the first run?
I remember in the past (years ago) I used to "pin" tables in memory, but now, even with 16GB, I can't pin the posting table at all.

Any ideas are welcome.


Start Free Trial
[+][-]10.07.2008 at 03:36PM PDT, ID: 22664588

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: MS SQL Server
Sign Up Now!
Solution Provided By: dtodd
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 - Hierarchy / EE_QW_2_20070628