>> How much memory does SQL use on startup? <<
I disagree about the relevance of this q. This knowledge is not only useful but vital for a senior DBA. Otherwise, in the wrong situation, the system could end up repeatedly allocating / deallocating pages and page thrashing. That's a sure recipe for dismal performance.
One example using fixed memory allocationnon a cluster and the two nodes do not have the same amount of memory. The A node has 4 gb and the B node has 2.5 gb. SQL server is a fixed allocation of 3 gb with the /3GB switch in the boot.ini. try failing over this cluster from A node to B node. This is not a test but an actual support situation that I ran into and had to fix. So YES, knowing how much memory SQL Serve uses on startup is a very relevant question in production support.
No, "wrong situation" refers primarily to an application being added to the server. And not necessarily a full-blown business app either.
Say, instead, Java applets are added to the server. Java applets require a JVM. A JVM uses a relatively large amount of RAM.
Or say a (large) virus checker is put on the server [not preferred on a SQL Server, but some companies demand it on *every* server]. Or a larger e-mail client. Or a combination of them and perhaps others, such as Winzip, etc..
If you don't understand how SQL's memory allocation works, you probably will not investigate more fully to determine if the other memory usage exceeds SQL's nominal allowance for other uses. Maybe it's OK, but maybe not. The key is that the DBA needs basic understanding to even realize that it needs checked.
Ditto on the ego boost LOL
I think I might have fell off my chair laughing
I'm ready for an interview now