Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dewacorp.alliances
452 Posts |
 Posted - 2006-10-03 : 04:39:50
|
| Hi thereI am trying to understand the basic concept of clustering. We have an Active/Passive on our environment. We would like to do the maintenance and for test it. We do the passive node first and have a test and then failed to and do the same thing for the other node and failover again to back to normal.In relation to when failover kick and at the same time there is a job/activies on the database (inserting/updating/deleting), is the query pending to process and commit later on when the the other node is taking over? Or the query is terminated straight away?Is the same principal let say if you have a single box and you shut down the server while there a serious activies on the database (inserting/updating/deleting) ... will it pending and process later on or the query is terminated straight away?Normally, when we shut down the node/box ... we only look at the job and wait till finish which sometimes is painfull cause could be running few hours.Need to clarify on this. Thanks |
|
|
Westley
Posting Yak Master
229 Posts |
Posted - 2006-10-03 : 06:28:47
|
| Nope, as far as I understand, when you shutdown or restart SQL, anything that is happening in the middle (any insert, update / delete), will rollback unless it already got committed, but I think your question will be right in the middle when its not committed yet? then its NO, it will rollback.Same goes to failover, as its consider to be a restart, so NO it will rollback.Error message will be given out to the client (if that is what you worry about) :) |
 |
|
|
|
|
|
SQL W2K Clustering