I have a Windows2003 cluster, two nodes, 12GB each. When the /PAE switch is on the nodes reboot themselves without warning or noticable error. I think that I've ruled out bad hardware because it occurs on more than one server. With /PAE off and only 4GB available to the OS the cluster seems rock solid (1 month, no issues).
After the month-long honeymoon I turned on /PAE on node 2 and within 48 hours node 1 rebooted itself. I know that you won't believe that, but there it is. I turned off /PAE on node 2 and we've been stable on both nodes since.
Anybody seen this before?I believe it, because it happened to us. The difference is ours took one week before it crashed and rebooted itself. We did a few things and it seems to be fine now. Put '/3GB' before '/PAE'. Run Rebuild Registries using SQL installation CD. After you enabled AWE in SQL, run sp_configure and see if SQL actually is using all the memory you have allocated for by looking at the number on 'max server memory (MB)'. If not, configure it with the right number.
Hope this help! Good luck.
Showing posts with label reboot. Show all posts
Showing posts with label reboot. Show all posts
Tuesday, March 20, 2012
Rebooting Server for Replication to work
At times, we have come across issues around replication such as high CPU for
transactional replication in SQL 2000 that requires a reboot to fix it.
Do we know why a reboot fixes ? Right now, we just reboot the server, but
dont know how it resolves and what it resolves under the hood ?
We are on SQL SP4. It doesnt happen all the time, just maybe once in 6
months or so.
Thanks
I suspect you are bumping into this.
http://support.microsoft.com/default.aspx/kb/812263
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Hassan" <Hassan@.hotmail.com> wrote in message
news:ukenRgwFHHA.1232@.TK2MSFTNGP05.phx.gbl...
> At times, we have come across issues around replication such as high CPU
> for transactional replication in SQL 2000 that requires a reboot to fix
> it.
> Do we know why a reboot fixes ? Right now, we just reboot the server, but
> dont know how it resolves and what it resolves under the hood ?
> We are on SQL SP4. It doesnt happen all the time, just maybe once in 6
> months or so.
> Thanks
>
|||Well maybe I wasnt too clear.. It does work, but it just causes a high CPU
like 90% and things start to slow down on the server. Stopping the SQL Agent
helps but the minute you start it again, it starts to peg again due to the
replication agents.
Any other thoughts ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23iEjI2wFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>I suspect you are bumping into this.
> http://support.microsoft.com/default.aspx/kb/812263
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:ukenRgwFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>
|||Hassan,
as soon as this occurs, you could do some investigation and post back. Use
sp_who2 and DBCC INPUTBUFFER to see what the agent is doing and if there is
blocking involved. Also, use sp_browsereplcommands and MSDistribution_status
to see how what commands are in the queue.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||One more thing Hilary, do you think this bug is fixed in SP4 ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23iEjI2wFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>I suspect you are bumping into this.
> http://support.microsoft.com/default.aspx/kb/812263
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:ukenRgwFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>
|||Probably a good idea to move distributor to dedicated box... just 1
occurence in 12 mo. period is justification for this...
Chris MCDBA MCSE
MSSQLConsulting.com
"Hassan" wrote:
> At times, we have come across issues around replication such as high CPU for
> transactional replication in SQL 2000 that requires a reboot to fix it.
> Do we know why a reboot fixes ? Right now, we just reboot the server, but
> dont know how it resolves and what it resolves under the hood ?
> We are on SQL SP4. It doesnt happen all the time, just maybe once in 6
> months or so.
> Thanks
>
>
|||It is unclear if it is or not. It seems that I am bumping into it all the
time on my laptop. I kill the log reader agents and this seems to solve it.
Can you tell if it is the agent which consumes all cpu or SQL Server?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Hassan" <Hassan@.hotmail.com> wrote in message
news:eV6jC9zFHHA.4588@.TK2MSFTNGP05.phx.gbl...
> One more thing Hilary, do you think this bug is fixed in SP4 ?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23iEjI2wFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>
|||I'll check the next time it occurs..
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23VqLoW7FHHA.1276@.TK2MSFTNGP04.phx.gbl...
> It is unclear if it is or not. It seems that I am bumping into it all the
> time on my laptop. I kill the log reader agents and this seems to solve
> it.
> Can you tell if it is the agent which consumes all cpu or SQL Server?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:eV6jC9zFHHA.4588@.TK2MSFTNGP05.phx.gbl...
>
transactional replication in SQL 2000 that requires a reboot to fix it.
Do we know why a reboot fixes ? Right now, we just reboot the server, but
dont know how it resolves and what it resolves under the hood ?
We are on SQL SP4. It doesnt happen all the time, just maybe once in 6
months or so.
Thanks
I suspect you are bumping into this.
http://support.microsoft.com/default.aspx/kb/812263
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Hassan" <Hassan@.hotmail.com> wrote in message
news:ukenRgwFHHA.1232@.TK2MSFTNGP05.phx.gbl...
> At times, we have come across issues around replication such as high CPU
> for transactional replication in SQL 2000 that requires a reboot to fix
> it.
> Do we know why a reboot fixes ? Right now, we just reboot the server, but
> dont know how it resolves and what it resolves under the hood ?
> We are on SQL SP4. It doesnt happen all the time, just maybe once in 6
> months or so.
> Thanks
>
|||Well maybe I wasnt too clear.. It does work, but it just causes a high CPU
like 90% and things start to slow down on the server. Stopping the SQL Agent
helps but the minute you start it again, it starts to peg again due to the
replication agents.
Any other thoughts ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23iEjI2wFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>I suspect you are bumping into this.
> http://support.microsoft.com/default.aspx/kb/812263
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:ukenRgwFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>
|||Hassan,
as soon as this occurs, you could do some investigation and post back. Use
sp_who2 and DBCC INPUTBUFFER to see what the agent is doing and if there is
blocking involved. Also, use sp_browsereplcommands and MSDistribution_status
to see how what commands are in the queue.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||One more thing Hilary, do you think this bug is fixed in SP4 ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23iEjI2wFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>I suspect you are bumping into this.
> http://support.microsoft.com/default.aspx/kb/812263
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:ukenRgwFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>
|||Probably a good idea to move distributor to dedicated box... just 1
occurence in 12 mo. period is justification for this...
Chris MCDBA MCSE
MSSQLConsulting.com
"Hassan" wrote:
> At times, we have come across issues around replication such as high CPU for
> transactional replication in SQL 2000 that requires a reboot to fix it.
> Do we know why a reboot fixes ? Right now, we just reboot the server, but
> dont know how it resolves and what it resolves under the hood ?
> We are on SQL SP4. It doesnt happen all the time, just maybe once in 6
> months or so.
> Thanks
>
>
|||It is unclear if it is or not. It seems that I am bumping into it all the
time on my laptop. I kill the log reader agents and this seems to solve it.
Can you tell if it is the agent which consumes all cpu or SQL Server?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Hassan" <Hassan@.hotmail.com> wrote in message
news:eV6jC9zFHHA.4588@.TK2MSFTNGP05.phx.gbl...
> One more thing Hilary, do you think this bug is fixed in SP4 ?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23iEjI2wFHHA.1232@.TK2MSFTNGP05.phx.gbl...
>
|||I'll check the next time it occurs..
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23VqLoW7FHHA.1276@.TK2MSFTNGP04.phx.gbl...
> It is unclear if it is or not. It seems that I am bumping into it all the
> time on my laptop. I kill the log reader agents and this seems to solve
> it.
> Can you tell if it is the agent which consumes all cpu or SQL Server?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:eV6jC9zFHHA.4588@.TK2MSFTNGP05.phx.gbl...
>
Monday, March 12, 2012
Rebooting Mirrored Servers
New to SQL. Can you reboot the principal server after running updates without causing a failover?
If not what would the correct procedure be.
Do you have a witness?
If so, you could stop SQL Server on the mirror while you reboot the principal, that will prevent failover.
When I do this I let failover happen - it's a good test of it and it's pretty quick, once the principal is back up you can fail back over to it.
|||If there is no witness , Database Mirroring will get into disconnected state and resumes when able to communicate with Mirror.Reboot? How often?
We currently have SQL server EE running on Windows Server 2003 EE in a 2 node
active/passive cluster. We want to restart periodically but not too often.
What is the best way to do this? What I've been doing is move the resources
to the inactive side of the cluster then rebooting the passive node. Then
next time move them back using cluster administrator then rebooting the other
box. Anyone see any potential issues with this approach? Thanks.
Tom
That works, but why do you want to reboot? Are you talking about software/OS
updates.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"rk rider" <rkrider@.discussions.microsoft.com> wrote in message
news:EA70D7F1-C143-4B63-A32D-A59FFC422E1C@.microsoft.com...
> We currently have SQL server EE running on Windows Server 2003 EE in a 2
> node
> active/passive cluster. We want to restart periodically but not too often.
> What is the best way to do this? What I've been doing is move the
> resources
> to the inactive side of the cluster then rebooting the passive node. Then
> next time move them back using cluster administrator then rebooting the
> other
> box. Anyone see any potential issues with this approach? Thanks.
> Tom
|||Because the VP of our dept thinks servers need to be rebooted on a regular
schedule. Personally I see no real reason althought it's nice to test the
fail over periodically in a controlled manner. Personally however, I see no
compelling reason given the stability of Windows server these days. I just
looking for a best practices approach.
"Rodney R. Fournier [MVP]" wrote:
> That works, but why do you want to reboot? Are you talking about software/OS
> updates.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> "rk rider" <rkrider@.discussions.microsoft.com> wrote in message
> news:EA70D7F1-C143-4B63-A32D-A59FFC422E1C@.microsoft.com...
>
>
|||That is what I am getting at, if you patch monthly then you will reboot
monthly
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"rk rider" <rkrider@.discussions.microsoft.com> wrote in message
news:2C3511EB-E75E-4B8F-8A73-53A608994E08@.microsoft.com...[vbcol=seagreen]
> Because the VP of our dept thinks servers need to be rebooted on a regular
> schedule. Personally I see no real reason althought it's nice to test the
> fail over periodically in a controlled manner. Personally however, I see
> no
> compelling reason given the stability of Windows server these days. I just
> looking for a best practices approach.
> "Rodney R. Fournier [MVP]" wrote:
|||The only issue that I see with it is that you blow away your cache, so when
the SQL Server starts back up, it has to incrementally repopulate that as
queries come in. That leads to performance degradation and heavy
utilization on your disk drives. I see no reason to just arbitrarily reboot
a server, at all. If I have to apply a service pack or hotfix that requires
rebooting, then I obviously reboot. But, that is the only time that I
reboot a machine. If it ain't broke, don't fix it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"rk rider" <rkrider@.discussions.microsoft.com> wrote in message
news:EA70D7F1-C143-4B63-A32D-A59FFC422E1C@.microsoft.com...
> We currently have SQL server EE running on Windows Server 2003 EE in a 2
> node
> active/passive cluster. We want to restart periodically but not too often.
> What is the best way to do this? What I've been doing is move the
> resources
> to the inactive side of the cluster then rebooting the passive node. Then
> next time move them back using cluster administrator then rebooting the
> other
> box. Anyone see any potential issues with this approach? Thanks.
> Tom
|||I agree with the other replies. Windows 2003 is orders of magnitude more
stable than NT 4.0. Your VP needs to update his technical skills or at
least admit that Windows 95 is not the Gold Standard for operating systems
any more.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"rk rider" <rkrider@.discussions.microsoft.com> wrote in message
news:EA70D7F1-C143-4B63-A32D-A59FFC422E1C@.microsoft.com...
> We currently have SQL server EE running on Windows Server 2003 EE in a 2
> node
> active/passive cluster. We want to restart periodically but not too often.
> What is the best way to do this? What I've been doing is move the
> resources
> to the inactive side of the cluster then rebooting the passive node. Then
> next time move them back using cluster administrator then rebooting the
> other
> box. Anyone see any potential issues with this approach? Thanks.
> Tom
|||rk rider wrote:
> We currently have SQL server EE running on Windows Server 2003 EE in
> a 2 node active/passive cluster. We want to restart periodically but
> not too often. What is the best way to do this?
When there are hotfix that require to be applied I install them on the
passive node and reboot it immediately.
Then I download and install it on active node and I schedule a shutdown
(using shutdown.exe or psshutdown from sysinternals) for the following
night.
So, usually I shutdown the system monthly but only if there are high
priority hotfix available...
> Tom
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
active/passive cluster. We want to restart periodically but not too often.
What is the best way to do this? What I've been doing is move the resources
to the inactive side of the cluster then rebooting the passive node. Then
next time move them back using cluster administrator then rebooting the other
box. Anyone see any potential issues with this approach? Thanks.
Tom
That works, but why do you want to reboot? Are you talking about software/OS
updates.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"rk rider" <rkrider@.discussions.microsoft.com> wrote in message
news:EA70D7F1-C143-4B63-A32D-A59FFC422E1C@.microsoft.com...
> We currently have SQL server EE running on Windows Server 2003 EE in a 2
> node
> active/passive cluster. We want to restart periodically but not too often.
> What is the best way to do this? What I've been doing is move the
> resources
> to the inactive side of the cluster then rebooting the passive node. Then
> next time move them back using cluster administrator then rebooting the
> other
> box. Anyone see any potential issues with this approach? Thanks.
> Tom
|||Because the VP of our dept thinks servers need to be rebooted on a regular
schedule. Personally I see no real reason althought it's nice to test the
fail over periodically in a controlled manner. Personally however, I see no
compelling reason given the stability of Windows server these days. I just
looking for a best practices approach.
"Rodney R. Fournier [MVP]" wrote:
> That works, but why do you want to reboot? Are you talking about software/OS
> updates.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> "rk rider" <rkrider@.discussions.microsoft.com> wrote in message
> news:EA70D7F1-C143-4B63-A32D-A59FFC422E1C@.microsoft.com...
>
>
|||That is what I am getting at, if you patch monthly then you will reboot
monthly
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"rk rider" <rkrider@.discussions.microsoft.com> wrote in message
news:2C3511EB-E75E-4B8F-8A73-53A608994E08@.microsoft.com...[vbcol=seagreen]
> Because the VP of our dept thinks servers need to be rebooted on a regular
> schedule. Personally I see no real reason althought it's nice to test the
> fail over periodically in a controlled manner. Personally however, I see
> no
> compelling reason given the stability of Windows server these days. I just
> looking for a best practices approach.
> "Rodney R. Fournier [MVP]" wrote:
|||The only issue that I see with it is that you blow away your cache, so when
the SQL Server starts back up, it has to incrementally repopulate that as
queries come in. That leads to performance degradation and heavy
utilization on your disk drives. I see no reason to just arbitrarily reboot
a server, at all. If I have to apply a service pack or hotfix that requires
rebooting, then I obviously reboot. But, that is the only time that I
reboot a machine. If it ain't broke, don't fix it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"rk rider" <rkrider@.discussions.microsoft.com> wrote in message
news:EA70D7F1-C143-4B63-A32D-A59FFC422E1C@.microsoft.com...
> We currently have SQL server EE running on Windows Server 2003 EE in a 2
> node
> active/passive cluster. We want to restart periodically but not too often.
> What is the best way to do this? What I've been doing is move the
> resources
> to the inactive side of the cluster then rebooting the passive node. Then
> next time move them back using cluster administrator then rebooting the
> other
> box. Anyone see any potential issues with this approach? Thanks.
> Tom
|||I agree with the other replies. Windows 2003 is orders of magnitude more
stable than NT 4.0. Your VP needs to update his technical skills or at
least admit that Windows 95 is not the Gold Standard for operating systems
any more.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"rk rider" <rkrider@.discussions.microsoft.com> wrote in message
news:EA70D7F1-C143-4B63-A32D-A59FFC422E1C@.microsoft.com...
> We currently have SQL server EE running on Windows Server 2003 EE in a 2
> node
> active/passive cluster. We want to restart periodically but not too often.
> What is the best way to do this? What I've been doing is move the
> resources
> to the inactive side of the cluster then rebooting the passive node. Then
> next time move them back using cluster administrator then rebooting the
> other
> box. Anyone see any potential issues with this approach? Thanks.
> Tom
|||rk rider wrote:
> We currently have SQL server EE running on Windows Server 2003 EE in
> a 2 node active/passive cluster. We want to restart periodically but
> not too often. What is the best way to do this?
When there are hotfix that require to be applied I install them on the
passive node and reboot it immediately.
Then I download and install it on active node and I schedule a shutdown
(using shutdown.exe or psshutdown from sysinternals) for the following
night.
So, usually I shutdown the system monthly but only if there are high
priority hotfix available...
> Tom
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
Reboot, how often?
Hello,
We have noticed that we begin developing system stability issues with our
database client systems (everything is running on Windows 2K... SQL Server
is on a Win 2k Server system and the clients are running Win 2k Pro) after a
little over a month. A reboot of the server system seems to straighten out
this issue.
Has anyone encountered an article or information about a recommended reboot
time period for Windows 2000 Server systems running SQL Server?
Thank you for any help.Ideally, you should never have to reboot the server, except when the power
goes out or the system software is upgraded in a way that requires a reboot.
Are you sure that your application(s) or user(s) aren't causing memory leaks
or spiraled CPU usage? Any hints in the event log that might correlate to
these "stability issues"? What are these issues, specifically?
We have a windows 2000 server with SQL 7.0 in production, that is used quite
heavily throughout the day by many clients in both the US and Europe, and
the last time it was rebooted was when we changed data centers. I also run
several SQL Server 2000 systems that have never been rebooted for "stability
issues"...
"Michael" <somone@.somewhere.com> wrote in message
news:ud0Jwn9RDHA.2460@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We have noticed that we begin developing system stability issues with
our
> database client systems (everything is running on Windows 2K... SQL Server
> is on a Win 2k Server system and the clients are running Win 2k Pro) after
a
> little over a month. A reboot of the server system seems to straighten
out
> this issue.
> Has anyone encountered an article or information about a recommended
reboot
> time period for Windows 2000 Server systems running SQL Server?
> Thank you for any help.
>|||Having said that, Analysis Services can sometimes be a different issue
altogether. :-)
> We have a windows 2000 server with SQL 7.0 in production, that is used
quite
> heavily throughout the day by many clients in both the US and Europe, and
> the last time it was rebooted was when we changed data centers. I also
run
> several SQL Server 2000 systems that have never been rebooted for
"stability
> issues"...
We have noticed that we begin developing system stability issues with our
database client systems (everything is running on Windows 2K... SQL Server
is on a Win 2k Server system and the clients are running Win 2k Pro) after a
little over a month. A reboot of the server system seems to straighten out
this issue.
Has anyone encountered an article or information about a recommended reboot
time period for Windows 2000 Server systems running SQL Server?
Thank you for any help.Ideally, you should never have to reboot the server, except when the power
goes out or the system software is upgraded in a way that requires a reboot.
Are you sure that your application(s) or user(s) aren't causing memory leaks
or spiraled CPU usage? Any hints in the event log that might correlate to
these "stability issues"? What are these issues, specifically?
We have a windows 2000 server with SQL 7.0 in production, that is used quite
heavily throughout the day by many clients in both the US and Europe, and
the last time it was rebooted was when we changed data centers. I also run
several SQL Server 2000 systems that have never been rebooted for "stability
issues"...
"Michael" <somone@.somewhere.com> wrote in message
news:ud0Jwn9RDHA.2460@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We have noticed that we begin developing system stability issues with
our
> database client systems (everything is running on Windows 2K... SQL Server
> is on a Win 2k Server system and the clients are running Win 2k Pro) after
a
> little over a month. A reboot of the server system seems to straighten
out
> this issue.
> Has anyone encountered an article or information about a recommended
reboot
> time period for Windows 2000 Server systems running SQL Server?
> Thank you for any help.
>|||Having said that, Analysis Services can sometimes be a different issue
altogether. :-)
> We have a windows 2000 server with SQL 7.0 in production, that is used
quite
> heavily throughout the day by many clients in both the US and Europe, and
> the last time it was rebooted was when we changed data centers. I also
run
> several SQL Server 2000 systems that have never been rebooted for
"stability
> issues"...
Reboot SQL Server 2000 server periodically ?
We currently reboot our Citrix and Application Server server/machines
periodically
Is it recommended to reboot the server/machine which hosts the SQL Server 2000
periodically ? If so how often ?
Our servers/machines are Windows 2003
Thanks
Well Why you reboot the server periodically.It is not recommended unless you
face any problems
"SQL Server newbie" wrote:
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server 2000
> periodically ? If so how often ?
> Our servers/machines are Windows 2003
> Thanks
|||"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:8076BE75-0E42-44DC-B461-2C59941F7420@.microsoft.com...
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
> 2000
> periodically ? If so how often ?
Hmm, I had one I tended to reboot every time we changed datacenters.
So perhaps once every 2-3 years.
Seriously, you should NOT need to reboot SQL Server.
> Our servers/machines are Windows 2003
> Thanks
periodically
Is it recommended to reboot the server/machine which hosts the SQL Server 2000
periodically ? If so how often ?
Our servers/machines are Windows 2003
Thanks
Well Why you reboot the server periodically.It is not recommended unless you
face any problems
"SQL Server newbie" wrote:
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server 2000
> periodically ? If so how often ?
> Our servers/machines are Windows 2003
> Thanks
|||"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:8076BE75-0E42-44DC-B461-2C59941F7420@.microsoft.com...
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
> 2000
> periodically ? If so how often ?
Hmm, I had one I tended to reboot every time we changed datacenters.
So perhaps once every 2-3 years.
Seriously, you should NOT need to reboot SQL Server.
> Our servers/machines are Windows 2003
> Thanks
Reboot SQL Server 2000 server periodically ?
We currently reboot our Citrix and Application Server server/machines
periodically
Is it recommended to reboot the server/machine which hosts the SQL Server 2000
periodically ? If so how often ?
Our servers/machines are Windows 2003
ThanksWell Why you reboot the server periodically.It is not recommended unless you
face any problems
"SQL Server newbie" wrote:
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server 2000
> periodically ? If so how often ?
> Our servers/machines are Windows 2003
> Thanks|||"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:8076BE75-0E42-44DC-B461-2C59941F7420@.microsoft.com...
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
> 2000
> periodically ? If so how often ?
Hmm, I had one I tended to reboot every time we changed datacenters.
So perhaps once every 2-3 years.
Seriously, you should NOT need to reboot SQL Server.
> Our servers/machines are Windows 2003
> Thanks
periodically
Is it recommended to reboot the server/machine which hosts the SQL Server 2000
periodically ? If so how often ?
Our servers/machines are Windows 2003
ThanksWell Why you reboot the server periodically.It is not recommended unless you
face any problems
"SQL Server newbie" wrote:
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server 2000
> periodically ? If so how often ?
> Our servers/machines are Windows 2003
> Thanks|||"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:8076BE75-0E42-44DC-B461-2C59941F7420@.microsoft.com...
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
> 2000
> periodically ? If so how often ?
Hmm, I had one I tended to reboot every time we changed datacenters.
So perhaps once every 2-3 years.
Seriously, you should NOT need to reboot SQL Server.
> Our servers/machines are Windows 2003
> Thanks
Reboot SQL Server 2000 server periodically ?
We currently reboot our Citrix and Application Server server/machines
periodically
Is it recommended to reboot the server/machine which hosts the SQL Server 20
00
periodically ? If so how often ?
Our servers/machines are Windows 2003
ThanksWell Why you reboot the server periodically.It is not recommended unless you
face any problems
"SQL Server newbie" wrote:
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
2000
> periodically ? If so how often ?
> Our servers/machines are Windows 2003
> Thanks|||"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:8076BE75-0E42-44DC-B461-2C59941F7420@.microsoft.com...
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
> 2000
> periodically ? If so how often ?
Hmm, I had one I tended to reboot every time we changed datacenters.
So perhaps once every 2-3 years.
Seriously, you should NOT need to reboot SQL Server.
> Our servers/machines are Windows 2003
> Thanks
periodically
Is it recommended to reboot the server/machine which hosts the SQL Server 20
00
periodically ? If so how often ?
Our servers/machines are Windows 2003
ThanksWell Why you reboot the server periodically.It is not recommended unless you
face any problems
"SQL Server newbie" wrote:
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
2000
> periodically ? If so how often ?
> Our servers/machines are Windows 2003
> Thanks|||"SQL Server newbie" <SQLServernewbie@.discussions.microsoft.com> wrote in
message news:8076BE75-0E42-44DC-B461-2C59941F7420@.microsoft.com...
> We currently reboot our Citrix and Application Server server/machines
> periodically
> Is it recommended to reboot the server/machine which hosts the SQL Server
> 2000
> periodically ? If so how often ?
Hmm, I had one I tended to reboot every time we changed datacenters.
So perhaps once every 2-3 years.
Seriously, you should NOT need to reboot SQL Server.
> Our servers/machines are Windows 2003
> Thanks
Reboot SAN of SQL Cluster
We are planning a recycle of our SAN to which our active/passive 2-node SQL
cluster is attached. Is there anything special to be aware of?
We will do the following steps:
Pause the passive node
using Cluster Admin, stop SQL service
Power down active node server
power down passive node server
after SAN recycle complete
Power up active node server
power up passive node server
restart (resume) passive node
Any insight is greatly appreciated!!
Go ahead and take the entire SQL resource group offline. Then take the
cluster group offline. Down the host nodes, reboot the SAN, then restart
the nodes one at a time.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"RobinMC" <RobinMC@.discussions.microsoft.com> wrote in message
news:78418060-D070-4AEE-BBD7-83D3D827069E@.microsoft.com...
> We are planning a recycle of our SAN to which our active/passive 2-node
> SQL
> cluster is attached. Is there anything special to be aware of?
> We will do the following steps:
> Pause the passive node
> using Cluster Admin, stop SQL service
> Power down active node server
> power down passive node server
> after SAN recycle complete
> Power up active node server
> power up passive node server
> restart (resume) passive node
> Any insight is greatly appreciated!!
|||If you are on a geo cluster (2 disk arrays replicated via a dedicated
technology), first restart the node which was stopped last (for cluster
service).
Guillaume.
==================
"RobinMC" wrote:
> We are planning a recycle of our SAN to which our active/passive 2-node SQL
> cluster is attached. Is there anything special to be aware of?
> We will do the following steps:
> Pause the passive node
> using Cluster Admin, stop SQL service
> Power down active node server
> power down passive node server
> after SAN recycle complete
> Power up active node server
> power up passive node server
> restart (resume) passive node
> Any insight is greatly appreciated!!
cluster is attached. Is there anything special to be aware of?
We will do the following steps:
Pause the passive node
using Cluster Admin, stop SQL service
Power down active node server
power down passive node server
after SAN recycle complete
Power up active node server
power up passive node server
restart (resume) passive node
Any insight is greatly appreciated!!
Go ahead and take the entire SQL resource group offline. Then take the
cluster group offline. Down the host nodes, reboot the SAN, then restart
the nodes one at a time.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"RobinMC" <RobinMC@.discussions.microsoft.com> wrote in message
news:78418060-D070-4AEE-BBD7-83D3D827069E@.microsoft.com...
> We are planning a recycle of our SAN to which our active/passive 2-node
> SQL
> cluster is attached. Is there anything special to be aware of?
> We will do the following steps:
> Pause the passive node
> using Cluster Admin, stop SQL service
> Power down active node server
> power down passive node server
> after SAN recycle complete
> Power up active node server
> power up passive node server
> restart (resume) passive node
> Any insight is greatly appreciated!!
|||If you are on a geo cluster (2 disk arrays replicated via a dedicated
technology), first restart the node which was stopped last (for cluster
service).
Guillaume.
==================
"RobinMC" wrote:
> We are planning a recycle of our SAN to which our active/passive 2-node SQL
> cluster is attached. Is there anything special to be aware of?
> We will do the following steps:
> Pause the passive node
> using Cluster Admin, stop SQL service
> Power down active node server
> power down passive node server
> after SAN recycle complete
> Power up active node server
> power up passive node server
> restart (resume) passive node
> Any insight is greatly appreciated!!
Reboot required to revitalize server?
I'm having a problem with my database server whereby performance decreases
after 12-18 hours in production and is only restored after a reboot. [almost
like hitting a wall]
Of course, the memory usage increases throughout the day and eventually
settles with a few hundred MB of free memory. SQL Server seems to top off at
1.75GB memory usage. [3GB total] Processor usage never seems to be a
problem, and there are no problematic table locks at the time a reboot is
necessary.
Can anyone point me in the right direction to begin tracing the problem. I
realize there are a million possibilities as to the cause of the problem,
but an "I'd start here..." suggestion would be helpful.
Thanks in advance.Hi
You don't say what your system is doing or how much load there is on it. If
there are a significant number of inserts/updates your indexes could be
fragmented and/or statistics out of date. Check out DBCC SHOWCONTIG and
sp_updatestats in books online.
John
"Chris" wrote:
> I'm having a problem with my database server whereby performance decreases
> after 12-18 hours in production and is only restored after a reboot. [almo
st
> like hitting a wall]
> Of course, the memory usage increases throughout the day and eventually
> settles with a few hundred MB of free memory. SQL Server seems to top off
at
> 1.75GB memory usage. [3GB total] Processor usage never seems to be a
> problem, and there are no problematic table locks at the time a reboot is
> necessary.
> Can anyone point me in the right direction to begin tracing the problem.
I
> realize there are a million possibilities as to the cause of the problem,
> but an "I'd start here..." suggestion would be helpful.
> Thanks in advance.
>
>|||Thanks, I'll begin my research.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:401CC40F-0E95-4B2B-B18D-4089A531942F@.microsoft.com...
> Hi
> You don't say what your system is doing or how much load there is on it.
> If
> there are a significant number of inserts/updates your indexes could be
> fragmented and/or statistics out of date. Check out DBCC SHOWCONTIG and
> sp_updatestats in books online.
> John
> "Chris" wrote:
>|||Hi
I have been thinking a bit more about this! This sounds more like a lack of
resources. Does stopping/starting SQL Server have the same effect as a
re-boot? This would narrow it down to the process itself!
You may also want to rule out open transactions (DBCC OPENTRAN)
John
"Chris" wrote:
> Thanks, I'll begin my research.
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:401CC40F-0E95-4B2B-B18D-4089A531942F@.microsoft.com...
>
>|||I'll try that when/if it happens again. I found that there was some
fragmentation, since my nightly index rebuilding sproc was disabled. Thanks
for the help.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:E40523F0-980B-4D0F-BBCE-74D564E2DCE4@.microsoft.com...
> Hi
> I have been thinking a bit more about this! This sounds more like a lack
> of
> resources. Does stopping/starting SQL Server have the same effect as a
> re-boot? This would narrow it down to the process itself!
> You may also want to rule out open transactions (DBCC OPENTRAN)
> John
> "Chris" wrote:
>
after 12-18 hours in production and is only restored after a reboot. [almost
like hitting a wall]
Of course, the memory usage increases throughout the day and eventually
settles with a few hundred MB of free memory. SQL Server seems to top off at
1.75GB memory usage. [3GB total] Processor usage never seems to be a
problem, and there are no problematic table locks at the time a reboot is
necessary.
Can anyone point me in the right direction to begin tracing the problem. I
realize there are a million possibilities as to the cause of the problem,
but an "I'd start here..." suggestion would be helpful.
Thanks in advance.Hi
You don't say what your system is doing or how much load there is on it. If
there are a significant number of inserts/updates your indexes could be
fragmented and/or statistics out of date. Check out DBCC SHOWCONTIG and
sp_updatestats in books online.
John
"Chris" wrote:
> I'm having a problem with my database server whereby performance decreases
> after 12-18 hours in production and is only restored after a reboot. [almo
st
> like hitting a wall]
> Of course, the memory usage increases throughout the day and eventually
> settles with a few hundred MB of free memory. SQL Server seems to top off
at
> 1.75GB memory usage. [3GB total] Processor usage never seems to be a
> problem, and there are no problematic table locks at the time a reboot is
> necessary.
> Can anyone point me in the right direction to begin tracing the problem.
I
> realize there are a million possibilities as to the cause of the problem,
> but an "I'd start here..." suggestion would be helpful.
> Thanks in advance.
>
>|||Thanks, I'll begin my research.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:401CC40F-0E95-4B2B-B18D-4089A531942F@.microsoft.com...
> Hi
> You don't say what your system is doing or how much load there is on it.
> If
> there are a significant number of inserts/updates your indexes could be
> fragmented and/or statistics out of date. Check out DBCC SHOWCONTIG and
> sp_updatestats in books online.
> John
> "Chris" wrote:
>|||Hi
I have been thinking a bit more about this! This sounds more like a lack of
resources. Does stopping/starting SQL Server have the same effect as a
re-boot? This would narrow it down to the process itself!
You may also want to rule out open transactions (DBCC OPENTRAN)
John
"Chris" wrote:
> Thanks, I'll begin my research.
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:401CC40F-0E95-4B2B-B18D-4089A531942F@.microsoft.com...
>
>|||I'll try that when/if it happens again. I found that there was some
fragmentation, since my nightly index rebuilding sproc was disabled. Thanks
for the help.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:E40523F0-980B-4D0F-BBCE-74D564E2DCE4@.microsoft.com...
> Hi
> I have been thinking a bit more about this! This sounds more like a lack
> of
> resources. Does stopping/starting SQL Server have the same effect as a
> re-boot? This would narrow it down to the process itself!
> You may also want to rule out open transactions (DBCC OPENTRAN)
> John
> "Chris" wrote:
>
reboot reboot reboot
I have installed ss2005 and now I want to change some things (add the
AdventureWorks dbs). On one machine it worked fine but on the other System
Configuration Check keeps getting a reboot required message that says...
"A previous installation required a reboot of the machine for changes to
take effect. To proceed, restart your computer and then run SQL Server
Setup again."
So, I reboot but it keeps getting the same message. What can I do?
Tinn ManI presume that there is an installation issue.
and at every reboot, Sql server starts and detect a file problem, like a
missing or worng DLL, then the installer starts a repair process.
when the reinstallation is done, the system ask for a reboot.
but this reinstallation doesn't works really fine and at every reboot the
same event occurs.
you'll see some installer event log in the windows log if the installer
starts himself.
Try to reinstall SQL server interactively to catch some installation issues.
stop any SQL services , reboot, see if the installer starts, then do a clean
install or repair process.
"Tinn Man" <tm@.nospammeexcite.com> wrote in message
news:uw8ZVLQiGHA.4512@.TK2MSFTNGP02.phx.gbl...
>I have installed ss2005 and now I want to change some things (add the
>AdventureWorks dbs). On one machine it worked fine but on the other System
>Configuration Check keeps getting a reboot required message that says...
> "A previous installation required a reboot of the machine for changes to
> take effect. To proceed, restart your computer and then run SQL Server
> Setup again."
> So, I reboot but it keeps getting the same message. What can I do?
> Tinn Man
>
AdventureWorks dbs). On one machine it worked fine but on the other System
Configuration Check keeps getting a reboot required message that says...
"A previous installation required a reboot of the machine for changes to
take effect. To proceed, restart your computer and then run SQL Server
Setup again."
So, I reboot but it keeps getting the same message. What can I do?
Tinn ManI presume that there is an installation issue.
and at every reboot, Sql server starts and detect a file problem, like a
missing or worng DLL, then the installer starts a repair process.
when the reinstallation is done, the system ask for a reboot.
but this reinstallation doesn't works really fine and at every reboot the
same event occurs.
you'll see some installer event log in the windows log if the installer
starts himself.
Try to reinstall SQL server interactively to catch some installation issues.
stop any SQL services , reboot, see if the installer starts, then do a clean
install or repair process.
"Tinn Man" <tm@.nospammeexcite.com> wrote in message
news:uw8ZVLQiGHA.4512@.TK2MSFTNGP02.phx.gbl...
>I have installed ss2005 and now I want to change some things (add the
>AdventureWorks dbs). On one machine it worked fine but on the other System
>Configuration Check keeps getting a reboot required message that says...
> "A previous installation required a reboot of the machine for changes to
> take effect. To proceed, restart your computer and then run SQL Server
> Setup again."
> So, I reboot but it keeps getting the same message. What can I do?
> Tinn Man
>
reboot reboot reboot
I have installed ss2005 and now I want to change some things (add the
AdventureWorks dbs). On one machine it worked fine but on the other System
Configuration Check keeps getting a reboot required message that says...
"A previous installation required a reboot of the machine for changes to
take effect. To proceed, restart your computer and then run SQL Server
Setup again."
So, I reboot but it keeps getting the same message. What can I do?
Tinn ManI presume that there is an installation issue.
and at every reboot, Sql server starts and detect a file problem, like a
missing or worng DLL, then the installer starts a repair process.
when the reinstallation is done, the system ask for a reboot.
but this reinstallation doesn't works really fine and at every reboot the
same event occurs.
you'll see some installer event log in the windows log if the installer
starts himself.
Try to reinstall SQL server interactively to catch some installation issues.
stop any SQL services , reboot, see if the installer starts, then do a clean
install or repair process.
"Tinn Man" <tm@.nospammeexcite.com> wrote in message
news:uw8ZVLQiGHA.4512@.TK2MSFTNGP02.phx.gbl...
>I have installed ss2005 and now I want to change some things (add the
>AdventureWorks dbs). On one machine it worked fine but on the other System
>Configuration Check keeps getting a reboot required message that says...
> "A previous installation required a reboot of the machine for changes to
> take effect. To proceed, restart your computer and then run SQL Server
> Setup again."
> So, I reboot but it keeps getting the same message. What can I do?
> Tinn Man
>
AdventureWorks dbs). On one machine it worked fine but on the other System
Configuration Check keeps getting a reboot required message that says...
"A previous installation required a reboot of the machine for changes to
take effect. To proceed, restart your computer and then run SQL Server
Setup again."
So, I reboot but it keeps getting the same message. What can I do?
Tinn ManI presume that there is an installation issue.
and at every reboot, Sql server starts and detect a file problem, like a
missing or worng DLL, then the installer starts a repair process.
when the reinstallation is done, the system ask for a reboot.
but this reinstallation doesn't works really fine and at every reboot the
same event occurs.
you'll see some installer event log in the windows log if the installer
starts himself.
Try to reinstall SQL server interactively to catch some installation issues.
stop any SQL services , reboot, see if the installer starts, then do a clean
install or repair process.
"Tinn Man" <tm@.nospammeexcite.com> wrote in message
news:uw8ZVLQiGHA.4512@.TK2MSFTNGP02.phx.gbl...
>I have installed ss2005 and now I want to change some things (add the
>AdventureWorks dbs). On one machine it worked fine but on the other System
>Configuration Check keeps getting a reboot required message that says...
> "A previous installation required a reboot of the machine for changes to
> take effect. To proceed, restart your computer and then run SQL Server
> Setup again."
> So, I reboot but it keeps getting the same message. What can I do?
> Tinn Man
>
reboot problem (not always)
Hi,
I have a server where, when I reboot it, sometimes the sql server 2005
service stop in starting mode and the performance log and alert service in
stopping mode.
this lock the computer from any remote access. (including Terminal server)
I have to do a hard reboot.
and if this doesn't works, I have to reboot again until all the services are
up and running correctly.
any idea of what can cause this lock?
why SQL Server don't starts correctly? and why the performance log service
don't stops?
thanks.
Jerome.JeJe,
Check the Application Event Log for any errors...may lead you to the cause.
HTH
Jerry
"Jeje" <willgart@.hotmail.com> wrote in message
news:OPGi4lafGHA.1276@.TK2MSFTNGP03.phx.gbl...
> Hi,
> I have a server where, when I reboot it, sometimes the sql server 2005
> service stop in starting mode and the performance log and alert service in
> stopping mode.
> this lock the computer from any remote access. (including Terminal server)
> I have to do a hard reboot.
> and if this doesn't works, I have to reboot again until all the services
> are up and running correctly.
> any idea of what can cause this lock?
> why SQL Server don't starts correctly? and why the performance log service
> don't stops?
> thanks.
> Jerome.
>
I have a server where, when I reboot it, sometimes the sql server 2005
service stop in starting mode and the performance log and alert service in
stopping mode.
this lock the computer from any remote access. (including Terminal server)
I have to do a hard reboot.
and if this doesn't works, I have to reboot again until all the services are
up and running correctly.
any idea of what can cause this lock?
why SQL Server don't starts correctly? and why the performance log service
don't stops?
thanks.
Jerome.JeJe,
Check the Application Event Log for any errors...may lead you to the cause.
HTH
Jerry
"Jeje" <willgart@.hotmail.com> wrote in message
news:OPGi4lafGHA.1276@.TK2MSFTNGP03.phx.gbl...
> Hi,
> I have a server where, when I reboot it, sometimes the sql server 2005
> service stop in starting mode and the performance log and alert service in
> stopping mode.
> this lock the computer from any remote access. (including Terminal server)
> I have to do a hard reboot.
> and if this doesn't works, I have to reboot again until all the services
> are up and running correctly.
> any idea of what can cause this lock?
> why SQL Server don't starts correctly? and why the performance log service
> don't stops?
> thanks.
> Jerome.
>
reboot problem (not always)
Hi,
I have a server where, when I reboot it, sometimes the sql server 2005
service stop in starting mode and the performance log and alert service in
stopping mode.
this lock the computer from any remote access. (including Terminal server)
I have to do a hard reboot.
and if this doesn't works, I have to reboot again until all the services are
up and running correctly.
any idea of what can cause this lock?
why SQL Server don't starts correctly? and why the performance log service
don't stops?
thanks.
Jerome.JeJe,
Check the Application Event Log for any errors...may lead you to the cause.
HTH
Jerry
"Jeje" <willgart@.hotmail.com> wrote in message
news:OPGi4lafGHA.1276@.TK2MSFTNGP03.phx.gbl...
> Hi,
> I have a server where, when I reboot it, sometimes the sql server 2005
> service stop in starting mode and the performance log and alert service in
> stopping mode.
> this lock the computer from any remote access. (including Terminal server)
> I have to do a hard reboot.
> and if this doesn't works, I have to reboot again until all the services
> are up and running correctly.
> any idea of what can cause this lock?
> why SQL Server don't starts correctly? and why the performance log service
> don't stops?
> thanks.
> Jerome.
>
I have a server where, when I reboot it, sometimes the sql server 2005
service stop in starting mode and the performance log and alert service in
stopping mode.
this lock the computer from any remote access. (including Terminal server)
I have to do a hard reboot.
and if this doesn't works, I have to reboot again until all the services are
up and running correctly.
any idea of what can cause this lock?
why SQL Server don't starts correctly? and why the performance log service
don't stops?
thanks.
Jerome.JeJe,
Check the Application Event Log for any errors...may lead you to the cause.
HTH
Jerry
"Jeje" <willgart@.hotmail.com> wrote in message
news:OPGi4lafGHA.1276@.TK2MSFTNGP03.phx.gbl...
> Hi,
> I have a server where, when I reboot it, sometimes the sql server 2005
> service stop in starting mode and the performance log and alert service in
> stopping mode.
> this lock the computer from any remote access. (including Terminal server)
> I have to do a hard reboot.
> and if this doesn't works, I have to reboot again until all the services
> are up and running correctly.
> any idea of what can cause this lock?
> why SQL Server don't starts correctly? and why the performance log service
> don't stops?
> thanks.
> Jerome.
>
reboot notification
Hi all,
I wanted SQL server to sent me an email when it reboots. I created an Alert
but doesn't seem to be working. Any suggestions.
Thanks,I would create a stored procedure that would send an email, then have that
stored procedure execute every time sql starts. I don't remember the name
or property so that it executes on startup of SQL server.
Oscar...
"Guju" <guju@.tpg.com.au> wrote in message
news:41943151$1_1@.news.iprimus.com.au...
> Hi all,
> I wanted SQL server to sent me an email when it reboots. I created an
Alert
> but doesn't seem to be working. Any suggestions.
> Thanks,
reboot from sql server 2000 unexpected
my sql 2000 server is rebooted without my permissinions
this happend random times my compleet server down and
nothing into the eventviewer The previous system shutdown
at 8:22:09 PM on 4/3/2004 was unexpected.
nothing else i have sp3 for sql2000 and my server is
win2000 sp4 with all updates
please help
sorry for english still pratics
Rene,
Without anything logged, it will be difficult if not
impossible to track this down. If you want to monitor the
SQL Server end of things, you can run a blackbox trace that
will show you everything that was going in SQL Server. You
can find information on this trace in books online under the
sp_trace_create help topic. Check the options for
TRACE_PRODUCE_BLACKBOX .
-Sue
On Thu, 8 Apr 2004 02:31:40 -0700, "rene"
<anonymous@.discussions.microsoft.com> wrote:
>my sql 2000 server is rebooted without my permissinions
>this happend random times my compleet server down and
>nothing into the eventviewer The previous system shutdown
>at 8:22:09 PM on 4/3/2004 was unexpected.
>nothing else i have sp3 for sql2000 and my server is
>win2000 sp4 with all updates
>please help
>sorry for english still pratics
|||unexpected shutdown means that there was no shutdown command, like when you
hit the reset switch.
So - check your hardware - motherboard, overheating and so on.
Bojidar Alexandrov
"rene" <anonymous@.discussions.microsoft.com> wrote in message
news:1a21c01c41d4c$4be38b20$a101280a@.phx.gbl...
> my sql 2000 server is rebooted without my permissinions
> this happend random times my compleet server down and
> nothing into the eventviewer The previous system shutdown
> at 8:22:09 PM on 4/3/2004 was unexpected.
> nothing else i have sp3 for sql2000 and my server is
> win2000 sp4 with all updates
> please help
> sorry for english still pratics
this happend random times my compleet server down and
nothing into the eventviewer The previous system shutdown
at 8:22:09 PM on 4/3/2004 was unexpected.
nothing else i have sp3 for sql2000 and my server is
win2000 sp4 with all updates
please help
sorry for english still pratics
Rene,
Without anything logged, it will be difficult if not
impossible to track this down. If you want to monitor the
SQL Server end of things, you can run a blackbox trace that
will show you everything that was going in SQL Server. You
can find information on this trace in books online under the
sp_trace_create help topic. Check the options for
TRACE_PRODUCE_BLACKBOX .
-Sue
On Thu, 8 Apr 2004 02:31:40 -0700, "rene"
<anonymous@.discussions.microsoft.com> wrote:
>my sql 2000 server is rebooted without my permissinions
>this happend random times my compleet server down and
>nothing into the eventviewer The previous system shutdown
>at 8:22:09 PM on 4/3/2004 was unexpected.
>nothing else i have sp3 for sql2000 and my server is
>win2000 sp4 with all updates
>please help
>sorry for english still pratics
|||unexpected shutdown means that there was no shutdown command, like when you
hit the reset switch.
So - check your hardware - motherboard, overheating and so on.
Bojidar Alexandrov
"rene" <anonymous@.discussions.microsoft.com> wrote in message
news:1a21c01c41d4c$4be38b20$a101280a@.phx.gbl...
> my sql 2000 server is rebooted without my permissinions
> this happend random times my compleet server down and
> nothing into the eventviewer The previous system shutdown
> at 8:22:09 PM on 4/3/2004 was unexpected.
> nothing else i have sp3 for sql2000 and my server is
> win2000 sp4 with all updates
> please help
> sorry for english still pratics
Friday, March 9, 2012
Reboot
I would like to reboot my server offsite (remote), can I do that? If I can,
what do I have to do?
Thanks
Tony
HI
Connect to server use remote desktop connection or write a little vb script
and use WMI reboot() method.
Andras Jakus MCDBA
"tony-icwgroup" wrote:
> I would like to reboot my server offsite (remote), can I do that? If I can,
> what do I have to do?
> Thanks
> Tony
|||... or use shutdown.exe from Windows Resource kit or any of the free tools available at the
Internet.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andras Jakus" <AndrasJakus@.discussions.microsoft.com> wrote in message
news:60689D29-6F36-4F6A-9997-748E10770E34@.microsoft.com...[vbcol=seagreen]
> HI
> Connect to server use remote desktop connection or write a little vb script
> and use WMI reboot() method.
> Andras Jakus MCDBA
> "tony-icwgroup" wrote:
what do I have to do?
Thanks
Tony
HI
Connect to server use remote desktop connection or write a little vb script
and use WMI reboot() method.
Andras Jakus MCDBA
"tony-icwgroup" wrote:
> I would like to reboot my server offsite (remote), can I do that? If I can,
> what do I have to do?
> Thanks
> Tony
|||... or use shutdown.exe from Windows Resource kit or any of the free tools available at the
Internet.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andras Jakus" <AndrasJakus@.discussions.microsoft.com> wrote in message
news:60689D29-6F36-4F6A-9997-748E10770E34@.microsoft.com...[vbcol=seagreen]
> HI
> Connect to server use remote desktop connection or write a little vb script
> and use WMI reboot() method.
> Andras Jakus MCDBA
> "tony-icwgroup" wrote:
Reboot
I would like to reboot my server offsite (remote), can I do that? If I can,
what do I have to do?
Thanks
TonyHI
Connect to server use remote desktop connection or write a little vb script
and use WMI reboot() method.
Andras Jakus MCDBA
"tony-icwgroup" wrote:
> I would like to reboot my server offsite (remote), can I do that? If I can,
> what do I have to do?
> Thanks
> Tony|||... or use shutdown.exe from Windows Resource kit or any of the free tools available at the
Internet.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andras Jakus" <AndrasJakus@.discussions.microsoft.com> wrote in message
news:60689D29-6F36-4F6A-9997-748E10770E34@.microsoft.com...
> HI
> Connect to server use remote desktop connection or write a little vb script
> and use WMI reboot() method.
> Andras Jakus MCDBA
> "tony-icwgroup" wrote:
> > I would like to reboot my server offsite (remote), can I do that? If I can,
> > what do I have to do?
> >
> > Thanks
> > Tony
what do I have to do?
Thanks
TonyHI
Connect to server use remote desktop connection or write a little vb script
and use WMI reboot() method.
Andras Jakus MCDBA
"tony-icwgroup" wrote:
> I would like to reboot my server offsite (remote), can I do that? If I can,
> what do I have to do?
> Thanks
> Tony|||... or use shutdown.exe from Windows Resource kit or any of the free tools available at the
Internet.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andras Jakus" <AndrasJakus@.discussions.microsoft.com> wrote in message
news:60689D29-6F36-4F6A-9997-748E10770E34@.microsoft.com...
> HI
> Connect to server use remote desktop connection or write a little vb script
> and use WMI reboot() method.
> Andras Jakus MCDBA
> "tony-icwgroup" wrote:
> > I would like to reboot my server offsite (remote), can I do that? If I can,
> > what do I have to do?
> >
> > Thanks
> > Tony
Reboot
I would like to reboot my server offsite (remote), can I do that? If I can,
what do I have to do?
Thanks
TonyHI
Connect to server use remote desktop connection or write a little vb script
and use WMI reboot() method.
Andras Jakus MCDBA
"tony-icwgroup" wrote:
> I would like to reboot my server offsite (remote), can I do that? If I can
,
> what do I have to do?
> Thanks
> Tony|||... or use shutdown.exe from Windows Resource kit or any of the free tools
available at the
Internet.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andras Jakus" <AndrasJakus@.discussions.microsoft.com> wrote in message
news:60689D29-6F36-4F6A-9997-748E10770E34@.microsoft.com...[vbcol=seagreen]
> HI
> Connect to server use remote desktop connection or write a little vb scrip
t
> and use WMI reboot() method.
> Andras Jakus MCDBA
> "tony-icwgroup" wrote:
>
what do I have to do?
Thanks
TonyHI
Connect to server use remote desktop connection or write a little vb script
and use WMI reboot() method.
Andras Jakus MCDBA
"tony-icwgroup" wrote:
> I would like to reboot my server offsite (remote), can I do that? If I can
,
> what do I have to do?
> Thanks
> Tony|||... or use shutdown.exe from Windows Resource kit or any of the free tools
available at the
Internet.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andras Jakus" <AndrasJakus@.discussions.microsoft.com> wrote in message
news:60689D29-6F36-4F6A-9997-748E10770E34@.microsoft.com...[vbcol=seagreen]
> HI
> Connect to server use remote desktop connection or write a little vb scrip
t
> and use WMI reboot() method.
> Andras Jakus MCDBA
> "tony-icwgroup" wrote:
>
Reboot
I'm trying to install MSDE through a custom installation program. However, we all know that Microsofts Merge Modules are complete crap so the next best way of doing such a thing is to just call the "setup.exe" for MSDE itself.
My problem is that the MSDE setup prompts the user for a reboot. How can I supress this reboot so that my user will only have to reboot the machine after my program is installed?
I was told that the command /qb would work, but for whatever reason, it did not. Any ideas?
Any help would be greatly appreciated for this is the last "problem" with the current project.I've found this question in a few diffrent places but I could never find a clear cut answer. Hopefully the next person with this problem will find my post...
The answer is just send the command line "REBOOT=ReallySupress" when calling the setup.exe. I've been told this is case sensative.
My problem is that the MSDE setup prompts the user for a reboot. How can I supress this reboot so that my user will only have to reboot the machine after my program is installed?
I was told that the command /qb would work, but for whatever reason, it did not. Any ideas?
Any help would be greatly appreciated for this is the last "problem" with the current project.I've found this question in a few diffrent places but I could never find a clear cut answer. Hopefully the next person with this problem will find my post...
The answer is just send the command line "REBOOT=ReallySupress" when calling the setup.exe. I've been told this is case sensative.
Subscribe to:
Posts (Atom)