 | |
Please help with Missing Management Studio in second node.
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Please help with Missing Management Studio in second node. -
12-18-2007
, 12:36 PM
#2
| |||
| |||
|
|
Hello, everyone. I installed a 2-node SQL 2005 Standard Edition with SP2 cluster (active/passive). I realized that the Management Studio was not installed on the 2nd node. How do I fix this issue without breaking my cluster in production mode already? This is very critical for me to get it right in one shot. Please advise. P.S: I can't believe MS SQL server team did not catch this in their QA. Additionally, I had other issue during the SQL cluster forcing me to redo the installation from scratch several times. SQL 2000 was more "stable" than 2005? I was hoping that SQL 2005 much much better off than 2000 with the big investment spent on it and touting as the best one ever .................. |
#3
| |||
| |||
|
|
Don't panic. What you see is by design. The SQL installer only pushes cluster-aware components to all cluster nodes. You can simply run the installer on the console of the second node. Select "Workstation Components" and let it run. Make sure and apply any Service Packs and Hotfixes to the second node. The installer is smart enough to only update the components that it needs to and will leave the database engine component alone. Note that SSMS is not the only component that does not install Cluster-wide. SSIS is also not on your second node unless you installed it manually. I will agree the installation process is more complex for SQL 20005 than for SQL 2000, but if you do all the preparation work correctly, a cluster install should go very smoothly. Fortunately, there is a new installer for SQL 2008 that looks a LOT better. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP "Windows W2K3 User" <WindowsW2K3User (AT) discussions (DOT) microsoft.com> wrote in message news:E1B34CC2-6F42-4E55-A084-6B89AF1E1927 (AT) microsoft (DOT) com... Hello, everyone. I installed a 2-node SQL 2005 Standard Edition with SP2 cluster (active/passive). I realized that the Management Studio was not installed on the 2nd node. How do I fix this issue without breaking my cluster in production mode already? This is very critical for me to get it right in one shot. Please advise. P.S: I can't believe MS SQL server team did not catch this in their QA. Additionally, I had other issue during the SQL cluster forcing me to redo the installation from scratch several times. SQL 2000 was more "stable" than 2005? I was hoping that SQL 2005 much much better off than 2000 with the big investment spent on it and touting as the best one ever .................. |
#4
| |||
| |||
|
|
Thanks, Geoff. So the Management Studio is not cluster-aware. I always do custom installs (selecting only needed components) I will give it a test try. "Geoff N. Hiten" wrote: Don't panic. What you see is by design. The SQL installer only pushes cluster-aware components to all cluster nodes. You can simply run the installer on the console of the second node. Select "Workstation Components" and let it run. Make sure and apply any Service Packs and Hotfixes to the second node. The installer is smart enough to only update the components that it needs to and will leave the database engine component alone. Note that SSMS is not the only component that does not install Cluster-wide. SSIS is also not on your second node unless you installed it manually. I will agree the installation process is more complex for SQL 20005 than for SQL 2000, but if you do all the preparation work correctly, a cluster install should go very smoothly. Fortunately, there is a new installer for SQL 2008 that looks a LOT better. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP "Windows W2K3 User" <WindowsW2K3User (AT) discussions (DOT) microsoft.com> wrote in message news:E1B34CC2-6F42-4E55-A084-6B89AF1E1927 (AT) microsoft (DOT) com... Hello, everyone. I installed a 2-node SQL 2005 Standard Edition with SP2 cluster (active/passive). I realized that the Management Studio was not installed on the 2nd node. How do I fix this issue without breaking my cluster in production mode already? This is very critical for me to get it right in one shot. Please advise. P.S: I can't believe MS SQL server team did not catch this in their QA. Additionally, I had other issue during the SQL cluster forcing me to redo the installation from scratch several times. SQL 2000 was more "stable" than 2005? I was hoping that SQL 2005 much much better off than 2000 with the big investment spent on it and touting as the best one ever .................. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.