Discussion Locked

When to move SQL from the BDC to it's ow

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
In a basic installation we install SQL7 and SQL2000 on the domain controller with at least 256 k of ram. When, should you consider moving the SQL to it's own server?What are the basic guidelines?

1 reply

by chuckmentz

We run into similar questions for SQL. While I cannot specifically answer your question, I can tell you some of the things we find helpful:

1. Make sure you have enough physical RAM to cover the size of your largest table plus another 10 percent.

2. Use a Raid 5 (or better) configuration for the drives, not only for durability but also for speed.

3. Microsoft SQL server is designed to use memory, SQL should be using about 80% of the memory available. If not SQL is idling (doing absolutely nothing) or is being squeezed out of necessary RAM by other applications. Adding more memory usually is the fix for problems along this line. The memory usage is easily viewed in the performance monitor settings included with SQL 7 (Total Server Memory).

This discussion is closed to new replies.