How to install SQL Server Management Studio 2008 component only [closed] - sql-server-2008

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Below is a list of the SQL components that I installed in the Visual Studio 2010 Professional setup. Sadly, while trying to work I could not find SQL Server Management Studio 2008.
Is there a way to download SQL Server Management Studio 2008 separately and install only that component?
Since in the past I installed SQL Server Management Studio 2005 with a whole new instance of SQL Server 2005 and had couple of instances, and it was a bit messy.

I found some articles to be of major use:
This link is an experience someone else had:
http://goneale.com/2009/05/24/cant-install-microsoft-sql-server-2008-management-studio-express/
This link has the exact steps involved to install everything properly:
http://www.codefrenzy.net/2011/06/03/how-to-install-sql-server-2008-management-studio/
This link confirms the previous link:
https://superuser.com/questions/88244/installing-sql-server-management-studio-when-vs2010-beta-2-is-already-installed
My Instructions
I am not sure if my instructions will be 100% accurate, but in my instance, because I installed VS2010 on a fresh copy of Windows 7, the VS2010 installer installs SQL Server 2008 Express for you, so from this point I just need the Management Studio.
What I gathered from these explanations is to do the following:
Download the SQL Server Management Studio install from
http://www.microsoft.com/download/en/details.aspx?id=22973
Run the setup, when you get to the point where it asks you to "Perform a new installation of SQL Server 2008" or "Add features to an existing instance of SQL Server 2008", this part is the CONFUSING PART (HEY MICROSOFT TAKE NOTES, DON'T DO THIS KIND OF STUFF).
As much as you want to select "Add features to an existing instance of SQL Server 2008" DON'T!!!!
You need to select "Perform a new installation of SQL Server 2008". It doesn't sound right I know - it is very confusing and counter intuitive, but this seems to be the way to install management studio. :(
Press next until you see the features selection portion. Heeeeeyyyy look at that, it has a check box for Management Studio. It should be selected already, if not then select it of course and press next.
Press Next next next next next next... basically just install it at this point.
Enjoy, it has installed.

If you have the SQL Server 2008 Installation media, you can install just the Client/Workstation Components. You don't have to install the database engine to install the workstation tools, but if you plan to do Integration Services development, you do need to install the Integration Services Engine on the workstation for BIDS to be able to be used for development. Keep in mind that Visual Studio 2010 does not have BI development support currently, so you have to install BIDS from the SQL Installation media and use the Visual Studio 2008 BI Development Studio that installs under the SQL Server 2008 folder in Program Files if you need to do any SSIS, SSRS, or SSAS development from the workstation.
As mentioned in the comments you can download Management Studio Express free from Microsoft, but if you already have the installation media for SQL Server Standard/Enterprise/Developer edition, you'd be better off using what you have.
Download SSMS 2008 Express

I am just updating this with Microsoft SQL Server Management Studio 2008 R2 version. if you run the installer normally, you can just add Management Tools – Basic, and by clicking Basic it should select Management Tools – Complete.
That is what worked for me.

The accepted answer was correct up until July 2011. To get the latest version, including the Service Pack you should find the latest version as described here:
http://support.microsoft.com/kb/2527041
For example, if you check the SP2 CTP and SP1, you'll find the latest version of SQL Server Management Studio under SP1:
http://www.microsoft.com/en-us/download/details.aspx?id=26727
Download the 32-bit (x86) or 64-bit (x64) version of the SQLManagementStudio*.exe files as appropriate and install it. You can find out whether your system is 32-bit or 64-bit by right clicking Computer, selecting Properties and looking at the System Type.
Although you could apply the service pack to the base version that results from following the accepted answer, it's easier to just download the latest version of SQL Server Management Studio and simply install it in one step.

For any of you still having problems as of Sept. 2012, go here: http://support.microsoft.com/kb/2527041 ...and grab the SQLManagementStudio_x(32|64)_ENU.exe (if you've already installed SQL Server 2008 Express R2), or SQL Server 2008 Express R2 with Tools, i.e. SQLEXPRWT_x64_ENU.exe or SQLEXPRWT_x32_ENU.exe (if you haven't).
From there, follow similar instructions as above (i.e. use the "Perform new installation and add shared features" selection, as "Management Tools - Basic" is considered a "shared feature"), if you've already installed SQL Server Express 2008 R2 (as I had). And if you haven't done that yet, then of course you're going to follow this way as you need to install the new instance anyway.
This solved things for me, and hopefully it will for you, too!

SQL Server Management Studio 2008 R2 Express commandline:
The answer by dyslexicanaboko hits the crucial point, but this one is even simpler and suited for command line (unattended scenarios):
(tried out with SQL Server 2008 R2 Express, one instance installed and having downloaded SQLManagementStudio_x64_ENU.exe)
As pointed out in this thread often enough, it is better to use the original SQL server setup (e.g. SQL Express with Tools), if possible, but there are some scenarios, where you want to add SSMS at a SQL derivative without that tools, afterwards:
I´ve already put it in a batch syntax here:
#echo off
"%~dp0SQLManagementStudio_x64_ENU.exe" /Q /ACTION="Install" /FEATURES="SSMS" /IACCEPTSQLSERVERLICENSETERMS
Remarks:
For 2008 without R2 it should be enough to omit the /IACCEPTSQLSERVERLICENSETERMS flag, i guess.
The /INDICATEPROGRESS parameter is useless here, the whole command takes a number of minutes and is 100% silent without any acknowledgement. Just look at the start menu, if the command is ready, if it has succeeded.
This should work for the "ADV_SSMS" Feature (instead of "SSMS") too, which is the management studio extended variant (profiling, reporting, tuning, etc.)

Related

Cant create BIDS project in VS2008

Client :
- Windows 7 SP1 32bit
- With SQL Express - Advance series installed (with VS2008)
Server:
- Database: SQL Server 2008R2 Enterprise Ed., 64bit
- OS: Windows Server 2008
I always get the message "To design IS packages in BIDS, BIDS has to be installed"
What am I missing here?
Really need your help guys, first time using VS much more the BIDS.
Thanks,
Elmer
You need to install BIDS on your client machine. BIDS is not included as part of Visual Studio, it is part of SQL Server (but runs in the Visual Studio shell). So get your SQL 2008R2 media and run the installation a new instance or add features. You don't need any of the Instance Features, but you should include the following Shared Features:
Business Intelligence Development Studio
Client tools Connectivity
Client tools SDK
Management Tools - Complete
SQL Client Connectivty SDK

SSIS SSDT - Deploying A DTSX to a Server

I have been searching for a while on this and have no real direction on what the problem may even be. I haven't done SSIS for about 5 years and even 5 years ago I only did one or two.
I have Visual Studio 2012 on my machine. I installed SSDT so that I could write an SSIS package. I have the package written and working locally but when I try to set up a job in the SQL Agent on the server I get this error after selecting the package:
I have looked into this error and none of the resolutions I have found are working. My project is already set to not use 64 bit mode. I'm kind of thinking this might have to do with the fact that the version of SQL Server on that machine is just 2008 and that maybe that means it has an incompatible SSIS runtime. I don't know if there is an additional runtime I need to install to get this to work and I don't know if it's backward compatible with the old runtime they are using if that's even the problem.
I can't find any information online about setting up the environment for an SSDT SSIS package..
Please help.
Thanks
You have a package built against the SQL Server 2012 Integration Services object model. You are attempting to execute it on a 2008 instance. Backwards compatibility is not an option.
You need to either update the 2008 instance to 2012 (there is a licensing change to be aware of) or recreate your package using the 2008 model.
There are 2 steps you have to do:
1) Build you package using correct version - Update 2208 Instance to 2012
2) If you have multiple versions install and you try to deploy using .ispac file, it will most likely pick the latest version. To resolve the issue, you have to pick the correct version of Installer by going to where it is installed. In my case it is (C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn)

