November 18, 2011 at 10:08 am
My first production db. Went live last Thursday. Running reasonably well. Access front-end, SS2k5 backend running on MS Server 2008.
I have a very small SQL Server setup. HP Server with 10/100 network, Core I3, 4 gb memory, two 150 gb disk. 100 or so tables. 5-10 active users.
I am seeing (as I watch the system monitor) 95% memory allocation, but few hard faults. I see network spikes up to 10 mbps. And, I see frequent disk read/write spikes. Nothing serious.
All of my data and log files are on drive D. I wonder if it makes any sense to move the log files to C (which currently has nothing on it but the OS). Or, I could put backups on C. (I back up and compact the db every night, saving 15 days' worth....)
Any thoughts?
Any monitoring I should be doing daily?
Jim
November 18, 2011 at 10:18 am
I would tend to keep SQL away from the OS. If space is an issue and the C drive has a lot of spare capacity put your backups on it.
If the database is low use you can easily get away with data and log sharing a drive.
Is this 32bit or 64? If 64 bit make sure you have set max memory in SQL to 3GB at the most. It is normal for SQL to use all the memory it can get so high memory usage would be typical behaviour.
---------------------------------------------------------------------
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply