Don't fall into the trap that the minimum requirements for SQL are sufficient
as this is rarely the case. The information from Microsoft is merely a
guidance as every implementation will have a different loading on SQL. 4GB
is recommended where SQL is installed on the same server as Project Server as
there is a significant amount of processing required to manage web browsing,
server side events, PSI calls, server side scheduling, queue management etc
etc etc.
On top of SQL DB, and Project Server memory is also likely to be required
for OLAP, SQL Reporting Services, oh and the OS itself.
You can monitor SQLs performance by checking the following perfmon coutners
(thresholds available from books onlines)
1. Memory
a. Available Bytes
b. Page Faults/sec
c. Pages/Sec
2. Network Segment
a. Bytes Received/Sec
b. Bytes Sent/Sec
c. Bytes Total/Sec
3. Disk I/O
a. Physical Disk - % of Disk Read Time
b. Physical Disk - % of Disk Write Time
c. Logical Disk - % of Disk Read Time
d. Logical Disk - % of Disk Write Time
e. Physical Disk - Average Disk Queue Length
f. Logical Disk - Average Disk Queue Length
4. Processor
a. % Processor Time
5. System
a. Processor Queue Length
b. Context Switches/Sec
c. Threads
6. SQLServer: Cache Manager Object
a. Cache Hit Ratio
7. SQLServer: General Statistics Object
a. User Connections
8. SQLServer: Database Object
a. Transactions/Sec
Of course you can install all of the components will less than 4GB of
memory, but tests have shown that the solution will generally under-perform.
A large factor is the number of projects, users, reports etc and how often
they interact with the solution.
Check out the planning guide at
http://technet2.microsoft.com/Offic...52d2-4967-ab9d-0e199c9bf0041033.mspx?mfr=true
HTH
