|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
No management StudioI installed SQL 2005 Developer on Win2003 quite a while ago in conjunction
with Sharepoint - - I didn't touch it for a long time, but since my other computer with SQL on it died, I thought I'd spin it up and do some work on it - - well, I saw the Configuration tools in the Program list, but no management studio Why would this happen and how can I get it back? > Why would this happen Usually because you didn't select Workstation Components during setup.> how can I get it back? Run setup again.Thanks, but I only wish it were that simple - - I went back through the
setup and chose my preferences, including WS Components and it told me that nothing was going to happen because I had no effective change to the existing setup Show quoteHide quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:C64B4083.2CFF2%ten.xoc@dnartreb.noraa... >> Why would this happen > > Usually because you didn't select Workstation Components during setup. > >> how can I get it back? > > Run setup again. > Did you search your machine for SqlWb.exe ?
On 6/2/09 8:59 PM, in article #6fdaa#4JHA.1***@TK2MSFTNGP06.phx.gbl, "Seth Wilson" <sputnik75***@yahoo.com> wrote: Show quoteHide quote > Thanks, but I only wish it were that simple - - I went back through the > setup and chose my preferences, including WS Components and it told me that > nothing was going to happen because I had no effective change to the > existing setup > > > "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message > news:C64B4083.2CFF2%ten.xoc@dnartreb.noraa... >>> Why would this happen >> >> Usually because you didn't select Workstation Components during setup. >> >>> how can I get it back? >> >> Run setup again. >> You cannot add features to an existing install by just re-running the setup
program. To add features you have to go into Add/Remove and select change. From there, you can add the workstation components. Show quoteHide quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:C64B4CDD.2D000%ten.xoc@dnartreb.noraa... > Did you search your machine for SqlWb.exe ? > > > On 6/2/09 8:59 PM, in article #6fdaa#4JHA.1***@TK2MSFTNGP06.phx.gbl, "Seth > Wilson" <sputnik75***@yahoo.com> wrote: > >> Thanks, but I only wish it were that simple - - I went back through the >> setup and chose my preferences, including WS Components and it told me >> that >> nothing was going to happen because I had no effective change to the >> existing setup >> >> >> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in >> message >> news:C64B4083.2CFF2%ten.xoc@dnartreb.noraa... >>>> Why would this happen >>> >>> Usually because you didn't select Workstation Components during setup. >>> >>>> how can I get it back? >>> >>> Run setup again. >>> > You should be able to, if you are just installing Workstation components,
setup isn't going to care if there's already a SQL Server instance installed. How would you suggest adding a new instance? Do you use Add/Remove Programs for that too? I guess I'll have to build a VM to verify. On 6/2/09 10:11 PM, in article 2D5B3A4B-928B-4BB7-BE47-C31375DE2***@microsoft.com, "Jeffrey Williams" <jeff.williams3***@verizon.net> wrote: Show quoteHide quote > You cannot add features to an existing install by just re-running the setup > program. To add features you have to go into Add/Remove and select change. > From there, you can add the workstation components. I tried creating a new instance - no luck there.
I'm trying to go the other route now - with Add/Remove Hopefully that will work Show quoteHide quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:C64B62DF.2D02E%ten.xoc@dnartreb.noraa... > You should be able to, if you are just installing Workstation components, > setup isn't going to care if there's already a SQL Server instance > installed. How would you suggest adding a new instance? Do you use > Add/Remove Programs for that too? I guess I'll have to build a VM to > verify. > > > > > On 6/2/09 10:11 PM, in article > 2D5B3A4B-928B-4BB7-BE47-C31375DE2***@microsoft.com, "Jeffrey Williams" > <jeff.williams3***@verizon.net> wrote: > >> You cannot add features to an existing install by just re-running the >> setup >> program. To add features you have to go into Add/Remove and select >> change. >> From there, you can add the workstation components. > Well, that didn't work either - I guess I'm just going to have to
uninstall/reinstall This really sucks Show quoteHide quote "Seth Wilson" <sputnik75***@yahoo.com> wrote in message news:OuW#4n$4JHA.2656@TK2MSFTNGP05.phx.gbl... > I tried creating a new instance - no luck there. > I'm trying to go the other route now - with Add/Remove > Hopefully that will work > > "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in > message news:C64B62DF.2D02E%ten.xoc@dnartreb.noraa... >> You should be able to, if you are just installing Workstation components, >> setup isn't going to care if there's already a SQL Server instance >> installed. How would you suggest adding a new instance? Do you use >> Add/Remove Programs for that too? I guess I'll have to build a VM to >> verify. >> >> >> >> >> On 6/2/09 10:11 PM, in article >> 2D5B3A4B-928B-4BB7-BE47-C31375DE2***@microsoft.com, "Jeffrey Williams" >> <jeff.williams3***@verizon.net> wrote: >> >>> You cannot add features to an existing install by just re-running the >>> setup >>> program. To add features you have to go into Add/Remove and select >>> change. >>> From there, you can add the workstation components. >> How about running "<sql_media(cd2)>\Tools\Setup\SqlRun_Tools.msi"?
If that does not work too, then you'll need to install it from command prompt: http://technet.microsoft.com/en-us/library/ms144259(SQL.90).aspx Go to this topic: To install SQL Server 2005 Client Tools only You may need to use SKUUPGRADE parameter too, you can find info about this info on the same page. -- Show quoteHide quoteEkrem Önsoy "Seth Wilson" <sputnik75***@yahoo.com>, iletisinde sunu yazdi, news:Okwt%23r$4JHA.1716@TK2MSFTNGP03.phx.gbl... > Well, that didn't work either - I guess I'm just going to have to > uninstall/reinstall > This really sucks > > "Seth Wilson" <sputnik75***@yahoo.com> wrote in message > news:OuW#4n$4JHA.2656@TK2MSFTNGP05.phx.gbl... >> I tried creating a new instance - no luck there. >> I'm trying to go the other route now - with Add/Remove >> Hopefully that will work >> >> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in >> message news:C64B62DF.2D02E%ten.xoc@dnartreb.noraa... >>> You should be able to, if you are just installing Workstation >>> components, >>> setup isn't going to care if there's already a SQL Server instance >>> installed. How would you suggest adding a new instance? Do you use >>> Add/Remove Programs for that too? I guess I'll have to build a VM to >>> verify. >>> >>> >>> >>> >>> On 6/2/09 10:11 PM, in article >>> 2D5B3A4B-928B-4BB7-BE47-C31375DE2***@microsoft.com, "Jeffrey Williams" >>> <jeff.williams3***@verizon.net> wrote: >>> >>>> You cannot add features to an existing install by just re-running the >>>> setup >>>> program. To add features you have to go into Add/Remove and select >>>> change. >>>> From there, you can add the workstation components. >>> A search of all partitions and drives - no sqlwb.exe
what next? Show quoteHide quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:C64B4CDD.2D000%ten.xoc@dnartreb.noraa... > Did you search your machine for SqlWb.exe ? > > > On 6/2/09 8:59 PM, in article #6fdaa#4JHA.1***@TK2MSFTNGP06.phx.gbl, "Seth > Wilson" <sputnik75***@yahoo.com> wrote: > >> Thanks, but I only wish it were that simple - - I went back through the >> setup and chose my preferences, including WS Components and it told me >> that >> nothing was going to happen because I had no effective change to the >> existing setup >> >> >> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in >> message >> news:C64B4083.2CFF2%ten.xoc@dnartreb.noraa... >>>> Why would this happen >>> >>> Usually because you didn't select Workstation Components during setup. >>> >>>> how can I get it back? >>> >>> Run setup again. >>> >  
Other interesting topics
SSMS 2008 Add-ons: What is the 2008 replacement for SQLWB.EXE?
2008 SSMS object explorer SQL Server 2005 Error execute long sql script saving SQL files in SSMS as ASCII Maintenance Plan Fails script to cliboard in microsoft SQL server management studio Management Studio 2005 download? Database diagrams in ss2008 Generating script to individual files |
|||||||||||||||||||||||
