Hi,
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production databases, and the other(S2) is just a standby. The database files are on a DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK array and use sp_attch sp's
to bring the database up.
Thanks,
Elvis
Have yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis
Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts
Monday, March 19, 2012
Crashing a server
Hi,
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production datab
ases, and the other(S2) is just a standby. The database files are on a DISK
array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK
array and use sp_attch sp's
to bring the database up.
Thanks,
ElvisHave yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production datab
ases, and the other(S2) is just a standby. The database files are on a DISK
array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK
array and use sp_attch sp's
to bring the database up.
Thanks,
ElvisHave yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis
Wednesday, March 7, 2012
CPU Time
I have a SQL server 2000 standard version installed on a window 2000 server.
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
YingHi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
YingHi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying
CPU Time
I have a SQL server 2000 standard version installed on a window 2000 server.
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
Ying
Hi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
Ying
Hi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying
CPU Time
I have a SQL server 2000 standard version installed on a window 2000 server.
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
YingHi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
YingHi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying
Subscribe to:
Posts (Atom)