SQL Server actually will not use the page file unless the server is under duress. Page file access is very slow compared to RAM access, so SQL Server aims to do everything in RAM.

Is it a 64-bit instance of SQL Server? If so, then what you did with the min and max memory is fine as a starting point. Just monitor the memory usage of the server to ensure there is always a few hundred megabytes free for the OS to use at its discretion.

If the instance is 32-bit then setting max memory to 3GB is not going to have much effect at all whereas setting a 2GB minimum could impact some things. If you could check the boot.ini file to see if the /3GB switch is being provided on the startup command as well as post the results of this select-query when run against your instance we can get to the bottom of it and get you a solid configuration:

-- memory overview

SELECT CAST(physical_memory_in_bytes / (1024.0 * 1024.0 * 1024.0) AS DECIMAL(20, 2)) AS PhysicalMemoryGB,

CAST(virtual_memory_in_bytes / (1024.0 * 1024 * 1024) AS DECIMAL(20, 2)) AS VasGB,

CAST((bpool_committed * 8) / (1024.0 * 1024.0) AS DECIMAL(20, 2)) AS BufferPoolCommittedMemoryGB,

CAST((bpool_commit_target * 8) / (1024.0 * 1024.0) AS DECIMAL(20, 2)) AS BufferPoolTargetMemoryGB,

(

SELECT CAST(CAST(value_in_use AS INT) / 1024.0 AS DECIMAL(20, 2))

FROM sys.configurations

WHERE name = 'min server memory (MB)'

) AS MinServerMemoryGB,

(

SELECT CAST(CAST(value_in_use AS INT) / 1024.0 AS DECIMAL(20, 2))

FROM sys.configurations

WHERE name = 'max server memory (MB)'

) AS MaxServerMemoryGB,

(

SELECT value_in_use

FROM sys.configurations

WHERE name = 'awe enabled'

) AS IsAweEnabled

FROM sys.dm_os_sys_info;

Please check out this book when you have some time: Troubleshooting SQL Server: A Guide for the Accidental DBA By Jonathan Kehayias and Ted Krueger. The whole book is fantastic but Chapter 4 is immediately relevant for you.