| Title: | WinNT-Clusters |
| Notice: | Info directories moved to DECWET::SHARE1$:[NT_CLSTR] |
| Moderator: | DECWET::CAPPELLOF |
| Created: | Thu Oct 19 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 863 |
| Total number of notes: | 3478 |
I just came from a brief update on 1.1 Clusters (and sp2).
I appreciate the efforts being made by engineering to make
the implementation of SQL Server databases much easier than in
the past.
I do have a question that has been an issue since the inception--
When we have a shared database that has extended the db device
or the log... how is that change in the master db communicated
to the secondary master db so they match on failover?
Thank you.
Mary Jo
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 602.1 | A three step process | DECWET::CAPPELLOF | My other brain is a polymer | Fri Feb 07 1997 16:35 | 17 |
There is a procedure documented in the Cluster Administrator's guide
chapter 3 for how to extend or shrink a SQL database that resides on a
shared cluster disk. Basically, the steps look like this:
Unenroll the database from fallback support (leaves it online on
the primary server.)
Extend or shrink the database using SQL Enterprise Manager or some
other tool.
Re-enroll the database for fallback support. This last step
updates the SQL spt_fallback_ tables in the master databases on
both nodes.
Note that this must be done while both nodes are up! The NT Cluster
software doesn't log changes that need to be made to the "other" node's
master SQL database if the other node is down.
| |||||
| 602.2 | CSC32::HOEPNER | A closed mouth gathers no feet | Fri Feb 07 1997 20:43 | 3 | |
Thanks for the update.
| |||||