I've upgraded my SQL Server from the 2008 R2 Express edition to a full standard version of SQL Server 2014. Now I'm running them both side by side. But my problem is how can I abandon the 2008 version and only run on the 2014 version? I've check the properties on the SQL Server 2014, and it shows that I'm still with 2008 R2 Express edition. How is that possible?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
So, to clarify, you did a side-by-side upgrade. Meaning that you installed a new instance of SQL Server 2014?
In that case, if you are ready to rid yourself of the SQL Server 2008 R2 instance then you would need to transfer all of your necessary entities from the 2008 R2 instance to the 2014 instance. That'll include everything it would take to make your clients hit the new 2014 instance. Most notably, you'll be backing up and restoring your databases from the source (SQL Server 2008 R2 instance) to the destination (SQL Server 2014 instance). But you will most likely need to transfer other server objects as well.
Note: Max brought up a good point in his comment below, ensure that you have a valid database backup/restore on your destination instance before removing anything.
Point your applications/clients to the new SQL Server 2014 instance after the migration. And then you can rid yourself of the SQL Server 2008 R2 instance if you no longer want those bits to be living on that machine. Warning, you should verify with the business and end users that functionality is now back to the same state as it was prior to the upgrade.
I'm not sure what you mean here. How did you check the "properties" and what exactly are you referring to? You're either connecting to your old SQL Server 2008 R2 instance, or you new SQL Server 2014 instance. If the former, you'd be in the context of the old one. If the latter, you should be seeing the new 2014 instance. If that's not what you mean, then please clarify.
select @@version will give you which version you are actually connecting to.Also check whether your instance names of both in configuration manager to avoid accidentally connecting