Nope - can't suggest anything more than setting the max memory. SQL Server will take the max memory you assign it - and shouldn't take any more than that.

What you are really needing to look at is memory pressure issues? Again, SQL Server is not going to take more memory than is allocated - and in your configuration won't be able to use more than 2GB anyways.

So, you need to be monitoring for memory pressure - and not target memory/total memory on the server. These counters will just tell you if you have another memory leak issue - and not whether or not SQL Server is performing well with 2GB.