Showing posts with label w2k. Show all posts
Showing posts with label w2k. Show all posts

Sunday, March 25, 2012

Computerrename

Hello,
I have a small question. We have an cluster (W2K) running with an
SQL2000 and an IIS on it. Is it possible to rename the notes of the
cluster without any problems?
Greetings
Stefan
Your best method for renaming cluster nodes is to fail every thing across to
one of the nodes. Then remove the node with no resources from the cluster and
then rename it. After it has been renamed join the node back to the cluster
move the resources across to the renamed node and repeat the process with the
second node.
Thanks
Mark
"Stefan Oswald" wrote:

> Hello,
> I have a small question. We have an cluster (W2K) running with an
> SQL2000 and an IIS on it. Is it possible to rename the notes of the
> cluster without any problems?
> Greetings
> Stefan
>
|||Mark, have you tried this yet? I am not aware of any supported method of
renaming a SQL server (clustered or not).
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
"Mark Bradley" <MarkBradley@.discussions.microsoft.com> wrote in message
news:8C1A89C9-16CE-4467-A770-721197B4A7EF@.microsoft.com...[vbcol=seagreen]
> Your best method for renaming cluster nodes is to fail every thing across
> to
> one of the nodes. Then remove the node with no resources from the cluster
> and
> then rename it. After it has been renamed join the node back to the
> cluster
> move the resources across to the renamed node and repeat the process with
> the
> second node.
> Thanks
> Mark
>
> "Stefan Oswald" wrote:
|||He left off the little detail of uninstalling and reinstalling SQL on the
newly renamed node.
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:eTfZnls5FHA.3636@.TK2MSFTNGP09.phx.gbl...
> Mark, have you tried this yet? I am not aware of any supported method of
> renaming a SQL server (clustered or not).
> 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
>
> "Mark Bradley" <MarkBradley@.discussions.microsoft.com> wrote in message
> news:8C1A89C9-16CE-4467-A770-721197B4A7EF@.microsoft.com...
>
|||Ok, in that case, his method will work nicely
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:eJJfPBt5FHA.1864@.TK2MSFTNGP12.phx.gbl...
> He left off the little detail of uninstalling and reinstalling SQL on the
> newly renamed node.
> --
> 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:eTfZnls5FHA.3636@.TK2MSFTNGP09.phx.gbl...
>
|||In this case it looked like it was not the instance being renamed only the
nodes name in which case the SQL instance would remain unchanged. Exactley
the same as if you added a new node to a cluster.
Your correct that you have to reinstall to rename the instance but it is
easier and safer to add a new virtual server instance and migrate the data.
As for standalone SQL you can rename it but it can cause problems with any
code using specified name.
Example in books online is incorrect correct article below
http://support.microsoft.com/default...b;en-us;303774
Cheers
Mark
"Rodney R. Fournier [MVP]" wrote:

> Ok, in that case, his method will work nicely
> 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:eJJfPBt5FHA.1864@.TK2MSFTNGP12.phx.gbl...
>
>

Sunday, February 19, 2012

Completely Removing SQL Server 2005 Express

I've recently tried to load SQL Server 2005 Express onto the main server that services our small company of 10 people. The server is a W2K Server, and acts as our domain controller. I've had NUMEROUS problems trying to get SQL Server 2005 Express to work on this system - so much so that I've given up trying. However, in attempting to uninstall this, I've now encountered even bigger issues. It seems that the uninstaller leaves files behind (such as VSS Writer, Set up Files) that then will not uninstall themselves. So, being the novice I am, I tried re-installing SQL Server Express as a whole, removing the above files, then uninstalling SQL Server Express "proper." Well, that didn't work either - I got the subordinate stuff to come off, but now the main files won't remove - nor can I reinstall the whole thing any more.

This is an absolute mess - and I need help getting out of it. Can anyone direct me to help on how to SAFELY remove the ENTIRE instance of SQL Server 2005 Express so that nothing else is interrupted/harmed? Any sound advice at this point is most appreciated.

I ve got the same Problem here. Ive installed the Beta of Visual Studie - even after de-installation it was not possible to install Sql Server Developer edition.
I think it is something wrong in registry...|||Not sure about uninstalling, but I think I saw a blurb somewhere on the books online stating you shouldn't install SQL 2005 on a domain controller...|||

SQLWriter and Support files (amongst other 'leftovers') should uninstall just fine after SQL is gone. They may pop up a message saying that removing them may cause other dependent applications to fail. But if you have already removed all instances of SQL Server 2005, you should be fine.

In the situation where you removed them while SQL Express was already on the box, I would suggest installing Express again (to let the installer put back what you deleted), then uninstalling Express, then uninstalling the leftovers.

If that fails, as a last resort you can use the Windows Installer clean up tool. However this may leave some services behind. I definitely recommend

http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe