Solved

SQL instalation

Posted on 2014-12-11
5
110 Views
Last Modified: 2014-12-12
Hi!
Will I face any problems when installing a 2012 SQL Standard instance on a server that is already running a 2014 SQL Standard instance?
0
Comment
Question by:elit2007
  • 3
  • 2
5 Comments
 
LVL 5

Expert Comment

by:Dejan Vasiljevic
ID: 40493663
Hi elit2007,

SQL Server SysPrep does not support side by side installation of prepared instances of SQL Server 2014 with earlier versions of SQL Server on the same computer. For example, you cannot prepare a SQL Server 2014 instance side by side with a prepared instance of SQL Server 2012. However, you can install multiple prepared instances of the same major version of SQL Server side by side on the same computer. For more information, see Considerations for Installing SQL Server Using SysPrep .

SQL Server 2014 cannot be installed side-by-side with earlier versions of SQL Server on a computer that is running Windows Server 2008 R2 Server Core SP1. For more information on Server Core installations, see Install SQL Server 2014 on Server Core .

From official MSDN
Also, I saw Exsisting Instance of SQL Server 2014 support Side-by-side 2005 to 2014 both 32/64 bits. But I guess You will need to define major version and minor version.
All in all, i think You will be able to configure them without any major problem, just pay attention to those things. *SysPrep

Thanks,
D.
0
 
LVL 1

Author Comment

by:elit2007
ID: 40493713
The OS on the server is 2012. So it shouldn't be a problem as long as i run a manually installation?
My concern was shared files. If SQL 2012 overwrite files that SQL 2014 already is using.
0
 
LVL 5

Accepted Solution

by:
Dejan Vasiljevic earned 500 total points
ID: 40493741
I would backup files, which I always do before doing such an important thing, so if anything goes wrong, You always have Your files backed up. I think the OS is not a problem at all, everything after 2008 R2 should be just fine.

And for Your concerns about shared SQL files there is an article saying - "Certain components are shared by all instances of all installed versions of SQL Server. When you install different versions of SQL Server side-by-side on the same machine, these components are automatically upgraded to the latest version. Such components are usually uninstalled automatically when the last instance of SQL Server is uninstalled.
Examples: SQL Server Browser and Microsoft SQL Server VSS Writer.
"
MSDN is source again
Also You can change the default path, and etc.

Thanks,
D.
0
 
LVL 1

Author Comment

by:elit2007
ID: 40495585
Thanks a lot! I just have to hope that when I install SQL 2012, the installation program will see that the shared files have a newer version and not overwrite them.  :)
0
 
LVL 5

Expert Comment

by:Dejan Vasiljevic
ID: 40495640
You are welcome. As what we saw from microsoft official site, it should not overwrite them, because they are newer than SQL 2012 shared files, but again to make yourself secured, backup files before start.

Regards,
D.
0

Featured Post

Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Nowadays, some of developer are too much worried about data. Who is using data, who is updating it etc. etc. Because, data is more costlier in term of money and information. So security of data is focusing concern in days. Lets' understand the Au…
Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Via a live example, show how to shrink a transaction log file down to a reasonable size.

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question