Are there any pitfalls when upgrading SQL Server Express to Standard 2008 R2 that serves a Microsoft Sharepoint 2007 (MOSS 2077) implementation? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Are there any pitfalls when upgrading SQL Server Express to SQL Server Standard 2008 R2 that serves a Microsoft Sharepoint 2007 (MOSS 2077) implementation?
We recently completed an update of a team foundation sql server by installing the Standard Edition of SQL over the top of the existing Express edition with no issue. So we plan to upgrade the Sharepoint server the same way.
Are there any pitfalls or hints we should be aware of? I am concerned that the data and customizations done in Sharepoint are not lost or damaged.
We will as a matter of course be taking backups prior to any change.
Question: Are there any pitfalls when upgrading SQL Server Express to SQL Server Standard 2008 R2 that serves a Microsoft Sharepoint 2007 (MOSS 2077) implementation?
There are no real pitfalls, but definitely some items to put on your migration checklist. You need to convert the whole instance from Express to a 2008 R2 "real database solution". This is a good move to make.
Given that you have an Express edition that came with the Sharepoint installation, it is mostly likely not a SQL Server 2008 or SQL Server 2008 R2 edition, and most likely have not SSMS tools installed. You will need the Standard Edition installation media and the product key. That is a given. Run the setup program from the standard edition media directly. Do NOT try to run setup from the installed SQL Server and use Edition upgrade option.
Verify the installation using SQLCMD once you have the Standard Edition in place. Run setup from installation media again and install the desired shared components such as SSMS, Integration Services, Books Online, etc. The Sharepoint setup installed SQL Agent installed with SQL Express by the Sharepoint installation may be disabled and set to run as "Network Service" and not have the SysAdmin SQL Server rights.
Change the service account for the Agent to have the sysadmin rights. The SQL Agent will then start. Check database options, file size, auto grow settings, and other maintenance items for the sharepoint databases. You probably want to move the Sharepoint databases to a better location than the default folders in Program Files --> Common Files. Good luck as you move off of the Express Edition.

Can't install SQL Server 2008 R2 management tool (complete)

I have SQL Server 2008 R2 Express installed on my workstation. I’m in the process of learning Entity Framework, and wanted to use the Management Studio Profiler to help understand the SQL commands generated by EF.
Since the Express version does not include the Profiler, I installed SQL Server 2008-R2 Developer side-by-side with Express. The installation went perfectly and I had no problem adding my databases to the full Server installation.
The problem is that Management Studio – Complete was not installed with the full SQL Server so I still don’t have access to the profiler. I re-ran the installer so I could install the Complete version, but it is greyed out and I cannot select it for installation.
Can someone help me get Management Studio – Complete installed?
If I have to uninstall the Express version, will that hurt anything (I have VS2010 Ultimate installed as well)?
Thanks!
I ran into this and had the hardest time getting the Management Tools - Complete to install. I finally got it working by running the upgrade. Even though it was already Enterprise edition with nothing obvious to upgrade I went through the update wizard. After that I was able to do the install of the complete tools.
Steps:
Run the installer -> Maintenance -> Edition Upgrade -> follow the wizard.
Then -> Run the installer -> Installation -> New SQL Server stand-alone ... -> ... "Add features to existing install" -> Management Tools - Complete.
To solve the problem I uninstalled SQL express and the Basic version of Server Management Studio.
Uninstalling SQL Express is not intuitive as it does not appear as a separate item in the “Programs and Features” window.
To uninstall it, I right-clicked on “Microsoft SQL Server 2008 R2 (64-bit)” and selected Uninstall/Change”. This opened a dialog, from which I selected ‘Remove’. I navigated though the process until I arrived at a screen which allowed me to elect to remove the Express version (all items with 'Express' in the name). I also elected to remove Management Studio Basic.
After SQL Server Express and Management Studio Basic were uninstalled, I started the SQL Server 2008 R2 installer; this time I was able to select Management Studio Complete for installation.
The installation process executed normally; when it finished the Complete version of Management Studio was available and I was able to execute the Profiler.
Uninstalling SQL Server Express appears to have done no harm to my system; I was able to modify the Server Explorer data connection in VS2010 to connect to my database in the full version of SQL Explorer.
This process outlined above worked for me; YMMV.
In my case I was trying to install instance features, while SQL Management Studio is a Shared feature.
Another way of installing SQL Management Studio is to install another instance using SQL With Tools or the Advance Services issue. Do not look into another instance that is already installed.

SQL Server DTA Missing

Slightly OT, but...
I have two named instances of MSSQL 2008 Developer Edition and also SQL Express 2008 with Advanced Services.
I just went to use the DTA, and it is not anywhere on my system.
I went to setup to add it, and see that the checkbox for it is cleared (all others are checked), and it and every other shared tool is greyed out so I can't get it installed.
Before I uninstall all of this stuff, can anyone recommend a way to get this stuff installed.
Thanks.
The bottom line is "don't install SQL Server Express after you install Developer Edition".
I uninstalled all of the Shared Services (Basic Management Tools, etc) for the SQLExpress instance, then installed a new instance of Developer Edition, and I was able to then get the performance tools included. DTA is now back.