SQLMint
Running the SQL Server 2014 upgrade advisor is a good idea when say planning an in-place upgrade from a previous version of SQL Server.
To do this, run setup from the installation disc, go to planning, run install upgrade advisor.
You might get a pop up such as below, this is resolved by downloading and installing the SQL 2014 feature pack components from this link. Click here.
Notes:
After performing an in-place upgrade on a SQL 2008 R2 server to SQL 2014, l had access issue to SSIS 2014.
I also noticed [rom SSCM SQL Server Configuration Mananger] that SSIS 2008 R2 ie SSIS version 10.0 was still running, using the NT Autohoritynetworkservice account while SSIS 2014 ie version 12.0 was also running – but using the nt servicemsdtsserver120 local account.
From a remote SSMS 2008 R2 window, l could access the target SSIS instance and it shows up with version 10.50.4000 [the number for SSIS 2008 R2]
From the local upgraded server’s SSMS 2014 , connecting to the target SSIS 2014 shows a connection with version number 12.0.2000
Steps taken to resolve the initial access issue.
In some situations you might want to perform an in-place upgrade from say SQL 2008 R2 to SQL 2014, rather than a fresh installation.
First thing to do is to run the Install upgrade advisor, this can be sound by running the setup.exe in the SQL 2014 installation disk, selecting Install Upgrade Advisor from the planning menu.
You might get an error as shown below. To solve this, run/install components for SQL 2014 which can be found by clicking here.
After a restart, you should be able to run the install upgrade advisor, which will be accessible from Start/PRograms/SQL 2014/SQL Server 2014 Upgrade Advisor
Below shows a step by step install of Microsoft SQL Server 2014 which was releases on April 1st 2014. in pictures with some notes.
Notes:
For a server install, Microsoft recommends using separate domain accounts for each sql service. Below setup is the same for a server environment install, but works best for a developer workstation. Also, for a stand alone sql server, you will want to place the mdf, ldf, backup files in separate sas,san, ssd, raid configured san setup uptimally for the individual files you are storing.
Below shows SQL Server Configuration Manager 2014. Remember to enable TCP/IP and restart the SDE and SSA – SQL database and sql server agent engines.
“Microsoft SQL Server 2014 builds on the mission-critical capabilities delivered in the prior release by providing breakthrough performance, availability and manageability for your mission critical applications. SQL Server 2014 delivers new in-memory capabilities built into the core database for OLTP and data warehousing, which complement our existing in-memory data warehousing and BI capabilities for the most comprehensive in-memory database solution in the market.”