This is not an issue. The disks have to be configured inside Windows and
visible at a Windows level before they can even be added to the cluster.
Clustering doesn't write any signatures to the disks that force them to
behave differently. If you want to verify this, just highlight a disk
resource in Cluster Admin and hit the delete key. The reason that it
instantly corrupts the dsk is because all nodes in the cluster immediately
grab the disk that is no longer controlled by the cluster service.
Clustering controls the disk visibility, because it integrates directly into
the OS level and at the disk I/O level controls the disk behavior, not
because it writes specialized signatures to the disk.
You can in fact stop the cluster service anytime you want to. You can then
go to the Service Control applet and start the SQL Server itself manually.
If you look in disk administrator, you see exactly what you describe, but
you can still read and write anything you want to on the disks from the
machine that last had ownership of the disk resources, even with the cluster
service offline.
If you remove the cluster (unconfigure it), the disks become immediately
accessible to any machine that they were configured into when you hooked
them up. In this case, it is exactly one machine (a single node cluster).
So, when you take clustering out, the disks that were previously controlled
by the cluster are now nothing more than regular disks which can be read and
written to as much as you want without requiring any reconfig of the disks.
This I know, because I have done this many times.
The only part I have not done is to remove the cluster when I had a failover
cluster instance installed and try to have a fully working SQL Server on the
machine once clustering was removed. I very strongly doubt this would work,
mainly because of the registry settings related to the instance.
--
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.
[quoted text, click to view] "Geoff N. Hiten" <SQLCraftsman@gmail.com> wrote in message
news:OKHkV2qJGHA.648@TK2MSFTNGP14.phx.gbl...
>I still argue that the disks won't mount without the clustering service.
>Clustering mangles the signature on the disk so it appears as a foreign
>volume to Windows. The clustering service brings the disks online.
>Without the cluster service working, the disks will remain inaccessable to
>the Windows OS. They will show up in disk administrator, but they won't
>appear as Windows disks.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
>
>
> "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
> message news:uEH5gTnJGHA.668@TK2MSFTNGP11.phx.gbl...
>> The disks would work, I would worry about SQL. Funny the clustering guys
>> worries about SQL, the SQL guy worries about clustering...
>>
>> Cheers,
>>
>> Rod
>>
>> MVP - Windows Server - Clustering
>>
http://www.nw-america.com - Clustering Website
>>
http://www.msmvps.com/clustering - Blog
>>
http://www.clusterhelp.com - Cluster Training
>>
>>
>> "Geoff N. Hiten" <SQLCraftsman@gmail.com> wrote in message
>> news:eGgkR4mJGHA.2912@tk2msftngp13.phx.gbl...
>>>I doubt that would work. The data disks and virtual IP address are under
>>>the control of the cluster service. Without the cluster, the devices
>>>will stay offline. You can either rebuild SQL as a stand-alone system or
>>>leave it with a single-node cluster. There is no harm in leaving it as a
>>>clustered instance with only one node.
>>>
>>> --
>>> Geoff N. Hiten
>>> Senior Database Administrator
>>> Microsoft SQL Server MVP
>>>
>>>
>>>
>>>
>>> "Aaron Elliott" <AaronElliott@discussions.microsoft.com> wrote in
>>> message news:1FD7AF10-F30F-4706-9846-8CA76E506E82@microsoft.com...
>>>>
>>>> Hi All,
>>>>
>>>> We have a single node cluster (formally 2 node) which is running SQL
>>>> 2000.
>>>> My question is this: wanting to remove the clustering component
>>>> entirely from
>>>> the picture, can I simply disable the cluster service and start SQL as
>>>> normal? We have no need to any clusting on this server any more.
>>>>
>>>> If I do this, I gather it will still be known on the network as the SQL
>>>> Virtual Server name - which is different to the Windows server name.
>>>>
>>>> Thanks!
>>>>
>>>> Aaron
>>>
>>>
>>
>>
>
>