Hi John
Have you tried to look at the event logs (system and application)? Also you
can try to use the SQL profiler to help you identify te problem. Just out of
curiosity, is it really the SQL server that stops or the .NET application
that stops. You can also try to monitor the .NET application using the
performance monitor. I am not sure which version of .NET Framework you are
on, sometimes if the application open a lot of connections and they never
closed it can give some problems also.
Another thing that you can look for is how the busy the SQL server processor
is. Depending on the nature of the application, if there are a lot of
calculation going on (like looping, etc.) it can max out the processor.
There could be some other things also...
Lucas
[quoted text, click to view] "John Grant" wrote:
> SQL Server 2005 enterpise edition with 8g or memory in the compaq dl380
> server with AWE enabled. I think the server is using about 7g.
> Connections are 0 - unlimited
> I have a .net application that tries to create 300 connections async and
> start a small process on each connection from one workstation.
> The SQL Server stops at about 280 connections.
> Am I out of memory, and how can I tell?
>
What exactly do you mean by "the server stops"? What on earth can you
possibly be doing with 300 constant concurrent processes from a single work
station? You should see errors in the SQL Error log as well as the event
logs that can give you more of a clue as to what is going on. But one thing
you may be running into is memory for the connections if the processes are
sucking up a lot of other memory such as procedure cache. Do you have the
/3GB enabled in the boot.ini?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
[quoted text, click to view] "John Grant" <JohnGrant@discussions.microsoft.com> wrote in message
news:71B7ABD5-C5E7-4DF6-81E0-7612BF295549@microsoft.com...
> SQL Server 2005 enterpise edition with 8g or memory in the compaq dl380
> server with AWE enabled. I think the server is using about 7g.
> Connections are 0 - unlimited
> I have a .net application that tries to create 300 connections async and
> start a small process on each connection from one workstation.
> The SQL Server stops at about 280 connections.
> Am I out of memory, and how can I tell?
>
> thanks
Serevr stops accepting connections.
Did not try them from another machine...good point.
I am using .net 2.0 from Vista 64 bit. Simple winform application.
No clues in the sql server log, or event logs.
I am trying to test some concurrency behavior on SQL Server.
I do not have the /3gb set. I will set that and try again.
thanks
[quoted text, click to view] "Andrew J. Kelly" wrote:
> What exactly do you mean by "the server stops"? What on earth can you
> possibly be doing with 300 constant concurrent processes from a single work
> station? You should see errors in the SQL Error log as well as the event
> logs that can give you more of a clue as to what is going on. But one thing
> you may be running into is memory for the connections if the processes are
> sucking up a lot of other memory such as procedure cache. Do you have the
> /3GB enabled in the boot.ini?
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "John Grant" <JohnGrant@discussions.microsoft.com> wrote in message
> news:71B7ABD5-C5E7-4DF6-81E0-7612BF295549@microsoft.com...
> > SQL Server 2005 enterpise edition with 8g or memory in the compaq dl380
> > server with AWE enabled. I think the server is using about 7g.
> > Connections are 0 - unlimited
> > I have a .net application that tries to create 300 connections async and
> > start a small process on each connection from one workstation.
> > The SQL Server stops at about 280 connections.
> > Am I out of memory, and how can I tell?
> >
> > thanks
>
Have a look at DBCC MEMORYSTATUS to see where the memory is being used in
SQL Server but I bet it is a client issue. From what I understand Vista has
some limit on the number of connections it can make but I don't know what it
is. Try spreading the load over client several machines.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
[quoted text, click to view] "John Grant" <JohnGrant@discussions.microsoft.com> wrote in message
news:E51FF884-3B35-4665-9C39-21E4C68F6A26@microsoft.com...
> Serevr stops accepting connections.
> Did not try them from another machine...good point.
> I am using .net 2.0 from Vista 64 bit. Simple winform application.
> No clues in the sql server log, or event logs.
> I am trying to test some concurrency behavior on SQL Server.
> I do not have the /3gb set. I will set that and try again.
>
> thanks
>
>
> "Andrew J. Kelly" wrote:
>
>> What exactly do you mean by "the server stops"? What on earth can you
>> possibly be doing with 300 constant concurrent processes from a single
>> work
>> station? You should see errors in the SQL Error log as well as the event
>> logs that can give you more of a clue as to what is going on. But one
>> thing
>> you may be running into is memory for the connections if the processes
>> are
>> sucking up a lot of other memory such as procedure cache. Do you have the
>> /3GB enabled in the boot.ini?
>>
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>>
>> "John Grant" <JohnGrant@discussions.microsoft.com> wrote in message
>> news:71B7ABD5-C5E7-4DF6-81E0-7612BF295549@microsoft.com...
>> > SQL Server 2005 enterpise edition with 8g or memory in the compaq dl380
>> > server with AWE enabled. I think the server is using about 7g.
>> > Connections are 0 - unlimited
>> > I have a .net application that tries to create 300 connections async
>> > and
>> > start a small process on each connection from one workstation.
>> > The SQL Server stops at about 280 connections.
>> > Am I out of memory, and how can I tell?
>> >
>> > thanks
>>
>>
Don't see what you're looking for? Try a search.
