Conditional -- ?

What does "conditional" mean as a command? sp_who2 reports this for
some sessions, along with "insert" etc.

Thanks,
Jim Geissman(jim_geissman@.countrywide.com) writes:
> What does "conditional" mean as a command? sp_who2 reports this for
> some sessions, along with "insert" etc.

An IF or WHILE statement. Typically with a query in the condition, like
IF EXISTS(SELECT ...). If this query is long-running, or the longest
running in a stuck loop, CONDITIONAL is likely to turn up.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks, Erland!

Erland Sommarskog wrote:
> (jim_geissman@.countrywide.com) writes:
> > What does "conditional" mean as a command? sp_who2 reports this for
> > some sessions, along with "insert" etc.
> An IF or WHILE statement. Typically with a query in the condition, like
> IF EXISTS(SELECT ...). If this query is long-running, or the longest
> running in a stuck loop, CONDITIONAL is likely to turn up.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Concurrent Access

Hi,
I have been asked to give a realistic number of concurrent access to do the
stress test to the sql server for our application. I used sp_who2, and
there are about 187 rows in the result pane. However, most of them has"Sleep"
status. 187 concurrent access is a lot. Am I using the right method? Have you
done stress test on your sql server? What is the number of concurrent access
that you put on the server during the test?
Thanks in advance!
K
We have a couple hundred workstations and just over 1000 database
connections.
Keith
"K" <K@.discussions.microsoft.com> wrote in message
news:562243D0-BF68-45BB-A7FA-F4760A79DEB7@.microsoft.com...
> Hi,
> I have been asked to give a realistic number of concurrent access to do
> the
> stress test to the sql server for our application. I used sp_who2, and
> there are about 187 rows in the result pane. However, most of them
> has"Sleep"
> status. 187 concurrent access is a lot. Am I using the right method? Have
> you
> done stress test on your sql server? What is the number of concurrent
> access
> that you put on the server during the test?
> Thanks in advance!
> K
>

Concurrent Access

Hi,
I have been asked to give a realistic number of concurrent access to do the
stress test to the sql server for our application. I used sp_who2, and
there are about 187 rows in the result pane. However, most of them has"Sleep"
status. 187 concurrent access is a lot. Am I using the right method? Have you
done stress test on your sql server? What is the number of concurrent access
that you put on the server during the test?
Thanks in advance!
KWe have a couple hundred workstations and just over 1000 database
connections.
--
Keith
"K" <K@.discussions.microsoft.com> wrote in message
news:562243D0-BF68-45BB-A7FA-F4760A79DEB7@.microsoft.com...
> Hi,
> I have been asked to give a realistic number of concurrent access to do
> the
> stress test to the sql server for our application. I used sp_who2, and
> there are about 187 rows in the result pane. However, most of them
> has"Sleep"
> status. 187 concurrent access is a lot. Am I using the right method? Have
> you
> done stress test on your sql server? What is the number of concurrent
> access
> that you put on the server during the test?
> Thanks in advance!
> K
>

Concurrent Access

Hi,
I have been asked to give a realistic number of concurrent access to do the
stress test to the sql server for our application. I used sp_who2, and
there are about 187 rows in the result pane. However, most of them has"Sleep
"
status. 187 concurrent access is a lot. Am I using the right method? Have yo
u
done stress test on your sql server? What is the number of concurrent access
that you put on the server during the test?
Thanks in advance!
KWe have a couple hundred workstations and just over 1000 database
connections.
Keith
"K" <K@.discussions.microsoft.com> wrote in message
news:562243D0-BF68-45BB-A7FA-F4760A79DEB7@.microsoft.com...
> Hi,
> I have been asked to give a realistic number of concurrent access to do
> the
> stress test to the sql server for our application. I used sp_who2, and
> there are about 187 rows in the result pane. However, most of them
> has"Sleep"
> status. 187 concurrent access is a lot. Am I using the right method? Have
> you
> done stress test on your sql server? What is the number of concurrent
> access
> that you put on the server during the test?
> Thanks in advance!
> K
>