Use SQL Express 2014 instead of SQL Express 2014

(Newbie alert - I have used SQL Server mostly only as an extension of Visual Studio).

I'm trying to get Management Studio (SSMS) (and VS) to use SQL Express 2014 instead of SQL Express 2012.  

The more general problem is to get "localhost" to be SQL Express 2014;  I'm stating with SSMS.

I've got an apparent full install of SQL Server 2014 on my machine (courtesy BizSparks/MSDN)

When I start  SSMS and do the login selecting MyPC\SQLExpress,  the resulting server =
      MyPC\SQLExpress (SQL Server 11.0.5343 - MyPC\Me)

11.0.5343 is 2012, best I can tell.

I tried to uninstall SQL Server 2012 and SQLExpress 2012.  Main SS 12 didn't change at all after uninstall routine, and SQLExpress came back after a reboot.

Any suggestions on how to get localhost to be SQLExpress 2014 instead of 2012 would be appreciated.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
You have to uninstall both SQL server instances. Then reinstall MSSQL 2014 Express, and make sure to choose "unnamed instance" instead of ".\SQLExpress" as instance name.

On the other hand, there is nothing wrong with using .\sqlexpress as connection property!
codequestAuthor Commented:
Thanks for the input.  Here's where we run into my newbieness:

Re: uninstall - to uninstall ALL of the SQL Server components for BOTH 2014 and 2012?  Or Just SQL Express?

"On the other hand, there is nothing wrong with using .\sqlexpress as connection property"
How would I make use of that?

Please pardon this rant:  My situation right now is that I've got some credits on Azure for the next six months, and I'm trying to upload a DB to Azure, and it says I need to migrate it to overcome compatibility issues with "Azure SQL Server", and I can't get the MS Migration Tool to work, because it won't detect any DB's under "localhost", so I backed up into starting with "make sure local host = 2014", because that might help with the compatibility issues.   At this point I'm starting to look for other hosting providers;  the credits aren't that much all things considered, and they don't include support, which is getting to look pretty important...
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
If you are unsure about how to use a named instance, probably the best is indeed to uninstall *both* MSSQL instances, as said - 2012 and 2014. Then you should be able to install 2014 Express again. I cannot add much to my last comment.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
codequestAuthor Commented:
Understood, thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.