Failover test case

#31

I too am looking to test a 2 node SQL cluster. I am new to SQL as well.
I've built the cluster and am ready to test. I realize that when node 1 goes
down, the current SQL connection will drop, but I need to test being able to
connect again, add something to the DB, fail the second node, connect again,
make sure the records have been added, etc. Can someone offer any good ways
to test this? I need to migrate to this cluster in 9 days and need to get it
properly tested.

Thanks so much for any input.

Regards,

Matthew White

"Linchi Shea" wrote:

Quote:

In addition to what Jason said, if it's a strict T-SQL script, it'll just
stop where the node crashes. For the failover to be 'transparent' to the
client, the client must have error handling logic to re-establish the
connection and re-submit the query/transaction that is aborted. Also, as is
the case with a restart, any in-flight transaction (i.e. uncommitted
transaction) is lost and will be rolled back when the instance starts up on
the other node.

Linchi

"jinshuang" wrote:

I am new both for cluster and SQL, and I have built a new two nodes SQL
cluster. For testing failover, I am planing to write a long sql script and
have a client excute and write data in. During the writing, I am going to
take off network or power from node 1. can I expect the script would finish
properly since SQL failover to node 2?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Failover test case

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

RE: Failover test case - 02-14-2008 , 09:25 AM