May 13, 2009 at 4:23 am
While I know that SQL will welcome any RAM you happen to have lying around in your office cupboard, jamming a crowbar into the manager's wallet to (dare I say it...) "spend money" is something else.
For those not blessed with an MPs expense account, is there a nice easy to follow guide which recommends RAM per user connections which can use used as leverage to up the RAM? Currently my manager thinks that 3Gb is "a great deal" since it's 24 times more than his 486DX2 Windows 3.11 workstation he uses at home.
Yes I can show performance graphs showing 90% of available memory is used and therefore more is required but honestly this is like trying to get money back off the tax man.
May 13, 2009 at 4:50 am
Completly understand your circumstances, there used to be days when working as developer making a graphics application the PM allocated less 256 GB RAM and had to work on it.
Back to your question on RAM mapped directly to user load , you need to provide more details type of application you are using ? if the database is primarily for OLTP tx ?
Also OS details is it 32 bit or 64 bit ? etc
Microsoft website has performance statistics in this regard for you to refer and drive home a point to your management.
🙂
Cheer Satish 🙂
May 13, 2009 at 5:05 am
As TECHBABU noted, the architecture is important as memory is handled differently - especially when you go over 2/4GB. 64bit makes life nice and easy.
Also, it's not just your user count - what type of application are you supporting? OLAP, OLTP or ETL? Obviously, the more memory, the more SQL will use and thus cache your database objects in said memory. How big is your database?
Also, in terms of "user" connections - will individual users be connecting directly? will they be using an "always online" connection or something similar to disconnected datasets also .NET 2 ADO? Will multiple users be grouped using connection pools? Does the user launch a single user app from a single user PC that makes the connection or is it a web app or some other 3 tier application that performs data access on behalf of the user?
--
Andrew Hatfield
May 13, 2009 at 8:41 am
It's all 32-bit :crying: and unlikely to move to 64-bit
All the connections are from websites so asp and .NET 2 with connection pooling. The database is ~30Gb so nothing massive but enough not to just lob onto a Windows XP workstation under my desk.
While I know there are no hard and fast rules with this because it will depend on things like number of transactions / minute, the number of reads vs writes, the (ab)use of stored procs vs ad-hoc queries and so on.... (pause for breath).... what would be useful is some loose guide so I can back up my statement of "Captain! The database cannae take any more! She's gonna blow!"
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply