how much is enough memory for sql
-
hey guys,
im no sql expert so expect some either noobian or foolish questions/statements.
We have a server which we use for c# development it runs as a terminal server, and also runs sql server on it.
Its a dual athlon 2200 wtih 2gb of ram.
Its current max memory is set to 512 and min is 0.
We are encountering problems when trying to use query analyser and enterprise manager on the server when ts in to do development. Enterprise manager locks up looking at local server and takes along time for other servers. But when connections are made to the server from another server or from a local computer the analyser and enterprise manager run fine.
What could this probnlem be?
ps running win2k service pack 4 not sure if there are any service packs isntalled for sql.
Any advice?
-
Wow, that's a busy server – Terminal Services, SQL Server, C# development, SQL Server development and SQL Server admin!
As EM and QA work well from other PCs/servers, why don't you just shrug your shoulders and carry on using other machines for these apps?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin -
well are doing that now.
but its pretty inefficient as well as a pain in the ass to have change b/w either terminal server windows or to your desktop if installed locally.
plus it doesnt explain why its occurring
the c# dev has not been uped in intenisty there a maybe even less ppl deving on the server at the moment, there are about 40 databases i think i counted, and intotal they are abotu 6.5 gb of space.
does this shed any more light on the subject?
-
I have never seen this but have heard of this happening before. I can't remember where I heard about this but I do remember as part of the solution they used perf-mon in Windows. Can't remember what they saw of how they resolved it. if I remember I will respond back.
-NS
-
that would be greatly appreciated
-
There could be any number of reasons for your problems, usually if SQL Server is very busy then it can be difficult to connect at the desktop, which is good as you don't want desktop apps interferring with the server engine.
Memory is always good but unless you're running with adv server you're stuck with 2Gb.
I suggest you monitor the server and see what is busy, cpu usuage and disk usage would be a start. Check the free memory and if you've got some then increase the memory available to sql server.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/ -
ive monitored cpu at diff times its not that as far as i can tell
disk and memory are where it may be getting stuck
waht would be good things to monitor and how for both say in perf mon
-
SQL Cache hit ratio will be an idication of sql memory. Disk time + i/o rates, although you'll have to do your sums with regard to the spindles .. I assume you are using seperate drives on your server ?
a simple look in task manager will show how much memory is being used, ideally you don't want to be paging
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/ -
k il take a look tomorrow see wahts happening.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply