Active / passive in SQL 7

A friend of mine runs QL 7 Stanad on a Compaq Cluster. I want him to
upgrade to SQL 2005. I want to know how he can do the below with SQL
7?
His message:
That feature, available with the SQL Server7 Enterprise, would allow
my passive node to startup the database without any DBA involvement.
Right now my cluster simply fails over, but SQL7 does not
automatically activate on the passive node once the shared disk is
available. This is because the passive node only checks for the
presence of the disk drive at bootup. Hence, it does not start the
service when the disk is available after a fail-over.
At the end of the day, I would be running the same database in the
same manner, with no licensing implications because I have not changed
the availability or seat count; I would merely have the second node
fire up after it detects the availability of the shared disk where the
program and data files reside.
Thanks
Buy new hardware and migrate! How old is the equipment running SQL 7?
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"David Sherman" <dshermin@.ameritech.net> wrote in message
news:e7jmu1hk54lfb1i126lrs35dknv2dtk12r@.4ax.com...
>A friend of mine runs QL 7 Stanad on a Compaq Cluster. I want him to
> upgrade to SQL 2005. I want to know how he can do the below with SQL
> 7?
> His message:
>
> That feature, available with the SQL Server7 Enterprise, would allow
> my passive node to startup the database without any DBA involvement.
> Right now my cluster simply fails over, but SQL7 does not
> automatically activate on the passive node once the shared disk is
> available. This is because the passive node only checks for the
> presence of the disk drive at bootup. Hence, it does not start the
> service when the disk is available after a fail-over.
> At the end of the day, I would be running the same database in the
> same manner, with no licensing implications because I have not changed
> the availability or seat count; I would merely have the second node
> fire up after it detects the availability of the shared disk where the
> program and data files reside.
> Thanks
|||I have tried to get him to buy new equipment. The equipment is about 6
years old.
On Thu, 9 Feb 2006 09:20:26 -0600, "Rodney R. Fournier [MVP]"
<rod@.die.spam.die.nw-america.com> wrote:

>Buy new hardware and migrate! How old is the equipment running SQL 7?
>Cheers,
>Rodney R. Fournier
>MVP - Windows Server - Clustering
>http://www.nw-america.com - Clustering Website
>http://www.msmvps.com/clustering - Blog
>http://www.clusterhelp.com - Cluster Training
>ClusterHelp.com is a Microsoft Certified Gold Partner
>
>"David Sherman" <dshermin@.ameritech.net> wrote in message
>news:e7jmu1hk54lfb1i126lrs35dknv2dtk12r@.4ax.com.. .
>
|||The first thing you have to check is whether the hardware is even supported
for SQL Server 2005. Secondly, unless Enterprise Edition is installed, you
aren't going to get SQL Server 2005 into a failover cluster.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"David Sherman" <dshermin@.ameritech.net> wrote in message
news:e7jmu1hk54lfb1i126lrs35dknv2dtk12r@.4ax.com...
>A friend of mine runs QL 7 Stanad on a Compaq Cluster. I want him to
> upgrade to SQL 2005. I want to know how he can do the below with SQL
> 7?
> His message:
>
> That feature, available with the SQL Server7 Enterprise, would allow
> my passive node to startup the database without any DBA involvement.
> Right now my cluster simply fails over, but SQL7 does not
> automatically activate on the passive node once the shared disk is
> available. This is because the passive node only checks for the
> presence of the disk drive at bootup. Hence, it does not start the
> service when the disk is available after a fail-over.
> At the end of the day, I would be running the same database in the
> same manner, with no licensing implications because I have not changed
> the availability or seat count; I would merely have the second node
> fire up after it detects the availability of the shared disk where the
> program and data files reside.
> Thanks
|||Thanks for the infomation.
Is there a way to write a script that monitors the active node and
when it dies (1) notifies the DBA of the failure and (2) starts the
passive node. or (3) is there a package that will do this?
thanks
On Thu, 9 Feb 2006 10:29:31 -0600, "Michael Hotek"
<mike@.solidqualitylearning.com> wrote:

>The first thing you have to check is whether the hardware is even supported
>for SQL Server 2005. Secondly, unless Enterprise Edition is installed, you
>aren't going to get SQL Server 2005 into a failover cluster.
>--
>Mike
>http://www.solidqualitylearning.com
>Disclaimer: This communication is an original work and represents my sole
>views on the subject. It does not represent the views of any other person
>or entity either by inference or direct reference.
>
>"David Sherman" <dshermin@.ameritech.net> wrote in message
>news:e7jmu1hk54lfb1i126lrs35dknv2dtk12r@.4ax.com.. .
>
|||The package is called "Failover Clustering" and is a built-in feature of SQL
2000 Enterprise Edition and SQL 2005 Enterprise and Standard Editions.
Windows 2000/2003 Enterprise Edition is also required.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Sherman" <dshermin@.ameritech.net> wrote in message
news:nvtmu11ik9jpnf2i7nlrhf6ppq0f64nqbd@.4ax.com...
> Thanks for the infomation.
> Is there a way to write a script that monitors the active node and
> when it dies (1) notifies the DBA of the failure and (2) starts the
> passive node. or (3) is there a package that will do this?
> thanks
>
> On Thu, 9 Feb 2006 10:29:31 -0600, "Michael Hotek"
> <mike@.solidqualitylearning.com> wrote:
>
|||Thanks for the update.
I know he has 2005 Standard. He needs to get the CALS that he needs.
thanks again.
On Thu, 9 Feb 2006 14:01:04 -0500, "Geoff N. Hiten"
<SQLCraftsman@.gmail.com> wrote:

>The package is called "Failover Clustering" and is a built-in feature of SQL
>2000 Enterprise Edition and SQL 2005 Enterprise and Standard Editions.
>Windows 2000/2003 Enterprise Edition is also required.
|||According to this link:
http://www.databasejournal.com/featu...le.php/3444181
Failover clustering has been supported since SQL Server 7.0 so it is
not surprising that its latest implementation is a combination of
already familiar (and stable) technology with a number of useful ...
How does one use Failover Clustering withe Windows 2000 Advanced
server and SQL 7?
thanks again.
On Thu, 9 Feb 2006 14:01:04 -0500, "Geoff N. Hiten"
<SQLCraftsman@.gmail.com> wrote:

>The package is called "Failover Clustering" and is a built-in feature of SQL
>2000 Enterprise Edition and SQL 2005 Enterprise and Standard Editions.
>Windows 2000/2003 Enterprise Edition is also required.