HestonJames
Programmer
Guys,
How would you guestimate the amount of RAM that is required for your instance of SQL server to run efficiently, I've found a few discussions on the web about it with one or two suggesting that you should use the datafile size for your database as a rough gauge as to how much RAM you need in the machine, is that correct?
In this particular scenario we have a single database attached to the server which has a data file of about 1.8GB and log file of about 5.6GB.
Presumably we want enough memory for SQL to be able to store any data which its handling for queries so that it doesn't start caching on the disk (which is what I think is happening at the moment). Is there any nice way of seeing how large the datasets my queries are generating are?
I'd be interested to hear your thoughts on this.
Heston
How would you guestimate the amount of RAM that is required for your instance of SQL server to run efficiently, I've found a few discussions on the web about it with one or two suggesting that you should use the datafile size for your database as a rough gauge as to how much RAM you need in the machine, is that correct?
In this particular scenario we have a single database attached to the server which has a data file of about 1.8GB and log file of about 5.6GB.
Presumably we want enough memory for SQL to be able to store any data which its handling for queries so that it doesn't start caching on the disk (which is what I think is happening at the moment). Is there any nice way of seeing how large the datasets my queries are generating are?
I'd be interested to hear your thoughts on this.
Heston