 |
|
You are not logged in! F.A.Q Log in Register |
 |
|
 |
 (nobody)...and 395 guests Last 5 registered Oplandisks nothingstar N_loop yipe foxtrotromeo Browse members... |
 |
Members 8025Messages 2614093 Today 6 Topics 127542 |
|
|||||||||
| |||||||||
|
|
Does this seem like too high a memory usage to you? |
||||||||
| Attached picture | |||||||||
|
|||||||||
|
|
|||||||||
| |||||||||
|
|
haha |
||||||||
|
|
|||||||||
| |||||||||
|
|
Yeah.. |
||||||||
| Attached picture | |||||||||
|
|||||||||
|
|
|||||||||
| |||||||||
|
|
So mine's only a tad higher than yours. What are you running on it? I'm just wondering if that's anything to do with it? I honestly don't know a lot about it but seeing it nearing a gig seemed strange. It's on Windows Server 2003. |
||||||||
|
|
|||||||||
| |||||||||
|
|
Mine's 15mb and yours is like 900+mb, I'd say that was more than a tad. I'm running couple of tiny databases on XP. |
||||||||
|
|
|||||||||
| |||||||||
|
|
I know it's more than a tad mate :). One of the databases attached it's running is about 700meg mate. I think that could be why it's nearly a gig as there's a couple of other databases attached that are around 100meg. |
||||||||
|
|
|||||||||
| |||||||||
|
|
I'd say someone is sifting your tuples hard man. Can you check the processes more closely ie PS -AX in unix? |
||||||||
|
|
|||||||||
| |||||||||
|
|
Yeah I realised that you weren't being serious straight after I posted. I am an idiot. I guess the size of the database could explain it, but I don't really know enough about it to help any more... maybe have a look . |
||||||||
|
|
|||||||||
| |||||||||
|
|
Cheers for the link Horsefactory. That did indeed give me an answer. Quernstone: I can see who's accessing the system the database is linked to. That's about it. |
||||||||
|
|
|||||||||
| |||||||||
|
|
I only have access to a tiny amount of the data I used to, but looking at my old employers stuff, even our fairly large SQL server DBs (pupil records for big unis like plymouth) were seldom bigger than about a gig themselves. Total memory usage (for all process) on the machines only exceeded 512mb at a few of the largest site and even on those SQL server was seldom more than a 3/400mb! Either that's a really meaty database with millions of users or something is going wrong. Things you can try: In the CLI (there is a proper name for it), run the "SP_WHO2" query (set it to display the results in a table) to look at the number of connections and how long they've been on. Think about terminating connections (other than those done by program itself) that have been in access for more than 24 hours. Stop/Start the SQL server service (Icon in your task bar). Reboot (Sounds simple I know, but in the past it has worked for me when a SQL server instance was eating too much memory and I couldn't locate/fix the problem) Finally, insist they send you on the official SQL Server 2000 course (Course: 2072A) if they want you to deal with this in future/stop it happening again. There are places in London near you that do it. |
||||||||
|
|
|||||||||
| |||||||||
|
|
Cheers mate, I'll give that all a whirl. I wont have to insist on the course though. They want me to train up in as muuch as possible. |
||||||||
|
|
|||||||||
|
Messageboard index
|
|||||||||
