We have a Hitachi Thunder SAN to host SharePoint databases. We are running
SQL server 2000 SP3 in a 2 node active/passive cluster. I have read articles
stating to run diskpar to align the offset correctly with the disks to
dramatically increase performance. I'm undecided on whether I should run
diskpar.
Does anybody have experience of seeing improvement using Hitachi SANs?
There seems to be more experience with Exchange than SQL out there.
--
Will RobinsonHi
Yes, run it. The alignment of OS blocks with the underlying SAN block does
eliminate the need for the SAN to do unnecessary IO.
Also, make sure that your formatting matches your SAN's block size. On or
Hitachi and EMC's, we format the drives with 64kb blocks, as this matches
SQL Server I/O sizes and our SAN's stripe size.
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/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:C95D1918-D841-42F9-B156-1C00A7BF8304@.microsoft.com...
> We have a Hitachi Thunder SAN to host SharePoint databases. We are
> running
> SQL server 2000 SP3 in a 2 node active/passive cluster. I have read
> articles
> stating to run diskpar to align the offset correctly with the disks to
> dramatically increase performance. I'm undecided on whether I should run
> diskpar.
> Does anybody have experience of seeing improvement using Hitachi SANs?
> There seems to be more experience with Exchange than SQL out there.
> --
> Will Robinson
2012年3月29日星期四
diskpar and Hitachi SAN for performance
We have a Hitachi Thunder SAN to host SharePoint databases. We are running
SQL server 2000 SP3 in a 2 node active/passive cluster. I have read articles
stating to run diskpar to align the offset correctly with the disks to
dramatically increase performance. I'm undecided on whether I should run
diskpar.
Does anybody have experience of seeing improvement using Hitachi SANs?
There seems to be more experience with Exchange than SQL out there.
Will Robinson
Hi
Yes, run it. The alignment of OS blocks with the underlying SAN block does
eliminate the need for the SAN to do unnecessary IO.
Also, make sure that your formatting matches your SAN's block size. On or
Hitachi and EMC's, we format the drives with 64kb blocks, as this matches
SQL Server I/O sizes and our SAN's stripe size.
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/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:C95D1918-D841-42F9-B156-1C00A7BF8304@.microsoft.com...
> We have a Hitachi Thunder SAN to host SharePoint databases. We are
> running
> SQL server 2000 SP3 in a 2 node active/passive cluster. I have read
> articles
> stating to run diskpar to align the offset correctly with the disks to
> dramatically increase performance. I'm undecided on whether I should run
> diskpar.
> Does anybody have experience of seeing improvement using Hitachi SANs?
> There seems to be more experience with Exchange than SQL out there.
> --
> Will Robinson
sql
SQL server 2000 SP3 in a 2 node active/passive cluster. I have read articles
stating to run diskpar to align the offset correctly with the disks to
dramatically increase performance. I'm undecided on whether I should run
diskpar.
Does anybody have experience of seeing improvement using Hitachi SANs?
There seems to be more experience with Exchange than SQL out there.
Will Robinson
Hi
Yes, run it. The alignment of OS blocks with the underlying SAN block does
eliminate the need for the SAN to do unnecessary IO.
Also, make sure that your formatting matches your SAN's block size. On or
Hitachi and EMC's, we format the drives with 64kb blocks, as this matches
SQL Server I/O sizes and our SAN's stripe size.
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/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:C95D1918-D841-42F9-B156-1C00A7BF8304@.microsoft.com...
> We have a Hitachi Thunder SAN to host SharePoint databases. We are
> running
> SQL server 2000 SP3 in a 2 node active/passive cluster. I have read
> articles
> stating to run diskpar to align the offset correctly with the disks to
> dramatically increase performance. I'm undecided on whether I should run
> diskpar.
> Does anybody have experience of seeing improvement using Hitachi SANs?
> There seems to be more experience with Exchange than SQL out there.
> --
> Will Robinson
sql
diskpar and Hitachi SAN for performance
We have a Hitachi Thunder SAN to host SharePoint databases. We are running
SQL server 2000 SP3 in a 2 node active/passive cluster. I have read article
s
stating to run diskpar to align the offset correctly with the disks to
dramatically increase performance. I'm undecided on whether I should run
diskpar.
Does anybody have experience of seeing improvement using Hitachi SANs?
There seems to be more experience with Exchange than SQL out there.
--
Will RobinsonHi
Yes, run it. The alignment of OS blocks with the underlying SAN block does
eliminate the need for the SAN to do unnecessary IO.
Also, make sure that your formatting matches your SAN's block size. On or
Hitachi and EMC's, we format the drives with 64kb blocks, as this matches
SQL Server I/O sizes and our SAN's stripe size.
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/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:C95D1918-D841-42F9-B156-1C00A7BF8304@.microsoft.com...
> We have a Hitachi Thunder SAN to host SharePoint databases. We are
> running
> SQL server 2000 SP3 in a 2 node active/passive cluster. I have read
> articles
> stating to run diskpar to align the offset correctly with the disks to
> dramatically increase performance. I'm undecided on whether I should run
> diskpar.
> Does anybody have experience of seeing improvement using Hitachi SANs?
> There seems to be more experience with Exchange than SQL out there.
> --
> Will Robinson
SQL server 2000 SP3 in a 2 node active/passive cluster. I have read article
s
stating to run diskpar to align the offset correctly with the disks to
dramatically increase performance. I'm undecided on whether I should run
diskpar.
Does anybody have experience of seeing improvement using Hitachi SANs?
There seems to be more experience with Exchange than SQL out there.
--
Will RobinsonHi
Yes, run it. The alignment of OS blocks with the underlying SAN block does
eliminate the need for the SAN to do unnecessary IO.
Also, make sure that your formatting matches your SAN's block size. On or
Hitachi and EMC's, we format the drives with 64kb blocks, as this matches
SQL Server I/O sizes and our SAN's stripe size.
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/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:C95D1918-D841-42F9-B156-1C00A7BF8304@.microsoft.com...
> We have a Hitachi Thunder SAN to host SharePoint databases. We are
> running
> SQL server 2000 SP3 in a 2 node active/passive cluster. I have read
> articles
> stating to run diskpar to align the offset correctly with the disks to
> dramatically increase performance. I'm undecided on whether I should run
> diskpar.
> Does anybody have experience of seeing improvement using Hitachi SANs?
> There seems to be more experience with Exchange than SQL out there.
> --
> Will Robinson
2012年3月25日星期日
Disk exchange on two-node MS SQL 2000 active/active cluster
Hi!
I have two-node cluster on Windows 2000 Adv Server sp4. There are two
instanses of MS SQL 2000 Server sp3, one on each node. I have one
physical disk owened by the first node, that is not used. I need to
transfer it to the second node, name it with the letter this node
already has (removing the disk with this letter from the node by
renaming it or just by deleting) and place on it SQL Server logs that
were located on the disk with this letter.
This is my plan:
1. Transfer disk Z: from node SQL1 to node SQL2
2. Stop sql server and agent services on node SQL2 (or take them
offline with cluster administrator) WHich is better?
3. Copy log files from disk V: to disk Z: on node SQL2
4. Delete disk V: (or rename it as lets say P: ) - I plan to remove
the mirror with the former V: disk from storage
5. Rename disk Z: to disk V: on node SQL2
6. Start sql server and agent services on node SQL2 (or take them
online with cluster administrator)
Is the plan correct? Are there any dangers like (suppose) node signs
its drives and will not accept another disk because of it or because
the disks are a bit different in size? Anything else?
Thanks.
I will be doing something similar this Sunday morning, but with a 2003
cluster. Comments inline.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0405210601.2d69da11@.posting.google.c om...
> Hi!
> I have two-node cluster on Windows 2000 Adv Server sp4. There are two
> instanses of MS SQL 2000 Server sp3, one on each node. I have one
> physical disk owened by the first node, that is not used. I need to
> transfer it to the second node, name it with the letter this node
> already has (removing the disk with this letter from the node by
> renaming it or just by deleting) and place on it SQL Server logs that
> were located on the disk with this letter.
> This is my plan:
> 1. Transfer disk Z: from node SQL1 to node SQL2
> 2. Stop sql server and agent services on node SQL2 (or take them
> offline with cluster administrator) WHich is better?
Use Cluster administrator to take the SQL service offline but leave the disk
resources online.
> 3. Copy log files from disk V: to disk Z: on node SQL2
>
Good.
> 4. Delete disk V: (or rename it as lets say P: ) - I plan to remove
> the mirror with the former V: disk from storage
>
Reletter it. Take it out of the SQL resource group.
> 5. Rename disk Z: to disk V: on node SQL2
>
Add this disk to the SQL resource group. Make SQL Server dependant on this
disk resource.
> 6. Start sql server and agent services on node SQL2 (or take them
> online with cluster administrator)
> Is the plan correct? Are there any dangers like (suppose) node signs
> its drives and will not accept another disk because of it or because
> the disks are a bit different in size? Anything else?
>
I have tested this once with a complete disk replacement using a test build.
Everything worked as expected. Make sure SQL stays offline while you are
moving things around. Make double sure you have fixed the dependancies.
Backup the universe before trying anything.
> Thanks.
|||Trying to transfer disk Z: from node SQL1 to node SQL2 (right mouse
button, change group, choose SQL2) get a window:
Are you sure the 'SQL1 Backup Z:' resource should be moved from the
''SQL1' group to the ''SQL2' group?
Choose "Yes"
Get another message:
Move Resources
The group will be changed for the following resources:
SQL1 Backup Z: (Only this resource, that means that I removed SQL
Server and dependancies from it)
Choose "Yes" again:
Get an error:
An error occured attempting to change the group of the 'Node2_BACKUP
Z:' resource to 'Node1'
The cluster node is not the owner of the group.
Error ID: 5016 (00001398).
Could not find how to change this.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message news:<urKIL3zPEHA.3012@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> I will be doing something similar this Sunday morning, but with a 2003
> cluster. Comments inline.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Roust_m" <roustam@.hotbox.ru> wrote in message
> news:a388fd78.0405210601.2d69da11@.posting.google.c om...
> Use Cluster administrator to take the SQL service offline but leave the disk
> resources online.
> Good.
> Reletter it. Take it out of the SQL resource group.
> Add this disk to the SQL resource group. Make SQL Server dependant on this
> disk resource.
> I have tested this once with a complete disk replacement using a test build.
> Everything worked as expected. Make sure SQL stays offline while you are
> moving things around. Make double sure you have fixed the dependancies.
> Backup the universe before trying anything.
|||Bring both resource groups to the node you are logged into. Do the group
changes from that machine.
FYI, my changeover went smoothly. No issues with a replacement partition as
long as the group membership and dependancies are correct.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0405220639.1bc712da@.posting.google.c om...
> Trying to transfer disk Z: from node SQL1 to node SQL2 (right mouse
> button, change group, choose SQL2) get a window:
> Are you sure the 'SQL1 Backup Z:' resource should be moved from the
> ''SQL1' group to the ''SQL2' group?
> Choose "Yes"
> Get another message:
> Move Resources
> The group will be changed for the following resources:
> SQL1 Backup Z: (Only this resource, that means that I removed SQL
> Server and dependancies from it)
> Choose "Yes" again:
> Get an error:
> An error occured attempting to change the group of the 'Node2_BACKUP
> Z:' resource to 'Node1'
> The cluster node is not the owner of the group.
> Error ID: 5016 (00001398).
> Could not find how to change this.
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:<urKIL3zPEHA.3012@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
disk[vbcol=seagreen]
this[vbcol=seagreen]
build.[vbcol=seagreen]
are[vbcol=seagreen]
|||Hi!
I tried to bring everything to the node I was loged on and the node I
was trying to give ownership of the disk (the same node) - the same
error. Just deleted this resource and recreated it on the correct node.
After this all went fine.
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
I have two-node cluster on Windows 2000 Adv Server sp4. There are two
instanses of MS SQL 2000 Server sp3, one on each node. I have one
physical disk owened by the first node, that is not used. I need to
transfer it to the second node, name it with the letter this node
already has (removing the disk with this letter from the node by
renaming it or just by deleting) and place on it SQL Server logs that
were located on the disk with this letter.
This is my plan:
1. Transfer disk Z: from node SQL1 to node SQL2
2. Stop sql server and agent services on node SQL2 (or take them
offline with cluster administrator) WHich is better?
3. Copy log files from disk V: to disk Z: on node SQL2
4. Delete disk V: (or rename it as lets say P: ) - I plan to remove
the mirror with the former V: disk from storage
5. Rename disk Z: to disk V: on node SQL2
6. Start sql server and agent services on node SQL2 (or take them
online with cluster administrator)
Is the plan correct? Are there any dangers like (suppose) node signs
its drives and will not accept another disk because of it or because
the disks are a bit different in size? Anything else?
Thanks.
I will be doing something similar this Sunday morning, but with a 2003
cluster. Comments inline.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0405210601.2d69da11@.posting.google.c om...
> Hi!
> I have two-node cluster on Windows 2000 Adv Server sp4. There are two
> instanses of MS SQL 2000 Server sp3, one on each node. I have one
> physical disk owened by the first node, that is not used. I need to
> transfer it to the second node, name it with the letter this node
> already has (removing the disk with this letter from the node by
> renaming it or just by deleting) and place on it SQL Server logs that
> were located on the disk with this letter.
> This is my plan:
> 1. Transfer disk Z: from node SQL1 to node SQL2
> 2. Stop sql server and agent services on node SQL2 (or take them
> offline with cluster administrator) WHich is better?
Use Cluster administrator to take the SQL service offline but leave the disk
resources online.
> 3. Copy log files from disk V: to disk Z: on node SQL2
>
Good.
> 4. Delete disk V: (or rename it as lets say P: ) - I plan to remove
> the mirror with the former V: disk from storage
>
Reletter it. Take it out of the SQL resource group.
> 5. Rename disk Z: to disk V: on node SQL2
>
Add this disk to the SQL resource group. Make SQL Server dependant on this
disk resource.
> 6. Start sql server and agent services on node SQL2 (or take them
> online with cluster administrator)
> Is the plan correct? Are there any dangers like (suppose) node signs
> its drives and will not accept another disk because of it or because
> the disks are a bit different in size? Anything else?
>
I have tested this once with a complete disk replacement using a test build.
Everything worked as expected. Make sure SQL stays offline while you are
moving things around. Make double sure you have fixed the dependancies.
Backup the universe before trying anything.
> Thanks.
|||Trying to transfer disk Z: from node SQL1 to node SQL2 (right mouse
button, change group, choose SQL2) get a window:
Are you sure the 'SQL1 Backup Z:' resource should be moved from the
''SQL1' group to the ''SQL2' group?
Choose "Yes"
Get another message:
Move Resources
The group will be changed for the following resources:
SQL1 Backup Z: (Only this resource, that means that I removed SQL
Server and dependancies from it)
Choose "Yes" again:
Get an error:
An error occured attempting to change the group of the 'Node2_BACKUP
Z:' resource to 'Node1'
The cluster node is not the owner of the group.
Error ID: 5016 (00001398).
Could not find how to change this.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message news:<urKIL3zPEHA.3012@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> I will be doing something similar this Sunday morning, but with a 2003
> cluster. Comments inline.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Roust_m" <roustam@.hotbox.ru> wrote in message
> news:a388fd78.0405210601.2d69da11@.posting.google.c om...
> Use Cluster administrator to take the SQL service offline but leave the disk
> resources online.
> Good.
> Reletter it. Take it out of the SQL resource group.
> Add this disk to the SQL resource group. Make SQL Server dependant on this
> disk resource.
> I have tested this once with a complete disk replacement using a test build.
> Everything worked as expected. Make sure SQL stays offline while you are
> moving things around. Make double sure you have fixed the dependancies.
> Backup the universe before trying anything.
|||Bring both resource groups to the node you are logged into. Do the group
changes from that machine.
FYI, my changeover went smoothly. No issues with a replacement partition as
long as the group membership and dependancies are correct.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0405220639.1bc712da@.posting.google.c om...
> Trying to transfer disk Z: from node SQL1 to node SQL2 (right mouse
> button, change group, choose SQL2) get a window:
> Are you sure the 'SQL1 Backup Z:' resource should be moved from the
> ''SQL1' group to the ''SQL2' group?
> Choose "Yes"
> Get another message:
> Move Resources
> The group will be changed for the following resources:
> SQL1 Backup Z: (Only this resource, that means that I removed SQL
> Server and dependancies from it)
> Choose "Yes" again:
> Get an error:
> An error occured attempting to change the group of the 'Node2_BACKUP
> Z:' resource to 'Node1'
> The cluster node is not the owner of the group.
> Error ID: 5016 (00001398).
> Could not find how to change this.
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:<urKIL3zPEHA.3012@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
disk[vbcol=seagreen]
this[vbcol=seagreen]
build.[vbcol=seagreen]
are[vbcol=seagreen]
|||Hi!
I tried to bring everything to the node I was loged on and the node I
was trying to give ownership of the disk (the same node) - the same
error. Just deleted this resource and recreated it on the correct node.
After this all went fine.
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
2012年3月20日星期二
Discovery of instances not correct with SCOM DBCreateWizard.exe
I have a 2 node cluster active/passive 2003 SP2 cluster.
I have 4 instances
SQLSRVISPS1\SQLSRV1
SQLSRVISPS2\SQLSRV2
SQLSRVIMGMT\SQLMGMT
SQLSRVIISA\SQLISA
When I use the DBCreateWizard.Exe to create the databases for SCOM, the
instances are wrongly discovered as :
SQLSRVISPS2\SQLSRV1
SQLSRVISPS2\SQLSRV2
SQLSRVISPS2\SQLMGMT
SQLSRVISPS2\SQLISA
Has anyone an idea how I can resolve this ?
Thanks
Carla
Since that's a Microsoft application, I would just talk to the MS support to
get a fix (if it's indeed a problem).
Linchi
"Carla" wrote:
> I have a 2 node cluster active/passive 2003 SP2 cluster.
> I have 4 instances
> SQLSRVISPS1\SQLSRV1
> SQLSRVISPS2\SQLSRV2
> SQLSRVIMGMT\SQLMGMT
> SQLSRVIISA\SQLISA
> When I use the DBCreateWizard.Exe to create the databases for SCOM, the
> instances are wrongly discovered as :
> SQLSRVISPS2\SQLSRV1
> SQLSRVISPS2\SQLSRV2
> SQLSRVISPS2\SQLMGMT
> SQLSRVISPS2\SQLISA
> Has anyone an idea how I can resolve this ?
> Thanks
> --
> Carla
I have 4 instances
SQLSRVISPS1\SQLSRV1
SQLSRVISPS2\SQLSRV2
SQLSRVIMGMT\SQLMGMT
SQLSRVIISA\SQLISA
When I use the DBCreateWizard.Exe to create the databases for SCOM, the
instances are wrongly discovered as :
SQLSRVISPS2\SQLSRV1
SQLSRVISPS2\SQLSRV2
SQLSRVISPS2\SQLMGMT
SQLSRVISPS2\SQLISA
Has anyone an idea how I can resolve this ?
Thanks
Carla
Since that's a Microsoft application, I would just talk to the MS support to
get a fix (if it's indeed a problem).
Linchi
"Carla" wrote:
> I have a 2 node cluster active/passive 2003 SP2 cluster.
> I have 4 instances
> SQLSRVISPS1\SQLSRV1
> SQLSRVISPS2\SQLSRV2
> SQLSRVIMGMT\SQLMGMT
> SQLSRVIISA\SQLISA
> When I use the DBCreateWizard.Exe to create the databases for SCOM, the
> instances are wrongly discovered as :
> SQLSRVISPS2\SQLSRV1
> SQLSRVISPS2\SQLSRV2
> SQLSRVISPS2\SQLMGMT
> SQLSRVISPS2\SQLISA
> Has anyone an idea how I can resolve this ?
> Thanks
> --
> Carla
2012年3月19日星期一
Disconnect Issues & RPC Server Unavailable
We have recently upgraded our main server from NT4 to Active Directory
(Windows 2003 Server). Our SQL Database is 2000 and is running on a Windows
2000 Server Box. We use com+ components to connect to our database. Since
the change on our PDC to 2003 Server AD, we have had several errors such as
"The object invoked has disconnected from its clients" as well as RPC Server
Unavailable. This occurs even when the user is consistently active. We have
applied latest Windows Service Pack to clients xp sp2 and to the windows 2000
server box. If you reboot the server and or/stop services (Com+ and Dcom) on
the client end, they can get back in. You can browse to the machine no
problem through exporer - right to the database. Issue is only in SQL 2000.
Any assistance would be greatly appreciated. Note: I have also checked
using netstat -a to see if all ports were being used and that is not the
case. This is happening on more than one users connection and I am certain
it is not network based - ping 100%, can browse, two locations within
building etc.
We had a similar problem after upgrading clients to XP SP2, the problem
turned out to be the MDAC version that ships with SP2. Apparently, the new
version of MDAC has issues keeping a connection with the DB if it is using
named pipes. An example of this is when we would run a restore with QA using
the normal connection to a server(named pipes) it would die and say
something about a disconnect even though ping is at 100%. As soon as we
forced tcp/ip on QA everything worked fine. Might try setting up an alias to
the server using tcp/ip to see if that makes a difference.
KevinE
"Cstewart" <Cstewart@.discussions.microsoft.com> wrote in message
news:7FEEA68E-6785-480B-9F97-C81C7BD0ACD1@.microsoft.com...
> We have recently upgraded our main server from NT4 to Active Directory
> (Windows 2003 Server). Our SQL Database is 2000 and is running on a
> Windows
> 2000 Server Box. We use com+ components to connect to our database.
> Since
> the change on our PDC to 2003 Server AD, we have had several errors such
> as
> "The object invoked has disconnected from its clients" as well as RPC
> Server
> Unavailable. This occurs even when the user is consistently active. We
> have
> applied latest Windows Service Pack to clients xp sp2 and to the windows
> 2000
> server box. If you reboot the server and or/stop services (Com+ and Dcom)
> on
> the client end, they can get back in. You can browse to the machine no
> problem through exporer - right to the database. Issue is only in SQL
> 2000.
> Any assistance would be greatly appreciated. Note: I have also checked
> using netstat -a to see if all ports were being used and that is not the
> case. This is happening on more than one users connection and I am
> certain
> it is not network based - ping 100%, can browse, two locations within
> building etc.
|||The issue is regardless of sp1 or 2. Any error logs you can suggest for me
to look at?
Thank you
"KevinE" wrote:
> We had a similar problem after upgrading clients to XP SP2, the problem
> turned out to be the MDAC version that ships with SP2. Apparently, the new
> version of MDAC has issues keeping a connection with the DB if it is using
> named pipes. An example of this is when we would run a restore with QA using
> the normal connection to a server(named pipes) it would die and say
> something about a disconnect even though ping is at 100%. As soon as we
> forced tcp/ip on QA everything worked fine. Might try setting up an alias to
> the server using tcp/ip to see if that makes a difference.
> KevinE
> "Cstewart" <Cstewart@.discussions.microsoft.com> wrote in message
> news:7FEEA68E-6785-480B-9F97-C81C7BD0ACD1@.microsoft.com...
>
>
(Windows 2003 Server). Our SQL Database is 2000 and is running on a Windows
2000 Server Box. We use com+ components to connect to our database. Since
the change on our PDC to 2003 Server AD, we have had several errors such as
"The object invoked has disconnected from its clients" as well as RPC Server
Unavailable. This occurs even when the user is consistently active. We have
applied latest Windows Service Pack to clients xp sp2 and to the windows 2000
server box. If you reboot the server and or/stop services (Com+ and Dcom) on
the client end, they can get back in. You can browse to the machine no
problem through exporer - right to the database. Issue is only in SQL 2000.
Any assistance would be greatly appreciated. Note: I have also checked
using netstat -a to see if all ports were being used and that is not the
case. This is happening on more than one users connection and I am certain
it is not network based - ping 100%, can browse, two locations within
building etc.
We had a similar problem after upgrading clients to XP SP2, the problem
turned out to be the MDAC version that ships with SP2. Apparently, the new
version of MDAC has issues keeping a connection with the DB if it is using
named pipes. An example of this is when we would run a restore with QA using
the normal connection to a server(named pipes) it would die and say
something about a disconnect even though ping is at 100%. As soon as we
forced tcp/ip on QA everything worked fine. Might try setting up an alias to
the server using tcp/ip to see if that makes a difference.
KevinE
"Cstewart" <Cstewart@.discussions.microsoft.com> wrote in message
news:7FEEA68E-6785-480B-9F97-C81C7BD0ACD1@.microsoft.com...
> We have recently upgraded our main server from NT4 to Active Directory
> (Windows 2003 Server). Our SQL Database is 2000 and is running on a
> Windows
> 2000 Server Box. We use com+ components to connect to our database.
> Since
> the change on our PDC to 2003 Server AD, we have had several errors such
> as
> "The object invoked has disconnected from its clients" as well as RPC
> Server
> Unavailable. This occurs even when the user is consistently active. We
> have
> applied latest Windows Service Pack to clients xp sp2 and to the windows
> 2000
> server box. If you reboot the server and or/stop services (Com+ and Dcom)
> on
> the client end, they can get back in. You can browse to the machine no
> problem through exporer - right to the database. Issue is only in SQL
> 2000.
> Any assistance would be greatly appreciated. Note: I have also checked
> using netstat -a to see if all ports were being used and that is not the
> case. This is happening on more than one users connection and I am
> certain
> it is not network based - ping 100%, can browse, two locations within
> building etc.
|||The issue is regardless of sp1 or 2. Any error logs you can suggest for me
to look at?
Thank you
"KevinE" wrote:
> We had a similar problem after upgrading clients to XP SP2, the problem
> turned out to be the MDAC version that ships with SP2. Apparently, the new
> version of MDAC has issues keeping a connection with the DB if it is using
> named pipes. An example of this is when we would run a restore with QA using
> the normal connection to a server(named pipes) it would die and say
> something about a disconnect even though ping is at 100%. As soon as we
> forced tcp/ip on QA everything worked fine. Might try setting up an alias to
> the server using tcp/ip to see if that makes a difference.
> KevinE
> "Cstewart" <Cstewart@.discussions.microsoft.com> wrote in message
> news:7FEEA68E-6785-480B-9F97-C81C7BD0ACD1@.microsoft.com...
>
>
2012年3月11日星期日
Disaster Recovery Tests
Currently we use Log shipping between our active site and our DR site. The
question I have is when we do DR testing at the DR site to test
recoverability, we have to recover all those Log shipped databases which
means we are exposed until our DR tests are completed.
How does one go about ensuring we do not get exposed and continue to keep
data current and yet be able to test. Does that mean I have to log ship to 2
instances ? We have so many databases with TBs of storage and now I have to
double the storage and maintenance..
Anyways, are there other ways of doing so than Log shipping ?
We are on the SAN.When you say "exposed," what do you mean? What we do is we have DNS
settings that we manually change (IP address changes, that is) during DR
tests. This in itself will prevent anybody from accessing the production
servers, unless they know the server and instance names and access the
servers directly. After DR tests, we revert to the original IP addresses of
the production servers configured on our DNS settings.
"Hassan" <hassan@.hotmail.com> wrote in message
news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
> Currently we use Log shipping between our active site and our DR site. The
> question I have is when we do DR testing at the DR site to test
> recoverability, we have to recover all those Log shipped databases which
> means we are exposed until our DR tests are completed.
> How does one go about ensuring we do not get exposed and continue to keep
> data current and yet be able to test. Does that mean I have to log ship to
> 2 instances ? We have so many databases with TBs of storage and now I have
> to double the storage and maintenance..
> Anyways, are there other ways of doing so than Log shipping ?
> We are on the SAN.
>|||I meant exposed at the DR site by not receiving logs and being current as
the log ship databases would be recovered for DR testing..
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u7im1C7AIHA.4476@.TK2MSFTNGP06.phx.gbl...
> When you say "exposed," what do you mean? What we do is we have DNS
> settings that we manually change (IP address changes, that is) during DR
> tests. This in itself will prevent anybody from accessing the production
> servers, unless they know the server and instance names and access the
> servers directly. After DR tests, we revert to the original IP addresses
> of the production servers configured on our DNS settings.
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
>> Currently we use Log shipping between our active site and our DR site.
>> The question I have is when we do DR testing at the DR site to test
>> recoverability, we have to recover all those Log shipped databases which
>> means we are exposed until our DR tests are completed.
>> How does one go about ensuring we do not get exposed and continue to keep
>> data current and yet be able to test. Does that mean I have to log ship
>> to 2 instances ? We have so many databases with TBs of storage and now I
>> have to double the storage and maintenance..
>> Anyways, are there other ways of doing so than Log shipping ?
>> We are on the SAN.
>|||Hassan
RESTORE DATABASE database_name WITH RECOVERY
"Hassan" <hassan@.hotmail.com> wrote in message
news:%23MvD1r7AIHA.2268@.TK2MSFTNGP04.phx.gbl...
>I meant exposed at the DR site by not receiving logs and being current as
>the log ship databases would be recovered for DR testing..
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:u7im1C7AIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> When you say "exposed," what do you mean? What we do is we have DNS
>> settings that we manually change (IP address changes, that is) during DR
>> tests. This in itself will prevent anybody from accessing the production
>> servers, unless they know the server and instance names and access the
>> servers directly. After DR tests, we revert to the original IP addresses
>> of the production servers configured on our DNS settings.
>>
>> "Hassan" <hassan@.hotmail.com> wrote in message
>> news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
>> Currently we use Log shipping between our active site and our DR site.
>> The question I have is when we do DR testing at the DR site to test
>> recoverability, we have to recover all those Log shipped databases which
>> means we are exposed until our DR tests are completed.
>> How does one go about ensuring we do not get exposed and continue to
>> keep data current and yet be able to test. Does that mean I have to log
>> ship to 2 instances ? We have so many databases with TBs of storage and
>> now I have to double the storage and maintenance..
>> Anyways, are there other ways of doing so than Log shipping ?
>> We are on the SAN.
>>
>
question I have is when we do DR testing at the DR site to test
recoverability, we have to recover all those Log shipped databases which
means we are exposed until our DR tests are completed.
How does one go about ensuring we do not get exposed and continue to keep
data current and yet be able to test. Does that mean I have to log ship to 2
instances ? We have so many databases with TBs of storage and now I have to
double the storage and maintenance..
Anyways, are there other ways of doing so than Log shipping ?
We are on the SAN.When you say "exposed," what do you mean? What we do is we have DNS
settings that we manually change (IP address changes, that is) during DR
tests. This in itself will prevent anybody from accessing the production
servers, unless they know the server and instance names and access the
servers directly. After DR tests, we revert to the original IP addresses of
the production servers configured on our DNS settings.
"Hassan" <hassan@.hotmail.com> wrote in message
news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
> Currently we use Log shipping between our active site and our DR site. The
> question I have is when we do DR testing at the DR site to test
> recoverability, we have to recover all those Log shipped databases which
> means we are exposed until our DR tests are completed.
> How does one go about ensuring we do not get exposed and continue to keep
> data current and yet be able to test. Does that mean I have to log ship to
> 2 instances ? We have so many databases with TBs of storage and now I have
> to double the storage and maintenance..
> Anyways, are there other ways of doing so than Log shipping ?
> We are on the SAN.
>|||I meant exposed at the DR site by not receiving logs and being current as
the log ship databases would be recovered for DR testing..
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u7im1C7AIHA.4476@.TK2MSFTNGP06.phx.gbl...
> When you say "exposed," what do you mean? What we do is we have DNS
> settings that we manually change (IP address changes, that is) during DR
> tests. This in itself will prevent anybody from accessing the production
> servers, unless they know the server and instance names and access the
> servers directly. After DR tests, we revert to the original IP addresses
> of the production servers configured on our DNS settings.
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
>> Currently we use Log shipping between our active site and our DR site.
>> The question I have is when we do DR testing at the DR site to test
>> recoverability, we have to recover all those Log shipped databases which
>> means we are exposed until our DR tests are completed.
>> How does one go about ensuring we do not get exposed and continue to keep
>> data current and yet be able to test. Does that mean I have to log ship
>> to 2 instances ? We have so many databases with TBs of storage and now I
>> have to double the storage and maintenance..
>> Anyways, are there other ways of doing so than Log shipping ?
>> We are on the SAN.
>|||Hassan
RESTORE DATABASE database_name WITH RECOVERY
"Hassan" <hassan@.hotmail.com> wrote in message
news:%23MvD1r7AIHA.2268@.TK2MSFTNGP04.phx.gbl...
>I meant exposed at the DR site by not receiving logs and being current as
>the log ship databases would be recovered for DR testing..
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:u7im1C7AIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> When you say "exposed," what do you mean? What we do is we have DNS
>> settings that we manually change (IP address changes, that is) during DR
>> tests. This in itself will prevent anybody from accessing the production
>> servers, unless they know the server and instance names and access the
>> servers directly. After DR tests, we revert to the original IP addresses
>> of the production servers configured on our DNS settings.
>>
>> "Hassan" <hassan@.hotmail.com> wrote in message
>> news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
>> Currently we use Log shipping between our active site and our DR site.
>> The question I have is when we do DR testing at the DR site to test
>> recoverability, we have to recover all those Log shipped databases which
>> means we are exposed until our DR tests are completed.
>> How does one go about ensuring we do not get exposed and continue to
>> keep data current and yet be able to test. Does that mean I have to log
>> ship to 2 instances ? We have so many databases with TBs of storage and
>> now I have to double the storage and maintenance..
>> Anyways, are there other ways of doing so than Log shipping ?
>> We are on the SAN.
>>
>
2012年3月8日星期四
Disaster Recovery
Hi GUYS,
I am having a very mission critical sql server 2000 database with active
passive failover cluster an d logshipping with interval of 2 minutes.
what additional disaster recovery techniques i should implement to have
99.99999 availability and
i can not afford any data loss.
Pls advice.
Rgds
BijuHi
Most compnaies will not get better than 99.9, maybe, 99.99, but 99.999 is
possible with a big big budget.
For Production, you need 2 sets of everthing with one set at a distant
location. Everthing must be vendor certified to work together, so Unisys,
IBM, HP and Dell and really your only choices. Data Center editions are
usually only certifiable for something like this.
Then have exacly the same setup for your Test enviroment, and the same again
for a development environment. Power, aircon, access control, at least 3 of
each, at each site.
Document everthing, from setup to operations to the finest detail. Have run
books, and regularly test the validity of them.
Have your architecture reviewed and certified by Microsoft and the Hardware
Vendor.
Have your application reviewed and certified by Microsoft
Have the most restrictive change control in place that, so that you can
nearly do nothing.
http://www.ftponline.com/wss/2004_11/magazine/features/nruest/default.aspx
http://www.microsoft.com/sql/techinfo/administration/2000/availability.asp
Super high availability is not a piece of equipment that you buy, it a whole
process that everyone has to work towards.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bijupg@.hotmail.com" wrote:
> Hi GUYS,
> I am having a very mission critical sql server 2000 database with active
> passive failover cluster an d logshipping with interval of 2 minutes.
> what additional disaster recovery techniques i should implement to have
> 99.99999 availability and
> i can not afford any data loss.
> Pls advice.
> Rgds
> Biju|||This is a multi-part message in MIME format.
--040907010300030705010102
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
No such thing as guaranteed zero data loss. Even with tlog backups
every 2 minutes there is still a 2+ minute window (backup interval +
time to transmit backup file to secondary and restore) during which if
you lost your primary DB you would lose some data.
Basically the cost of the DR solution increases inversely exponentially
with the acceptable data loss window. With SAN to SAN mirroring
technology, which is very expensive in terms of disk space requirements,
bandwidth & $$$, you could probably get the data loss window down to a
second or two. When we evaluated EMC's SAN to SAN
snap/cloning/mirroring on their Clariion SAN range about 2 years ago the
technology wasn't quite ready. I expect it's probably improved a bit
since then but I'm still skeptical about SAN black magic (especially
since DB consistency can be a bit touchy when you don't go through the
approved RDBMS server processes).
The main problem we had with the technology a couple years ago was the
fact that it really needed synchronous comms between the 2 SANs. Since
we were looking at SANs in 2 geographically separated data centres the
latency between SANs over a typical IP network (on UTP for instance)
would mean every write on our primary SAN would be delayed for 10-30ms
while the data committed on the secondary SAN too (that's way too much
for every SAN write). The only solution was fibre between the 2 data
centres and over about 7km that was far too expensive.
DR is all a balance between acceptable data loss, time to recovery & the
amount of money you're willing to spend on the solution. It sounds like
you're already protecting your data pretty well. Five 9s is
theoretically about 5 minutes downtime per year. Half a dozen cluster
failovers over the course of the year in order to apply Windows hotfixes
to your cluster nodes will pretty much blow your five 9s margin. It's a
good target to aim for but one only the richest companies can attain.
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi GUYS,
>I am having a very mission critical sql server 2000 database with active
>passive failover cluster an d logshipping with interval of 2 minutes.
>what additional disaster recovery techniques i should implement to have
>99.99999 availability and
>i can not afford any data loss.
>Pls advice.
>Rgds
>Biju
>
--040907010300030705010102
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>No such thing as guaranteed zero data loss. Even with tlog backups
every 2 minutes there is still a 2+ minute window (backup interval +
time to transmit backup file to secondary and restore) during which if
you lost your primary DB you would lose some data.<br>
<br>
Basically the cost of the DR solution increases inversely exponentially
with the acceptable data loss window. With SAN to SAN mirroring
technology, which is very expensive in terms of disk space
requirements, bandwidth & $$$, you could probably get the data loss
window down to a second or two. When we evaluated EMC's SAN to SAN
snap/cloning/mirroring on their Clariion SAN range about 2 years ago
the technology wasn't quite ready. I expect it's probably improved a
bit since then but I'm still skeptical about SAN black magic
(especially since DB consistency can be a bit touchy when you don't go
through the approved RDBMS server processes).<br>
<br>
The main problem we had with the technology a couple years ago was the
fact that it really needed synchronous comms between the 2 SANs. Since
we were looking at SANs in 2 geographically separated data centres the
latency between SANs over a typical IP network (on UTP for instance)
would mean every write on our primary SAN would be delayed for 10-30ms
while the data committed on the secondary SAN too (that's way too much
for every SAN write). The only solution was fibre between the 2 data
centres and over about 7km that was far too expensive.<br>
<br>
DR is all a balance between acceptable data loss, time to recovery
& the amount of money you're willing to spend on the solution. It
sounds like you're already protecting your data pretty well. Five 9s
is theoretically about 5 minutes downtime per year. Half a dozen
cluster failovers over the course of the year in order to apply Windows
hotfixes to your cluster nodes will pretty much blow your five 9s
margin. It's a good target to aim for but one only the richest
companies can attain. <br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:bijupg@.hotmail.com">bijupg@.hotmail.com</a> wrote:
<blockquote cite="midD390CB5E-2AF0-476F-9E11-718D159B74DC@.microsoft.com"
type="cite">
<pre wrap="">Hi GUYS,
I am having a very mission critical sql server 2000 database with active
passive failover cluster an d logshipping with interval of 2 minutes.
what additional disaster recovery techniques i should implement to have
99.99999 availability and
i can not afford any data loss.
Pls advice.
Rgds
Biju
</pre>
</blockquote>
</body>
</html>
--040907010300030705010102--|||is it agood idea to replace harddisks in raid 10 to avoid any possible data
corruption?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most compnaies will not get better than 99.9, maybe, 99.99, but 99.999 is
> possible with a big big budget.
> For Production, you need 2 sets of everthing with one set at a distant
> location. Everthing must be vendor certified to work together, so Unisys,
> IBM, HP and Dell and really your only choices. Data Center editions are
> usually only certifiable for something like this.
> Then have exacly the same setup for your Test enviroment, and the same again
> for a development environment. Power, aircon, access control, at least 3 of
> each, at each site.
> Document everthing, from setup to operations to the finest detail. Have run
> books, and regularly test the validity of them.
> Have your architecture reviewed and certified by Microsoft and the Hardware
> Vendor.
> Have your application reviewed and certified by Microsoft
> Have the most restrictive change control in place that, so that you can
> nearly do nothing.
> http://www.ftponline.com/wss/2004_11/magazine/features/nruest/default.aspx
> http://www.microsoft.com/sql/techinfo/administration/2000/availability.asp
> Super high availability is not a piece of equipment that you buy, it a whole
> process that everyone has to work towards.
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "bijupg@.hotmail.com" wrote:
> > Hi GUYS,
> > I am having a very mission critical sql server 2000 database with active
> > passive failover cluster an d logshipping with interval of 2 minutes.
> > what additional disaster recovery techniques i should implement to have
> > 99.99999 availability and
> > i can not afford any data loss.
> > Pls advice.
> > Rgds
> > Biju|||RAID 1+0 is a good fit for SQL Server data disks but it will not protect
against all data corruption issues. It will minimize the chance for data
loss due to disk hardware issues but cannot protect against a controller
failure or an Operating System problem. As Mike said; availability is a
process, not an piece of equipment.
Geoff N. Hiten
Microsoft SQL Server MVP
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:5F2A5F0C-D565-43D6-AB19-64467990E0D9@.microsoft.com...
> is it agood idea to replace harddisks in raid 10 to avoid any possible
> data
> corruption?
>
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Most compnaies will not get better than 99.9, maybe, 99.99, but 99.999 is
>> possible with a big big budget.
>> For Production, you need 2 sets of everthing with one set at a distant
>> location. Everthing must be vendor certified to work together, so Unisys,
>> IBM, HP and Dell and really your only choices. Data Center editions are
>> usually only certifiable for something like this.
>> Then have exacly the same setup for your Test enviroment, and the same
>> again
>> for a development environment. Power, aircon, access control, at least 3
>> of
>> each, at each site.
>> Document everthing, from setup to operations to the finest detail. Have
>> run
>> books, and regularly test the validity of them.
>> Have your architecture reviewed and certified by Microsoft and the
>> Hardware
>> Vendor.
>> Have your application reviewed and certified by Microsoft
>> Have the most restrictive change control in place that, so that you can
>> nearly do nothing.
>> http://www.ftponline.com/wss/2004_11/magazine/features/nruest/default.aspx
>> http://www.microsoft.com/sql/techinfo/administration/2000/availability.asp
>> Super high availability is not a piece of equipment that you buy, it a
>> whole
>> process that everyone has to work towards.
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>>
>> "bijupg@.hotmail.com" wrote:
>> > Hi GUYS,
>> > I am having a very mission critical sql server 2000 database with
>> > active
>> > passive failover cluster an d logshipping with interval of 2 minutes.
>> > what additional disaster recovery techniques i should implement to have
>> > 99.99999 availability and
>> > i can not afford any data loss.
>> > Pls advice.
>> > Rgds
>> > Biju
I am having a very mission critical sql server 2000 database with active
passive failover cluster an d logshipping with interval of 2 minutes.
what additional disaster recovery techniques i should implement to have
99.99999 availability and
i can not afford any data loss.
Pls advice.
Rgds
BijuHi
Most compnaies will not get better than 99.9, maybe, 99.99, but 99.999 is
possible with a big big budget.
For Production, you need 2 sets of everthing with one set at a distant
location. Everthing must be vendor certified to work together, so Unisys,
IBM, HP and Dell and really your only choices. Data Center editions are
usually only certifiable for something like this.
Then have exacly the same setup for your Test enviroment, and the same again
for a development environment. Power, aircon, access control, at least 3 of
each, at each site.
Document everthing, from setup to operations to the finest detail. Have run
books, and regularly test the validity of them.
Have your architecture reviewed and certified by Microsoft and the Hardware
Vendor.
Have your application reviewed and certified by Microsoft
Have the most restrictive change control in place that, so that you can
nearly do nothing.
http://www.ftponline.com/wss/2004_11/magazine/features/nruest/default.aspx
http://www.microsoft.com/sql/techinfo/administration/2000/availability.asp
Super high availability is not a piece of equipment that you buy, it a whole
process that everyone has to work towards.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bijupg@.hotmail.com" wrote:
> Hi GUYS,
> I am having a very mission critical sql server 2000 database with active
> passive failover cluster an d logshipping with interval of 2 minutes.
> what additional disaster recovery techniques i should implement to have
> 99.99999 availability and
> i can not afford any data loss.
> Pls advice.
> Rgds
> Biju|||This is a multi-part message in MIME format.
--040907010300030705010102
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
No such thing as guaranteed zero data loss. Even with tlog backups
every 2 minutes there is still a 2+ minute window (backup interval +
time to transmit backup file to secondary and restore) during which if
you lost your primary DB you would lose some data.
Basically the cost of the DR solution increases inversely exponentially
with the acceptable data loss window. With SAN to SAN mirroring
technology, which is very expensive in terms of disk space requirements,
bandwidth & $$$, you could probably get the data loss window down to a
second or two. When we evaluated EMC's SAN to SAN
snap/cloning/mirroring on their Clariion SAN range about 2 years ago the
technology wasn't quite ready. I expect it's probably improved a bit
since then but I'm still skeptical about SAN black magic (especially
since DB consistency can be a bit touchy when you don't go through the
approved RDBMS server processes).
The main problem we had with the technology a couple years ago was the
fact that it really needed synchronous comms between the 2 SANs. Since
we were looking at SANs in 2 geographically separated data centres the
latency between SANs over a typical IP network (on UTP for instance)
would mean every write on our primary SAN would be delayed for 10-30ms
while the data committed on the secondary SAN too (that's way too much
for every SAN write). The only solution was fibre between the 2 data
centres and over about 7km that was far too expensive.
DR is all a balance between acceptable data loss, time to recovery & the
amount of money you're willing to spend on the solution. It sounds like
you're already protecting your data pretty well. Five 9s is
theoretically about 5 minutes downtime per year. Half a dozen cluster
failovers over the course of the year in order to apply Windows hotfixes
to your cluster nodes will pretty much blow your five 9s margin. It's a
good target to aim for but one only the richest companies can attain.
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi GUYS,
>I am having a very mission critical sql server 2000 database with active
>passive failover cluster an d logshipping with interval of 2 minutes.
>what additional disaster recovery techniques i should implement to have
>99.99999 availability and
>i can not afford any data loss.
>Pls advice.
>Rgds
>Biju
>
--040907010300030705010102
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>No such thing as guaranteed zero data loss. Even with tlog backups
every 2 minutes there is still a 2+ minute window (backup interval +
time to transmit backup file to secondary and restore) during which if
you lost your primary DB you would lose some data.<br>
<br>
Basically the cost of the DR solution increases inversely exponentially
with the acceptable data loss window. With SAN to SAN mirroring
technology, which is very expensive in terms of disk space
requirements, bandwidth & $$$, you could probably get the data loss
window down to a second or two. When we evaluated EMC's SAN to SAN
snap/cloning/mirroring on their Clariion SAN range about 2 years ago
the technology wasn't quite ready. I expect it's probably improved a
bit since then but I'm still skeptical about SAN black magic
(especially since DB consistency can be a bit touchy when you don't go
through the approved RDBMS server processes).<br>
<br>
The main problem we had with the technology a couple years ago was the
fact that it really needed synchronous comms between the 2 SANs. Since
we were looking at SANs in 2 geographically separated data centres the
latency between SANs over a typical IP network (on UTP for instance)
would mean every write on our primary SAN would be delayed for 10-30ms
while the data committed on the secondary SAN too (that's way too much
for every SAN write). The only solution was fibre between the 2 data
centres and over about 7km that was far too expensive.<br>
<br>
DR is all a balance between acceptable data loss, time to recovery
& the amount of money you're willing to spend on the solution. It
sounds like you're already protecting your data pretty well. Five 9s
is theoretically about 5 minutes downtime per year. Half a dozen
cluster failovers over the course of the year in order to apply Windows
hotfixes to your cluster nodes will pretty much blow your five 9s
margin. It's a good target to aim for but one only the richest
companies can attain. <br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:bijupg@.hotmail.com">bijupg@.hotmail.com</a> wrote:
<blockquote cite="midD390CB5E-2AF0-476F-9E11-718D159B74DC@.microsoft.com"
type="cite">
<pre wrap="">Hi GUYS,
I am having a very mission critical sql server 2000 database with active
passive failover cluster an d logshipping with interval of 2 minutes.
what additional disaster recovery techniques i should implement to have
99.99999 availability and
i can not afford any data loss.
Pls advice.
Rgds
Biju
</pre>
</blockquote>
</body>
</html>
--040907010300030705010102--|||is it agood idea to replace harddisks in raid 10 to avoid any possible data
corruption?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most compnaies will not get better than 99.9, maybe, 99.99, but 99.999 is
> possible with a big big budget.
> For Production, you need 2 sets of everthing with one set at a distant
> location. Everthing must be vendor certified to work together, so Unisys,
> IBM, HP and Dell and really your only choices. Data Center editions are
> usually only certifiable for something like this.
> Then have exacly the same setup for your Test enviroment, and the same again
> for a development environment. Power, aircon, access control, at least 3 of
> each, at each site.
> Document everthing, from setup to operations to the finest detail. Have run
> books, and regularly test the validity of them.
> Have your architecture reviewed and certified by Microsoft and the Hardware
> Vendor.
> Have your application reviewed and certified by Microsoft
> Have the most restrictive change control in place that, so that you can
> nearly do nothing.
> http://www.ftponline.com/wss/2004_11/magazine/features/nruest/default.aspx
> http://www.microsoft.com/sql/techinfo/administration/2000/availability.asp
> Super high availability is not a piece of equipment that you buy, it a whole
> process that everyone has to work towards.
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "bijupg@.hotmail.com" wrote:
> > Hi GUYS,
> > I am having a very mission critical sql server 2000 database with active
> > passive failover cluster an d logshipping with interval of 2 minutes.
> > what additional disaster recovery techniques i should implement to have
> > 99.99999 availability and
> > i can not afford any data loss.
> > Pls advice.
> > Rgds
> > Biju|||RAID 1+0 is a good fit for SQL Server data disks but it will not protect
against all data corruption issues. It will minimize the chance for data
loss due to disk hardware issues but cannot protect against a controller
failure or an Operating System problem. As Mike said; availability is a
process, not an piece of equipment.
Geoff N. Hiten
Microsoft SQL Server MVP
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:5F2A5F0C-D565-43D6-AB19-64467990E0D9@.microsoft.com...
> is it agood idea to replace harddisks in raid 10 to avoid any possible
> data
> corruption?
>
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Most compnaies will not get better than 99.9, maybe, 99.99, but 99.999 is
>> possible with a big big budget.
>> For Production, you need 2 sets of everthing with one set at a distant
>> location. Everthing must be vendor certified to work together, so Unisys,
>> IBM, HP and Dell and really your only choices. Data Center editions are
>> usually only certifiable for something like this.
>> Then have exacly the same setup for your Test enviroment, and the same
>> again
>> for a development environment. Power, aircon, access control, at least 3
>> of
>> each, at each site.
>> Document everthing, from setup to operations to the finest detail. Have
>> run
>> books, and regularly test the validity of them.
>> Have your architecture reviewed and certified by Microsoft and the
>> Hardware
>> Vendor.
>> Have your application reviewed and certified by Microsoft
>> Have the most restrictive change control in place that, so that you can
>> nearly do nothing.
>> http://www.ftponline.com/wss/2004_11/magazine/features/nruest/default.aspx
>> http://www.microsoft.com/sql/techinfo/administration/2000/availability.asp
>> Super high availability is not a piece of equipment that you buy, it a
>> whole
>> process that everyone has to work towards.
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>>
>> "bijupg@.hotmail.com" wrote:
>> > Hi GUYS,
>> > I am having a very mission critical sql server 2000 database with
>> > active
>> > passive failover cluster an d logshipping with interval of 2 minutes.
>> > what additional disaster recovery techniques i should implement to have
>> > 99.99999 availability and
>> > i can not afford any data loss.
>> > Pls advice.
>> > Rgds
>> > Biju
2012年3月7日星期三
Disadvantage "trunc. log on chkpt."?
Hi NG
In a published db (transactional), anytime
the option "trunc. log on chkpt."( for fast BCP) is active.
I have set
<PublicationDatabaseName>', 'sync with backup', 'true'
<DisributionDatabaseName>', 'sync with backup', 'true'
for full recovery in desaster case.
Is it a problem?
BOL says, if sync with backup = true
then trunc. log on chkpt must be false!
How can I bypass this circumstance?
Stop Logreader and Distritask?
Regards,
Thomas
the same question
for option: 'select into/bulkcopy'
On Mon, 16 Aug 2004 09:16:47 GMT, tohas@.freenet.de (Thomas Hase)
wrote:
>Hi NG
>In a published db (transactional), anytime
>the option "trunc. log on chkpt."( for fast BCP) is active.
>I have set
><PublicationDatabaseName>', 'sync with backup', 'true'
><DisributionDatabaseName>', 'sync with backup', 'true'
>for full recovery in desaster case.
>Is it a problem?
>BOL says, if sync with backup = true
>then trunc. log on chkpt must be false!
>How can I bypass this circumstance?
>Stop Logreader and Distritask?
>Regards,
>Thomas
|||If you have to switch recovery models you are breaking the log chain. You
will have to change your recovery model back to full, backup your databases
(distribution and publication) and restore them on the subscriber with the
keep_replication switch.
Then start shipping the logs again.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Thomas Hase" <tohas@.freenet.de> wrote in message
news:41227e0d.67962859@.news.t-online.de...
> the same question
> for option: 'select into/bulkcopy'
>
> On Mon, 16 Aug 2004 09:16:47 GMT, tohas@.freenet.de (Thomas Hase)
> wrote:
>
In a published db (transactional), anytime
the option "trunc. log on chkpt."( for fast BCP) is active.
I have set
<PublicationDatabaseName>', 'sync with backup', 'true'
<DisributionDatabaseName>', 'sync with backup', 'true'
for full recovery in desaster case.
Is it a problem?
BOL says, if sync with backup = true
then trunc. log on chkpt must be false!
How can I bypass this circumstance?
Stop Logreader and Distritask?
Regards,
Thomas
the same question
for option: 'select into/bulkcopy'
On Mon, 16 Aug 2004 09:16:47 GMT, tohas@.freenet.de (Thomas Hase)
wrote:
>Hi NG
>In a published db (transactional), anytime
>the option "trunc. log on chkpt."( for fast BCP) is active.
>I have set
><PublicationDatabaseName>', 'sync with backup', 'true'
><DisributionDatabaseName>', 'sync with backup', 'true'
>for full recovery in desaster case.
>Is it a problem?
>BOL says, if sync with backup = true
>then trunc. log on chkpt must be false!
>How can I bypass this circumstance?
>Stop Logreader and Distritask?
>Regards,
>Thomas
|||If you have to switch recovery models you are breaking the log chain. You
will have to change your recovery model back to full, backup your databases
(distribution and publication) and restore them on the subscriber with the
keep_replication switch.
Then start shipping the logs again.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Thomas Hase" <tohas@.freenet.de> wrote in message
news:41227e0d.67962859@.news.t-online.de...
> the same question
> for option: 'select into/bulkcopy'
>
> On Mon, 16 Aug 2004 09:16:47 GMT, tohas@.freenet.de (Thomas Hase)
> wrote:
>
Disactory recovery from MS SQL clustering
Hi all,
I have an MS SQL active/passive cluster with 2 nodes of windows 2000 advance
server. One of the node has hardware failure. After I restored win 2k
server from ntbackup, i can't re-join the cluster. Though I can see both
server are up in the cluster administrator, but it fails when fail over
occurs.
Please advise me how to do.
Justin
Here is a webcast that might help:
http://support.microsoft.com/default...b;en-us;822250
Or may this Q:
http://support.microsoft.com/default...b;en-us;822400
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Bill Gate" <iono@.umc.com.hk> wrote in message
news:eOGOkOxbEHA.1408@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> I have an MS SQL active/passive cluster with 2 nodes of windows 2000
advance
> server. One of the node has hardware failure. After I restored win 2k
> server from ntbackup, i can't re-join the cluster. Though I can see both
> server are up in the cluster administrator, but it fails when fail over
> occurs.
> Please advise me how to do.
> Justin
>
|||The information for such scenarios is well documented in "Help and Support Center" for Windows
Here is cut an paste from Help
Scenario 6Single Cluster Node Corruption or Failure
Symptom: The node cannot join the cluster.
If the Event Log indicates that the cluster database on the local node is merely corrupted, you can perform a System State restore on that node to replace the local cluster database. For information, see To
restore the cluster database on a local node. Alternatively, you can copy the latest checkpoint file (CHKxxx.TMP) from the quorum disk to the %systemroot%\Cluster\ directory, rename it as file CLUSDB, and
restart the Cluster service on that node.
If a single node fails in the cluster due to system disk or other hardware failure, follow these steps to rebuild the node and rejoin the cluster:
After verifying that all cluster resource groups have been successfully moved to other nodes, repair or replace the failed hardware. For information, see To move a group to another node and To manage cluster
hardware.
Perform an Automated System Recovery restore on the failed node to rebuild the node. For information, see To restore a damaged cluster node using Automated System Recovery.
If you have other files or application data for that node backed up on on tape or other backup medium, you can restore that now. For information, see To restore files from a file or a tape and Scenario 8 below.
For each cluster group and resource, verify that the newly recovered node appears as a possible owner in Cluster Administrator, then move a resource group to the newly recovered node and verify that the move
is successful. For information, see To test whether group resources can fail over.
Note
If you do not have an Automated System Recovery backup of the node, you can evict that node and add a new node to the cluster. For more information, see To evict a node from the cluster and To add
additional nodes to the cluster.
For more scenarios and options, please review the topic "Backing up and restoring server clusters" in Windows Help.
Or go online to the following link
http://www.microsoft.com/resources/d...r/proddocs/en-
us/SAG_MSCSusing_9.asp
SQL Server specific information is there in SQL Server Books Online. I am cutting and pasting the same for you.
How to recover from failover cluster failure in Scenario 1
http://msdn.microsoft.com/library/de...ering_2uax.asp (online link)
In this scenario, failure is caused by hardware failure in Node 1 of a two-node cluster. This hardware failure could be caused, for example, by the failure of a small computer system interface (SCSI) card or the
operating system.
After Node 1 fails, the Microsoft SQL Server 2000 failover cluster fails over to Node 2.
Run SQL Server Setup and remove Node 1. For more information, see How to remove a failover clustered instance .
Evict Node 1 from Microsoft Cluster Service (MSCS). To evict a node from MSCS, from Node 2, right-click on the node to remove, and then click Evict Node.
Install new hardware to replace the failed hardware in Node 1.
Install the operating system. For more information about which operating system to install and specific instructions on how to do this, see Before Installing Failover Clustering.
Install MSCS and join the existing cluster. For more information, see Before Installing Failover Clustering.
Run the Setup program on Node 2 and add Node 1 back to the failover cluster. For more information, see How to add nodes to an existing virtual server (Setup).
Hope that helps.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
I have an MS SQL active/passive cluster with 2 nodes of windows 2000 advance
server. One of the node has hardware failure. After I restored win 2k
server from ntbackup, i can't re-join the cluster. Though I can see both
server are up in the cluster administrator, but it fails when fail over
occurs.
Please advise me how to do.
Justin
Here is a webcast that might help:
http://support.microsoft.com/default...b;en-us;822250
Or may this Q:
http://support.microsoft.com/default...b;en-us;822400
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Bill Gate" <iono@.umc.com.hk> wrote in message
news:eOGOkOxbEHA.1408@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> I have an MS SQL active/passive cluster with 2 nodes of windows 2000
advance
> server. One of the node has hardware failure. After I restored win 2k
> server from ntbackup, i can't re-join the cluster. Though I can see both
> server are up in the cluster administrator, but it fails when fail over
> occurs.
> Please advise me how to do.
> Justin
>
|||The information for such scenarios is well documented in "Help and Support Center" for Windows
Here is cut an paste from Help
Scenario 6Single Cluster Node Corruption or Failure
Symptom: The node cannot join the cluster.
If the Event Log indicates that the cluster database on the local node is merely corrupted, you can perform a System State restore on that node to replace the local cluster database. For information, see To
restore the cluster database on a local node. Alternatively, you can copy the latest checkpoint file (CHKxxx.TMP) from the quorum disk to the %systemroot%\Cluster\ directory, rename it as file CLUSDB, and
restart the Cluster service on that node.
If a single node fails in the cluster due to system disk or other hardware failure, follow these steps to rebuild the node and rejoin the cluster:
After verifying that all cluster resource groups have been successfully moved to other nodes, repair or replace the failed hardware. For information, see To move a group to another node and To manage cluster
hardware.
Perform an Automated System Recovery restore on the failed node to rebuild the node. For information, see To restore a damaged cluster node using Automated System Recovery.
If you have other files or application data for that node backed up on on tape or other backup medium, you can restore that now. For information, see To restore files from a file or a tape and Scenario 8 below.
For each cluster group and resource, verify that the newly recovered node appears as a possible owner in Cluster Administrator, then move a resource group to the newly recovered node and verify that the move
is successful. For information, see To test whether group resources can fail over.
Note
If you do not have an Automated System Recovery backup of the node, you can evict that node and add a new node to the cluster. For more information, see To evict a node from the cluster and To add
additional nodes to the cluster.
For more scenarios and options, please review the topic "Backing up and restoring server clusters" in Windows Help.
Or go online to the following link
http://www.microsoft.com/resources/d...r/proddocs/en-
us/SAG_MSCSusing_9.asp
SQL Server specific information is there in SQL Server Books Online. I am cutting and pasting the same for you.
How to recover from failover cluster failure in Scenario 1
http://msdn.microsoft.com/library/de...ering_2uax.asp (online link)
In this scenario, failure is caused by hardware failure in Node 1 of a two-node cluster. This hardware failure could be caused, for example, by the failure of a small computer system interface (SCSI) card or the
operating system.
After Node 1 fails, the Microsoft SQL Server 2000 failover cluster fails over to Node 2.
Run SQL Server Setup and remove Node 1. For more information, see How to remove a failover clustered instance .
Evict Node 1 from Microsoft Cluster Service (MSCS). To evict a node from MSCS, from Node 2, right-click on the node to remove, and then click Evict Node.
Install new hardware to replace the failed hardware in Node 1.
Install the operating system. For more information about which operating system to install and specific instructions on how to do this, see Before Installing Failover Clustering.
Install MSCS and join the existing cluster. For more information, see Before Installing Failover Clustering.
Run the Setup program on Node 2 and add Node 1 back to the failover cluster. For more information, see How to add nodes to an existing virtual server (Setup).
Hope that helps.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
2012年2月24日星期五
Disable triggers only for active sessions
Hey,
is it possible to disable all DML triggers for the current session only?
This is for manual data correction sessions where no trigger should be fired but all other user connection still should have active triggers.
Cheers,I don't think you can do this without modifying your trigger. You can use SUSER_NAME() function inside your trigger and if it matches with the login user bypass the execution.
to be specific.
The first line of trigger code will be if SUSER_NAME() = 'Manuel' return|||I can second that, you will have to implement some additional logic to make this possible.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
2012年2月19日星期日
Disable Trigger rules
I had created several Trigger rules in current database and it will be
active on 1st Nov,2005,
Can I disable them now ? and then make them active on that target date '
Thanks a lotThe only way to disable a trigger is to drop it (or comment out the
T-SQL code in it so it does nothing). If I were you I'd script them out
to a file (with SQLEM), drop them (thereby "disabling" them) and then
schedule the SQL script in the file containing all the trigger code to
run via SQLAgent on Nov 1st (thereby "re-enabling" them).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Agnes wrote:
>I had created several Trigger rules in current database and it will be
>active on 1st Nov,2005,
>Can I disable them now ? and then make them active on that target date '
>Thanks a lot
>
>|||Thanks Mike, I try your method , script it out. (however, it seems I must sc
ript the table structure too.).Any Simple method, i can script trigger rule
only , and the drop them all '
Please be kind to provide some sample .. Thanks in advance. (Today is my 4th
day working about Trigger rule)
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> '?:%23B7WU132FHA.279
6@.tk2msftngp13.phx.gbl...
The only way to disable a trigger is to drop it (or comment out the T-SQL co
de in it so it does nothing). If I were you I'd script them out to a file (
with SQLEM), drop them (thereby "disabling" them) and then schedule the SQL
script in the file containing all the trigger code to run via SQLAgent on No
v 1st (thereby "re-enabling" them).
mike hodgson
blog: http://sqlnerd.blogspot.com
Agnes wrote:
I had created several Trigger rules in current database and it will be
active on 1st Nov,2005,
Can I disable them now ? and then make them active on that target date '
Thanks a lot|||Hey you have soemthing called
ALTER TABLE ENABLE/DISABLE TRIGGER Read in BOL
If you want to do it for all tables, use
sp_Msforeachtable "ALTER TABLE '?' DISABLE TRIGGER"
Regards
R.D
--Knowledge gets doubled when shared
"Agnes" wrote:
> Thanks Mike, I try your method , script it out. (however, it seems I must
script the table structure too.).Any Simple method, i can script trigger rul
e only , and the drop them all '
> Please be kind to provide some sample .. Thanks in advance. (Today is my 4
th day working about Trigger rule)
> "Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> '?:%23B7WU132FHA
.2796@.tk2msftngp13.phx.gbl...
> The only way to disable a trigger is to drop it (or comment out the T-SQL code i
n it so it does nothing). If I were you I'd script them out to a file (with SQLEM),
drop them (thereby "disabling" them) and then schedule the SQL script in the file c
ont
aining all the trigger code to run via SQLAgent on Nov 1st (thereby "re-enabling" them).[co
lor=darkred]
> --
> mike hodgson
> blog: http://sqlnerd.blogspot.com
>
> Agnes wrote:
> I had created several Trigger rules in current database and it will be
> active on 1st Nov,2005,
> Can I disable them now ? and then make them active on that target date '
> Thanks a lot
>
>[/color]|||> The only way to disable a trigger is to drop it (or comment out the
> T-SQL code in it so it does nothing).
This is simply not true. Disabling or enabling a trigger is done through the
ALTER TABLE statement.
- to disable a trigger:
ALTER TABLE <table>
DISABLE TRIGGER <trigger>
- to enable a trigger:
ALTER TABLE <table>
ENABLE TRIGGER <trigger>
More here:
http://msdn.microsoft.com/library/d...br />
3ied.asp
ML|||Well you learn something new every day (I don't claim to know
everything). Thanks for the tip - that one's filed away in permanent
cache now. You know, over 10 years working with MSSQL and I'd never
noticed that clause in the ALTER TABLE statement.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
R.D wrote:
>Hey you have soemthing called
>ALTER TABLE ENABLE/DISABLE TRIGGER Read in BOL
>If you want to do it for all tables, use
>sp_Msforeachtable "ALTER TABLE '?' DISABLE TRIGGER"
>
>|||I myself was reluctant to use these two methods at first since QA does not
recognize ENABLE and DISABLE as reserved keywords. :)
ML|||Maybe my brain's just not wired correctly, but wouldn't it make more
sense to have the ENABLED/DISABLED clause as part of the ALTER TRIGGER
statement rather than the ALTER TABLE statement? Something like "ALTER
TRIGGER MyTrig ON me.MyTable DISABLE"
*mike hodgson*
blog: http://sqlnerd.blogspot.com
ML wrote:
>I myself was reluctant to use these two methods at first since QA does not
>recognize ENABLE and DISABLE as reserved keywords. :)
>
>ML
>|||Quite the opposite! Wouldn't it make much more sense if triggers were added
to the objects:
alter table / view <name>
add trigger <trigger_name>
:)
After all - each trigger can only belong to a single table/view...
ML|||True, a trigger can only belong to a single table/view. But ALTER TABLE
is what you use to change the behaviour of an existing trigger (trigger
code, encryption, etc.), so it makes more sense to me that to change an
"attribute" of a trigger, which I would consider its "enabled/disabled"
status to be, you'd use ALTER TRIGGER.
Moot point anyway - purely a hypothetical, but I think the way they've
gone with T-SQL in SQL 2005 is better (with DISABLE TRIGGER being a DDL
statement all of its own).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
ML wrote:
>Quite the opposite! Wouldn't it make much more sense if triggers were added
>to the objects:
>alter table / view <name>
> add trigger <trigger_name>
>:)
>After all - each trigger can only belong to a single table/view...
>
>ML
>
active on 1st Nov,2005,
Can I disable them now ? and then make them active on that target date '
Thanks a lotThe only way to disable a trigger is to drop it (or comment out the
T-SQL code in it so it does nothing). If I were you I'd script them out
to a file (with SQLEM), drop them (thereby "disabling" them) and then
schedule the SQL script in the file containing all the trigger code to
run via SQLAgent on Nov 1st (thereby "re-enabling" them).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Agnes wrote:
>I had created several Trigger rules in current database and it will be
>active on 1st Nov,2005,
>Can I disable them now ? and then make them active on that target date '
>Thanks a lot
>
>|||Thanks Mike, I try your method , script it out. (however, it seems I must sc
ript the table structure too.).Any Simple method, i can script trigger rule
only , and the drop them all '
Please be kind to provide some sample .. Thanks in advance. (Today is my 4th
day working about Trigger rule)
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> '?:%23B7WU132FHA.279
6@.tk2msftngp13.phx.gbl...
The only way to disable a trigger is to drop it (or comment out the T-SQL co
de in it so it does nothing). If I were you I'd script them out to a file (
with SQLEM), drop them (thereby "disabling" them) and then schedule the SQL
script in the file containing all the trigger code to run via SQLAgent on No
v 1st (thereby "re-enabling" them).
mike hodgson
blog: http://sqlnerd.blogspot.com
Agnes wrote:
I had created several Trigger rules in current database and it will be
active on 1st Nov,2005,
Can I disable them now ? and then make them active on that target date '
Thanks a lot|||Hey you have soemthing called
ALTER TABLE ENABLE/DISABLE TRIGGER Read in BOL
If you want to do it for all tables, use
sp_Msforeachtable "ALTER TABLE '?' DISABLE TRIGGER"
Regards
R.D
--Knowledge gets doubled when shared
"Agnes" wrote:
> Thanks Mike, I try your method , script it out. (however, it seems I must
script the table structure too.).Any Simple method, i can script trigger rul
e only , and the drop them all '
> Please be kind to provide some sample .. Thanks in advance. (Today is my 4
th day working about Trigger rule)
> "Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> '?:%23B7WU132FHA
.2796@.tk2msftngp13.phx.gbl...
> The only way to disable a trigger is to drop it (or comment out the T-SQL code i
n it so it does nothing). If I were you I'd script them out to a file (with SQLEM),
drop them (thereby "disabling" them) and then schedule the SQL script in the file c
ont
aining all the trigger code to run via SQLAgent on Nov 1st (thereby "re-enabling" them).[co
lor=darkred]
> --
> mike hodgson
> blog: http://sqlnerd.blogspot.com
>
> Agnes wrote:
> I had created several Trigger rules in current database and it will be
> active on 1st Nov,2005,
> Can I disable them now ? and then make them active on that target date '
> Thanks a lot
>
>[/color]|||> The only way to disable a trigger is to drop it (or comment out the
> T-SQL code in it so it does nothing).
This is simply not true. Disabling or enabling a trigger is done through the
ALTER TABLE statement.
- to disable a trigger:
ALTER TABLE <table>
DISABLE TRIGGER <trigger>
- to enable a trigger:
ALTER TABLE <table>
ENABLE TRIGGER <trigger>
More here:
http://msdn.microsoft.com/library/d...br />
3ied.asp
ML|||Well you learn something new every day (I don't claim to know
everything). Thanks for the tip - that one's filed away in permanent
cache now. You know, over 10 years working with MSSQL and I'd never
noticed that clause in the ALTER TABLE statement.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
R.D wrote:
>Hey you have soemthing called
>ALTER TABLE ENABLE/DISABLE TRIGGER Read in BOL
>If you want to do it for all tables, use
>sp_Msforeachtable "ALTER TABLE '?' DISABLE TRIGGER"
>
>|||I myself was reluctant to use these two methods at first since QA does not
recognize ENABLE and DISABLE as reserved keywords. :)
ML|||Maybe my brain's just not wired correctly, but wouldn't it make more
sense to have the ENABLED/DISABLED clause as part of the ALTER TRIGGER
statement rather than the ALTER TABLE statement? Something like "ALTER
TRIGGER MyTrig ON me.MyTable DISABLE"
*mike hodgson*
blog: http://sqlnerd.blogspot.com
ML wrote:
>I myself was reluctant to use these two methods at first since QA does not
>recognize ENABLE and DISABLE as reserved keywords. :)
>
>ML
>|||Quite the opposite! Wouldn't it make much more sense if triggers were added
to the objects:
alter table / view <name>
add trigger <trigger_name>
:)
After all - each trigger can only belong to a single table/view...
ML|||True, a trigger can only belong to a single table/view. But ALTER TABLE
is what you use to change the behaviour of an existing trigger (trigger
code, encryption, etc.), so it makes more sense to me that to change an
"attribute" of a trigger, which I would consider its "enabled/disabled"
status to be, you'd use ALTER TRIGGER.
Moot point anyway - purely a hypothetical, but I think the way they've
gone with T-SQL in SQL 2005 is better (with DISABLE TRIGGER being a DDL
statement all of its own).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
ML wrote:
>Quite the opposite! Wouldn't it make much more sense if triggers were added
>to the objects:
>alter table / view <name>
> add trigger <trigger_name>
>:)
>After all - each trigger can only belong to a single table/view...
>
>ML
>
2012年2月14日星期二
Disable Fulltext
I have a server that has SQL Server 2000 with SP3A with
Windows 2000 Advanced Server with an Active/Active. We
are presently not using the SQL Server 2000 Fulltext.
How can I disable the SQL Server 2000 Fulltext service?
How could stop the service and disable the service to
restart when rebooted. How can I disable the SQL Server
2000 Fulltext service from the cluster?
Thanks,
Mike
You can manually take the resource offline, then it won't come back online
at the next restart or failover. You can also set the resource to not
affect the group in the resource properties.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Windows 2000 Advanced Server with an Active/Active. We
are presently not using the SQL Server 2000 Fulltext.
How can I disable the SQL Server 2000 Fulltext service?
How could stop the service and disable the service to
restart when rebooted. How can I disable the SQL Server
2000 Fulltext service from the cluster?
Thanks,
Mike
You can manually take the resource offline, then it won't come back online
at the next restart or failover. You can also set the resource to not
affect the group in the resource properties.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
订阅：
博文 (Atom)