Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sanjaytiwari
Starting Member
1 Post |
 Posted - 2004-07-01 : 07:47:50
|
| I am using SQL 7.00 With no SQL Service Pack. on P-III Xeon Processor with 2 GB RAM. on NT 4.00 BDC Server with SP 6.00. This works 24 hors & 365 days. i am facing memory problem. SQL is not releasing memory back. i had configre the Virtual memory also. When memory is full i am getting Error timeout for My Client which they are using VB+SQL Based ERP with ADO connection.Sanjay |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2004-07-01 : 09:19:29
|
| Hi Sanjay,A few things: It is not an ideal world to run SQL on your BDC - it should preferably be on a dedicated server. Why? because SQL uses a lot of resources to run optimally, and one of those Cheif resources is ... memory. What happens (by design) is that SQL grabs memory as client requests give it the need. It does not release that memory. When it reaches it's maximum, then it maintains that memory.So, a clue to a POTENTIAL solution was given there. You can set SQL to not take all memory - BUT remember, you are then affecting SQL's performance.Go to Enterprise Manager --> right click on your server, and choose "properties", go to the "memory" tab, and look at the settings there. You should do this in a test environment, and determine what the best setting is. As you can see, you can alter the maximum SQL memory amount, so you can throttle down SQL's use of memory.Of course, this can all be done by T-SQL as well - look at the sp_configure command in BOL.BTW ... SERIOUSLY push getting this box service packed (SP 4 I believe is latest SQL7 SP) ... you want all those fixes and security improvement. Make it your next prioprity, imho.CiaO*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
 |
|
|
|
|
|
|
|
SQL 7.00 Memory Problem