Some background information. I have a Windows 2003 Server that is also
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remote
users login to our SQL application the server creates a routing statement for
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they can
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay to
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.
Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the remote
> users login to our SQL application the server creates a routing statement for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until I
> manually delete their routes from the SQL Server. Once this is done they can
> successful log back into the SQL application. Is the server suppose to keep
> track of remote machine routing connections? We migrated from Frame Relay to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
Showing posts with label wan. Show all posts
Showing posts with label wan. Show all posts
Friday, February 24, 2012
Clients being disconnected periodically over WAN
Some background information. I have a Windows 2003 Server that is also
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remote
users login to our SQL application the server creates a routing statement for
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they can
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay to
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the remote
> users login to our SQL application the server creates a routing statement for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until I
> manually delete their routes from the SQL Server. Once this is done they can
> successful log back into the SQL application. Is the server suppose to keep
> track of remote machine routing connections? We migrated from Frame Relay to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remote
users login to our SQL application the server creates a routing statement for
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they can
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay to
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the remote
> users login to our SQL application the server creates a routing statement for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until I
> manually delete their routes from the SQL Server. Once this is done they can
> successful log back into the SQL application. Is the server suppose to keep
> track of remote machine routing connections? We migrated from Frame Relay to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
Clients being disconnected periodically over WAN
Some background information. I have a Windows 2003 Server that is also
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remot
e
users login to our SQL application the server creates a routing statement fo
r
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they ca
n
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay t
o
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the rem
ote
> users login to our SQL application the server creates a routing statement
for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under bo
th
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until
I
> manually delete their routes from the SQL Server. Once this is done they
can
> successful log back into the SQL application. Is the server suppose to ke
ep
> track of remote machine routing connections? We migrated from Frame Relay
to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remot
e
users login to our SQL application the server creates a routing statement fo
r
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they ca
n
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay t
o
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the rem
ote
> users login to our SQL application the server creates a routing statement
for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under bo
th
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until
I
> manually delete their routes from the SQL Server. Once this is done they
can
> successful log back into the SQL application. Is the server suppose to ke
ep
> track of remote machine routing connections? We migrated from Frame Relay
to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
Tuesday, February 14, 2012
client freezes
NEWBIE...We run a custom application that sends
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume?
What could cause this and is there a way to adjust?
Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume?
What could cause this and is there a way to adjust?
Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve
client freezes
NEWBIE...We run a custom application that sends
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume'
What could cause this and is there a way to adjust?Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
--
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume'
What could cause this and is there a way to adjust?Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
--
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve
client freezes
NEWBIE...We run a custom application that sends
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume'
What could cause this and is there a way to adjust?Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume'
What could cause this and is there a way to adjust?Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve
Subscribe to:
Posts (Atom)