I am a newbie to clustering so I hope this makes sense. Does the Cluster
Manager have to be in the sysadmin role? If not, what are the roles that it
does require?
Thanks for any guidance.
Neil
The Cluster Service must be a local admin on each server. The Cluster
Manager application is an MMC snap-in and can run wherever. Specific
cluster functions may need specific security role membership. I generally
give the person who administers a Cluster local administrator rights on each
node.
Geoff N. Hiten
Microsoft SQL Server MVP
"Neil W." <neilw@.netlib.com> wrote in message
news:%23VNuQeCeFHA.2604@.TK2MSFTNGP15.phx.gbl...
>I am a newbie to clustering so I hope this makes sense. Does the Cluster
> Manager have to be in the sysadmin role? If not, what are the roles that
> it
> does require?
> Thanks for any guidance.
> Neil
>
>
|||Thanks for the reply. The cluster manager appears to login with Windows
login: domain\Cluster. However, I cannot locate a domain user or a local
user named "Cluster". Am I missing something?
______________________
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:usU0lhCeFHA.1136@.TK2MSFTNGP12.phx.gbl...
The Cluster Service must be a local admin on each server. The Cluster
Manager application is an MMC snap-in and can run wherever. Specific
cluster functions may need specific security role membership. I generally
give the person who administers a Cluster local administrator rights on each
node.
Geoff N. Hiten
Microsoft SQL Server MVP
"Neil W." <neilw@.netlib.com> wrote in message
news:%23VNuQeCeFHA.2604@.TK2MSFTNGP15.phx.gbl...
>I am a newbie to clustering so I hope this makes sense. Does the Cluster
> Manager have to be in the sysadmin role? If not, what are the roles that
> it
> does require?
> Thanks for any guidance.
> Neil
>
>
|||Are you sure? The cluster service account should be a domain-level account
with local admin rights on each node. There should be a domain account that
matches the service account.
Geoff N. Hiten
Microsoft SQL Server MVP
"Neil W." <neilw@.REMOVEnetlib.com> wrote in message
news:eK6Ut7CeFHA.1448@.TK2MSFTNGP14.phx.gbl...
> Thanks for the reply. The cluster manager appears to login with Windows
> login: domain\Cluster. However, I cannot locate a domain user or a local
> user named "Cluster". Am I missing something?
> ______________________
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
> news:usU0lhCeFHA.1136@.TK2MSFTNGP12.phx.gbl...
> The Cluster Service must be a local admin on each server. The Cluster
> Manager application is an MMC snap-in and can run wherever. Specific
> cluster functions may need specific security role membership. I generally
> give the person who administers a Cluster local administrator rights on
> each
> node.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> "Neil W." <neilw@.netlib.com> wrote in message
> news:%23VNuQeCeFHA.2604@.TK2MSFTNGP15.phx.gbl...
>
>
Showing posts with label newbie. Show all posts
Showing posts with label newbie. Show all posts
Sunday, March 25, 2012
Tuesday, March 20, 2012
Cluster Addresses
Hi,
I am a newbie to Clustering so please bear with me.
We have a db environment set up with Win 2003 and SQL 2000 connecting to a
single disk array.
The question I have is, what is the difference between the Cluster IP
Address and the SQL IP address.
What I really want to know is what is the purpose for the two different
addresses?
Thanks for any help.
JD
When you create a cluster, you start working with Virtual Servers. The
cluster itself becomes a Virtual server, as does each SQL instance you
install. Each virtual server consists of a minimum of a physical disk
resource, an IP address, and a network name. Of course, each virtual server
has other resources to make it actually do something useful. So, the
Cluster IP address is used to connect to Cluster control resources and the
SQL IP address is used to connect to SQL service resources. These addresses
are in addition to the IP addresses of the host nodes.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"jimmy" <jimmy@.discussions.microsoft.com> wrote in message
news:DC5A7EF8-C516-411B-823D-BA36A6E24A85@.microsoft.com...
> Hi,
> I am a newbie to Clustering so please bear with me.
> We have a db environment set up with Win 2003 and SQL 2000 connecting to a
> single disk array.
> The question I have is, what is the difference between the Cluster IP
> Address and the SQL IP address.
> What I really want to know is what is the purpose for the two different
> addresses?
> Thanks for any help.
> JD
|||Hi Geoff,
Thanks for the explanation. We have a single application that points at the
database, so should we use the SQL IP Address to point the application at the
db server?
So from your explanaition if a file share was one of the Cluster resources
and you wanted to acces it. This is when you would use the Cluster address
to access the file share. Like so:
\\ClusterIP\FileShare
Thanks Again
JD
"Geoff N. Hiten" wrote:
> When you create a cluster, you start working with Virtual Servers. The
> cluster itself becomes a Virtual server, as does each SQL instance you
> install. Each virtual server consists of a minimum of a physical disk
> resource, an IP address, and a network name. Of course, each virtual server
> has other resources to make it actually do something useful. So, the
> Cluster IP address is used to connect to Cluster control resources and the
> SQL IP address is used to connect to SQL service resources. These addresses
> are in addition to the IP addresses of the host nodes.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "jimmy" <jimmy@.discussions.microsoft.com> wrote in message
> news:DC5A7EF8-C516-411B-823D-BA36A6E24A85@.microsoft.com...
>
>
|||Yes, you use the SQL vurtial server IP address as the connection target.
Personally, I prefer to use the network name. That way, I can play with
Aliases and DNS records during disasters.
You shouldn't use the cluster resource group and quorum disk for anything
extra. You should create another virtual server and add the file service to
that resource group. \\FileShareVirtualServerName\ShareName
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"jimmy" <jimmy@.discussions.microsoft.com> wrote in message
news:641B055A-4878-4E12-AE77-DE4BFDEF3718@.microsoft.com...
> Hi Geoff,
> Thanks for the explanation. We have a single application that points at
the
> database, so should we use the SQL IP Address to point the application at
the
> db server?
> So from your explanaition if a file share was one of the Cluster resources
> and you wanted to acces it. This is when you would use the Cluster
address[vbcol=seagreen]
> to access the file share. Like so:
> \\ClusterIP\FileShare
> Thanks Again
> JD
> "Geoff N. Hiten" wrote:
server[vbcol=seagreen]
the[vbcol=seagreen]
addresses[vbcol=seagreen]
to a[vbcol=seagreen]
different[vbcol=seagreen]
|||Hi Geoff,
Thats great.
Thanks
Jamie.
"Geoff N. Hiten" wrote:
> Yes, you use the SQL vurtial server IP address as the connection target.
> Personally, I prefer to use the network name. That way, I can play with
> Aliases and DNS records during disasters.
> You shouldn't use the cluster resource group and quorum disk for anything
> extra. You should create another virtual server and add the file service to
> that resource group. \\FileShareVirtualServerName\ShareName
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "jimmy" <jimmy@.discussions.microsoft.com> wrote in message
> news:641B055A-4878-4E12-AE77-DE4BFDEF3718@.microsoft.com...
> the
> the
> address
> server
> the
> addresses
> to a
> different
>
>
|||So...
Are there any restrictions on the Cluster IP and SQL IP?
If I have an internal and external NIC, should one go on each? Can they have neighboring IPs?
The reason I ask is that I set up a new cluster with the Cluster IP on the external NIC and the SQL IP on the internal NIC. At this point everything worked fine. However the requirements changed and I changed the SQL IP from the internal NIC to the external one - with an IP contigious to the Cluster IP. Ever since, I can not get my application to connect over TCP. Sometimes the sql services will not come online either until I change the IPs back to the original settings.
I have changed the IPs both in Cluster Admin and using the SQL installer as indicated in this KB article: http://support.microsoft.com/kb/244980.
Any thoughts?
I am a newbie to Clustering so please bear with me.
We have a db environment set up with Win 2003 and SQL 2000 connecting to a
single disk array.
The question I have is, what is the difference between the Cluster IP
Address and the SQL IP address.
What I really want to know is what is the purpose for the two different
addresses?
Thanks for any help.
JD
When you create a cluster, you start working with Virtual Servers. The
cluster itself becomes a Virtual server, as does each SQL instance you
install. Each virtual server consists of a minimum of a physical disk
resource, an IP address, and a network name. Of course, each virtual server
has other resources to make it actually do something useful. So, the
Cluster IP address is used to connect to Cluster control resources and the
SQL IP address is used to connect to SQL service resources. These addresses
are in addition to the IP addresses of the host nodes.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"jimmy" <jimmy@.discussions.microsoft.com> wrote in message
news:DC5A7EF8-C516-411B-823D-BA36A6E24A85@.microsoft.com...
> Hi,
> I am a newbie to Clustering so please bear with me.
> We have a db environment set up with Win 2003 and SQL 2000 connecting to a
> single disk array.
> The question I have is, what is the difference between the Cluster IP
> Address and the SQL IP address.
> What I really want to know is what is the purpose for the two different
> addresses?
> Thanks for any help.
> JD
|||Hi Geoff,
Thanks for the explanation. We have a single application that points at the
database, so should we use the SQL IP Address to point the application at the
db server?
So from your explanaition if a file share was one of the Cluster resources
and you wanted to acces it. This is when you would use the Cluster address
to access the file share. Like so:
\\ClusterIP\FileShare
Thanks Again
JD
"Geoff N. Hiten" wrote:
> When you create a cluster, you start working with Virtual Servers. The
> cluster itself becomes a Virtual server, as does each SQL instance you
> install. Each virtual server consists of a minimum of a physical disk
> resource, an IP address, and a network name. Of course, each virtual server
> has other resources to make it actually do something useful. So, the
> Cluster IP address is used to connect to Cluster control resources and the
> SQL IP address is used to connect to SQL service resources. These addresses
> are in addition to the IP addresses of the host nodes.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "jimmy" <jimmy@.discussions.microsoft.com> wrote in message
> news:DC5A7EF8-C516-411B-823D-BA36A6E24A85@.microsoft.com...
>
>
|||Yes, you use the SQL vurtial server IP address as the connection target.
Personally, I prefer to use the network name. That way, I can play with
Aliases and DNS records during disasters.
You shouldn't use the cluster resource group and quorum disk for anything
extra. You should create another virtual server and add the file service to
that resource group. \\FileShareVirtualServerName\ShareName
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"jimmy" <jimmy@.discussions.microsoft.com> wrote in message
news:641B055A-4878-4E12-AE77-DE4BFDEF3718@.microsoft.com...
> Hi Geoff,
> Thanks for the explanation. We have a single application that points at
the
> database, so should we use the SQL IP Address to point the application at
the
> db server?
> So from your explanaition if a file share was one of the Cluster resources
> and you wanted to acces it. This is when you would use the Cluster
address[vbcol=seagreen]
> to access the file share. Like so:
> \\ClusterIP\FileShare
> Thanks Again
> JD
> "Geoff N. Hiten" wrote:
server[vbcol=seagreen]
the[vbcol=seagreen]
addresses[vbcol=seagreen]
to a[vbcol=seagreen]
different[vbcol=seagreen]
|||Hi Geoff,
Thats great.
Thanks
Jamie.
"Geoff N. Hiten" wrote:
> Yes, you use the SQL vurtial server IP address as the connection target.
> Personally, I prefer to use the network name. That way, I can play with
> Aliases and DNS records during disasters.
> You shouldn't use the cluster resource group and quorum disk for anything
> extra. You should create another virtual server and add the file service to
> that resource group. \\FileShareVirtualServerName\ShareName
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "jimmy" <jimmy@.discussions.microsoft.com> wrote in message
> news:641B055A-4878-4E12-AE77-DE4BFDEF3718@.microsoft.com...
> the
> the
> address
> server
> the
> addresses
> to a
> different
>
>
|||So...
Are there any restrictions on the Cluster IP and SQL IP?
If I have an internal and external NIC, should one go on each? Can they have neighboring IPs?
The reason I ask is that I set up a new cluster with the Cluster IP on the external NIC and the SQL IP on the internal NIC. At this point everything worked fine. However the requirements changed and I changed the SQL IP from the internal NIC to the external one - with an IP contigious to the Cluster IP. Ever since, I can not get my application to connect over TCP. Sometimes the sql services will not come online either until I change the IPs back to the original settings.
I have changed the IPs both in Cluster Admin and using the SQL installer as indicated in this KB article: http://support.microsoft.com/kb/244980.
Any thoughts?
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)