December 18, 2008 at 2:28 am
Hi all,
I was wondering if anyone can tell me how to uninstall MSSQL management studio in MSSQL 2005 as well as in MSSQL 2008?
Thanks indeed
Niyala
December 18, 2008 at 3:08 am
Start --> Control Panel --> Add or Remove Programs --> Microsft SQL Server 2005 --> Remove
December 18, 2008 at 3:12 am
Hi
Thanks for your message, but I did not want to uninstall SQL 2005, instead only the management studio. I did not see the management studio in the list of programmes to uninstall or change.
Regards
Niyala
December 18, 2008 at 4:13 am
Hi Niyala,
Within add/remove programs if you choose 'Microsoft SQL Server 2005' and click remove you will be asked what you want to remove... Integration Services, Workstation Components etc etc. Simply choose Workstation Components to uninstall Management Studio.
Although it gives you the impression that everything will be removed you do get a choice!
May be the same for 2008 but haven't installed it yet so don't know.
Cheers,
Mark
December 18, 2008 at 4:16 am
Hi Mark,
Thanks for your hint. I will give it a go and try. Is it the same in SQL server 2008?
Cheers
Niyala
December 18, 2008 at 4:31 am
Hi Niyala,
Not sure about 2008 it could well be the same.
FYI - It's the same process for removing named instances from a server. If your not sure you should always try this within a dev environment...
Mark
December 18, 2008 at 4:42 am
Thanks Mark.
I tried the the management studio from sql server 2008. There is an option to remove shared features. Shared components, I suppose, include configuration tools as well. I will try on a test machine. My purpose is to avoid any chance of using ssms by operating system admins.
Cheers
Niyala
December 18, 2008 at 4:49 am
Niyala (12/18/2008)
My purpose is to avoid any chance of using ssms by operating system admins.
Don't forget that you should also remove the builtin\administrators security group! Otherwise windows admins who know a bit of sql could use other means such as osql to login.
Mark
December 18, 2008 at 4:59 am
Hi Mark,
Thanks indeed. Builtin\admins are not included by default in SQL server 2008. Isn't enough to disable this group in sql server 2005 instead of completely deleting?
Regards
Niyala
December 18, 2008 at 5:13 am
Niyala (12/18/2008)
Isn't enough to disable this group in sql server 2005 instead of completely deleting?Niyala
Disabled accounts can always be re-enabled, however it's a little bit more involved to recreate the builtin\administrators account. At the end of the day it's down to works best for your environment.
Mark
December 18, 2008 at 5:18 am
Hi Mark,
I myself am a member of builtin\admin group. Well how does it affect my login if I created one (a separate one xyz) for myself first with admin right and then delete the builtin one?
Thanks
Niyala
December 18, 2008 at 6:17 am
Niyala (12/18/2008)
Hi Mark,I myself am a member of builtin\admin group. Well how does it affect my login if I created one (a separate one xyz) for myself first with admin right and then delete the builtin one?
Niyala
Hi Niyala,
Good question! You shouldn't just remove the builtin\admin account without first knowing the potential impact it might have on your system/s. This topic has been discussed many times within SSC and other forums. A simple google search will highlight these.
Check out...
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=97558
http://www.sqlservercentral.com/Forums/Topic153613-202-1.aspx
To name just a few...
To answer your question, it's hard to say what impact it might have without first knowing what the builtin\admin account has permissions to/what ownership it has etc etc (see first url). If in any doubt DO NOT remove the account. Do some research first and decide the best course of action, if need be come back to SSC and ask further questions.
December 18, 2008 at 9:25 am
Many thanks for your useful answers. I'll have a look at those links. Thanks also for offering further help in case needed.
Cheers
Niyala
December 18, 2008 at 9:28 am
No Problem ...
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply