August 28, 2005 at 10:12 am
Hi,
My client windows 2003 standard server with SP1 have the follow configuration
01) 4 intel 3.4GHz intel processor
02) 3.5G of RAM
03) 72G of SCSI hardisk
04) Sql server 2000 Enterprise with SP3
Our ASP.NET written application will access the above sql server
for data.
However, when the memory usage of the SQL server hit 1.2G in the
task manager. All our application and C# written migration application will halt or hang.
We are confused why this happen.
Why it halt my other ASP.NET application
or C# program when SQL hit 1.2G
Anyone with similar problem can advise me or
assist me on why our ASP.NET or C# application halt or hang.
August 28, 2005 at 5:53 pm
Few queries...
1. Are you running windows with the /3GB switch in boot.ini - this will ensure that 3GB, not the usual 2GB, of RAM is available for application data.
2. How much physical memory is available when SQL hits the 1.2GB mark?
3. Have you seen any error messages in SQL Server's logs?
4. Is there anything in the Windows event log?
5. Could you start a profiler trace just before SQL hits the 1.2GB mark (before it freezes)? Track when statements/procs start and when they finish. When SQL freezes, I imagine you will see a statement/proc start but not finish - see if you have something wrong with that statement with regards to locking? (perhaps the 1.2GB is a red herring?)
6. Start up Enterprise Manager and see if you have SQL dynamically configuring its memory (the default) or if you have restricted it to certain min/max memory values.
Hopefully information gathered from the above questions should point you in the right direction.
Cheers,
Ian
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply