I know it might sound naïve but is there's anyway to use the SSMS 2012 with SQL Server 2008 as it's our deployment server but I really hate the absence of Intellisense SSMS 2008 and it makes me waste a lot of time that makes using the GUI much more reasonable option
You need to install SSMS 2012 from the installation media of SQL Server 2012. Or as an alternative you can download and use SSMS 2016, which is still in beta, but can be downloaded and updated separately from a database engine - https://msdn.microsoft.com/en-us/library/mt238290.aspx. It has all features of SSMS 2012 and more.
Yes, I've used SSMS 2012 and 2014 against our production 2008 and 2008R2 SQL server instances.
I have used SSMS2012 against multiple versions of SQL Server (2008R2, 2012 and even 2014) and I have not encountered any problems so far. Anyway, I expect to be fully backward compatible, so it should work fine with 2008R2.
Related
I am using locally the MS SQL Server Management Studio 2012 with SQL server 2012 database engine.
I have the following question:
Can I upgrade ONLY the SQL Server Management Studio 2012 (TOOLS) to 2014 version, and leave my old 2012 already installed database engine version?
Yes, you can.
But install SSMS 2014 as standalone (instead of trying to upgrade tools).
From SSMS 2014 SP1 release notes you can see that it vitally supported SQL Server 2012. See how many compatibility fixes for 2012 were delivered.
Generally I'd recommend to prefer latest release of SSMS 2016 which
works with all supported versions of SQL Server (SQL Server 2008 - SQL Server 2016)
(Besides that I tried to find similar statement for SSMS 2014 (there was one), but I couldn't.)
I'm using SSMS 2008 + SSMS 2016 side by side and they are running just fine. In similar way, I was using SSMS 2008 + SSMS 2014 before the upgrade.
You can download and install SQL Server Management Studio using the links provided in: Scott Hanselman's website
There are links to various SSMS versions (2012, 2014, for x86, x64), as well as links to various SQL-Server Express versions.
By the way, you can use the latest SSMS 2014 to manage your 2012 database.
You could simply install new SSMS 2014 version and leave the 2012 version installed ONLY IF they are all 32-bit or 64-bit. You cannot upgrade 32-bit 2012 to 64-bit 2014 and vice versa. Ideally you could use 2014 version SSMS to access databases created in 2012 before because of the compatible level allows you to do that, but it will raise another problem for restoring the databases since you cannot restore any backup files that backed up from old(2012) to (2014) because of the database version did not match.
SSMS is now a separate free product that works with all versions from 2008 and up. The current version is 16.5.3
For older versions:
There is no explicit block for SQL Server 2000 or SQL Server 2005, but some features may not work properly.
You'll have to download the RC version if you want to connect to SQL Server vNext, eg to SQL Server on Linux
I just upgraded my MS SQL Server 2008 R2 to 2012 on my local machine. Its all ok and there is no problems. All is working good (I mostly develop asp.net mvc applications and some desktop applications. All of them are pretty simple).
Can i safely delete 2008 server from my computer? Are there any things that i should care about?
Thank you.
When I upgraded to SQL 2012, I first removed SQL 2008 completely in Programs and features and then installed SQL 2012. This was fine and I had no problems. Where ever practically possible I would recommend removing the old product first before installing the new.
I would think that removing SQL 2008 should be fine. Worst case senario you may have to do a repair on SQL 2012 or re-install.
I use SQL Server 2008 R2 as the database engine. With my MSDN subscription, I can get SQL Server 2012 for development use. Since I noticed some cool things in 2012 SSMS, my question is that if I only use 2012 SSMS and keep 2008 R2 as the database engine, will there be any difference in scripts' generation or any other effects?
Thanks.
UPDATE 1:
Oh yes, I saw this page: SQL Server Database Engine Backward Compatibility, but it is not exactly what I am looking for.
No, there should be no ill effects.
SSMS 2012 should generate scripts that are compatible with the database version that is being actively used.
Does the SQL 2008 Express have intellisense?
If you mean SQL Server 2008 Management Studio Express, then yes. It's context-based depending on the database you're currently in, and not always 100%, but it is there.
According to this post it was initially in there but later dropped:
SQL Server Management Studio 2008 Intellisense
SSMS 2008 has intellisense, but it works with SQL Server 2008 only.
If you need SQL autocomplete/formatting functionality for previous versions of SQL Server, take a look at dbForge SQL Complete - a free add-in for SQL Server Management Studio that replaces built-in intellisense.
In adding to our previous answer: recently we have released a new version of dbForge SQL Complete that offers a bunch of new features. All new features are available in shareware Standard Edition (30-days free trial, $49.95).
You still can get all basic functionality, similar to v. 1.0, with Express Edition.
When I try to install a new instance of SQL Server 2008 Express on a development machine with SQL 2005 Express already up and running, the install validation fails because the "SQL 2005 Express tools" are installed and I'm told to remove them.
What exactly does that mean?
After reading this article:
http://www.asql.biz/Articoli/SQLX08/Art1_5.aspx
I uninstalled the 2005 version of the SQL Management Studio but received the same error from the 2008 installer during my follow-up attempt.
Updates
1) Uninstalled the SQL 2005 Management Studio only. Received the same error from the 2008 install.
2) Removed all SQL 2005 common components. Received the same error from the 2008 install.
3) Installed the shared components from the SQL 2008 installation program. Received the same error from the 2008 install when trying to install the new SQL 2008 instance.
4) Uninstalled SQL 2008 components, rebooted, re-installed SQL 2005 Management Studio from installation media, rebooted, un-installed SQL 2005 Workstation Components from Control Panel, re-booted.
Installation of SQL 2008 is now proceeding as it should.
Seems likely that if I'd re-booted after update 2 above things would have gone more smoothly. :-(
Although you should have no problem running a 2005 instance of the database engine beside a 2008 instance, The tools are installed into a shared directory, so you can't have two versions of the tools installed. Fortunately, the 2008 tools are backwards-compatible. As we speak, I'm using SSMS 2008 and Profiler 2008 to manage my 2005 Express instances. Works great.
Before installing the 2008 tools, you need to remove any and all "shared" components from 2005. Try going to your Add/Remove programs control panel, find Microsoft SQL Server 2005, and click "Change." Then choose "Workstation Components" and remove everything there (this will not remove your database engine).
I believe the 2008 installer also has an option to upgrade shared components only. You might try that. Good luck!
In my case even after uninstalling all 2005 related components it didn't worked. I had to resort to a brute force way and remove following registry keys
32 Bit OS: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90
64 Bit OS: HKLM\Software\Wow6432Node\Microsoft\Microsoft SQL Server\90
I had to unistall the Workstation Components and SSMS Tools Pack (SSMS Tools Pack is an add-in for Microsoft SQL Server Management Studio (SSMS) including SSMS Express.)
Installation of SQL 2008 is now proceeding as it should.
The problem is that SQL 2008 MS has a bug where connecting to a remote server (say like a service provider collocation) it will always try to open the fist db in the list, and since the possibilities of been ur db the first on the list are really low, it will throw and error and fail to display the list of dbs... which using sql 2005 management studio it just works.
Wished I could use SQL 2008 MS, but looks like as far I connect to remote SQL 2005, SQL 2008 is out of the question on my dev machine :(
Just Remove the the Workstation Components from Add/Remove Programs - SQL Server 2005.
Removing Workstation Components, SQL Server 2008 installation goes well.
Simply remove the Microsoft SQL Server Management Studio Express 2005 from control panel
N.B. These notes are for SQL Server Express 2008 R2 (so Microsoft still haven't made this any easier). I also realise that I complicated things by installing 32-bit SQL Server Express 2005 and 64-bit SQL Server Express 2008.
I followed the steps by Josh Hinman above. Uninstalling the SQL Server Express 2005 "Workstation Components" was not enough. I required an uninstall of the 2005 Management Studio as well.
I also tried the Upgrade route that Josh Hinman suggested by clicking on the 'Upgrade from SQL Server 2000, SQL Server 2005 or SQL Server 2008'. This route never gave me the option of installing the components side-by-side it just went straight through the process of upgrading from 2005 to 2008. It completed successfully - but hadn't actually done anything. Thankfully though it hadn't harmed any existing database instances. So be warned trying that route.
If you currently have Red Gate SQL Toolbelt, you will need to unistall that too before continuing. Somehow it adds a reference to the 2005 version of the SQL Management Studio.
I'am trying to install SQL SERVER developer 2008 R2 alongside SQL SERVER 2005 EXPRESS,
i went to program features, clicked on unistall SQL SERVER 2005 EXPRESS, and only checked, WORKSTATION COMPONENTS, it unistalled: support files, sql mngmt studio
After that installation of sql 2008 r2 developer went ok....
Hopes this helps somebody
I also had to remove the SMSS before it would get past that step.