Upgrade sql server 2008 to 2014

Hello,
1- is it possible to install 2014 while 2008 is installed. And then restore the 2008 database into the 2014 version?
2- is 2014 version out and can it be fully used now?
Thanks

SQL Server edition
Definition
Enterprise (64-bit and 32-bit)
The premium offering, SQL Server 2014 Enterprise edition delivers comprehensive high-end datacenter capabilities with blazing-fast performance, unlimited virtualization, and end-to-end business intelligence — enabling
high service levels for mission-critical workloads and end user access to data insights.
https://msdn.microsoft.com/en-us/library/ms144275.aspx
SQL Server Data Tools - Business
Intelligence (SSDT-BI) includes SQL Server Analysis Service Projects, SQL Server Reporting Services
Projects, and SQL Server Integration Services Projects hosted in Visual Studio. SSDT-BI
tools can be downloaded and installed as free tools from the web.
http://blogs.technet.com/b/dataplatforminsider/archive/2013/11/13/microsoft-sql-server-data-tools-update.aspx

Similar Messages

Upgrade SQL server 2008 r2 to latest available Service Pack in SP 2010 farm.

Hi,
We have 2 server's in the farm ( WFE+App server and SQL server).
We are planning to upgrade SQL server 2008 r2 to latest available Service pack [10.50.6000 (SP3)] version.
So before upgrading SQL server , need to take any necessary actions from SharePoint server side ?
And once patching is done on SQL server, need to run SharePoint Configuration wizard ?
Please provide best way for this upgrade.
Cheers,
RameshNK

You certainly can turn off SharePoint/stop IIS if you wish, but it isn't required. SharePoint will be unavailable during a portion of the SP3 upgrade and will reconnect once SQL is back online.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

Hi Bob，
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Upgrade SQL Server 2008 R2 enterprise edition to SQL server 2012 slandered edition

Hi everyone,
Need help on below concern.
I have SQL Server 2008 R2 enterprise edition installed. Which contains SSAS cubes, SSIS packages and SSRS Reports.
I need to upgrade it to SQL Server 2012 Standard edition.
How can I achieve this ??
And I don't have much idea in SSIS package migrations.
Please help me to achieve this.
Thanks,
Rohit

Hi,
Please follow side by side approach for upgrade.Get a new windows box and install SQL server 2012 on it
Move databases from SS2008 R2 to SS 2012 by backup restore mechanism.
Move
jobs and logins by Scripting out and running it on SQL SS 2012.See links as well
Please refer to
this link for SSIS package migration
For SSAS please post question in SSAS forum
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Upgrade sql server 2008 to 2008R2 and apply Service pack 3

Hello,
I have a two node cluster (sql server 2008). I would like to upgrade to SQL Server R2 and at the same time would like to patch to Service Pack 3. What would be the best way to accomplish this task with minimal downtime to the users?
This is my plan:
1. Detach any read only databases.
2. Upgrade to 2008 R2 (shared feature only) on passive node (node1).
3. Apply SP3 on passive node in step 2.
4. Swith active node to passive node (node2).
5. Upgrade to 2008 R2 (shared feature only) on node2.
6. Apply SP3 on node2.
7. Upgrade db (instance) on node2 to 2008 R2.
8. Upgrade db (instance) on node1 to 2008 R2.
9. Re-attach read only databases.
Is my procedures correct?
Thank you.

Hello,
Have you seen the following article before?
http://msdn.microsoft.com/en-us/library/ms191295(v=sql.105).aspx
You can slipstream SQL 2008 R2 + SP3.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Limitations for upgrading SQL server database engin from SQL 2008 R2 enterprise edition to SQL 2014 enterprise edition

Dear All,
we are planning to upgrade SQL Server 2008 R2 Enterprise edition to SQL Server 2014 Enterprise edition.
please suggest the limitations for the up gradation.
Thanks in Advance
Vineet Srivastava
NIIT Technology Ltd.
New Delhi , India

Hello,
Please note that we have 2 Enterprise Editions now:
(1) Enterprise Edition with Server + Client Access License (CAL) and (2) the Enterprise Edition licensed by core. “Enterprise Edition with Server + Client Access License (CAL) based licensing (not available
for new agreements) is limited to a maximum of 20 cores per SQL Server instance. There are no limits under the Core-based Server Licensing model”. Source:
https://msdn.microsoft.com/en-us/library/ms143760(v=sql.120).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"

I've been searching for HOURS how to resolve this issue:
I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
======================================================================================
Rule Check Result
Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
=====================================================================================
This is the Configuration Report issue:
Microsoft SQL Server 2014 - System Configuration Check Report
UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
KJRTMUpgradeBlockRule
Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack. Failed The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
====================================================================================
I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
out!!!
Thanks.

Hi again
This is the scenario:
-I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
-As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
resolved immediately with the Windows Update service.
-Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
Now we are on 12.0.2000.8
Thanks anyway and all of you for your interest!!!

Upgrade DTSX packages from VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014

Hello everyone,
I’m very new to SSIS world. I’ve been assigned a task to upgrade the existing packages running in VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014. And then submit the migration report to my client.
On very quick search at Google, I've found the following link. It seems like I just need to open the existing SSIS project in VS 2013 and follow the wizard.
https://msdn.microsoft.com/en-us/library/cc280547.aspx
Can anybody please advise, are there any other things need to be taken care while doing this up gradation process?
Please share your experience.
Any help would be much appreciated.
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Hello Arthur,
Thank you for the response.
I just got an access of the packages. They are of VS 2008 and not 2010.
Do you know how to upgrade VS 2008 packaged to VS 2013?
When I tried to open the solution file in VS 2013, it says "incompatible".
Any help would be much appreciated.
Thanks,
Ankit
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Upgrade to SP3 from sql server 2008 R2 SP2 and SharePoint server 2010 known issues

Hi Guys,
We are planning to upgrade SQL server to SP3 from 2008 R2 SP2 and would like to known if there are any known issues with SharePoint 2010 server and office web apps.
Though I was searching blogs and forums and could not find any noteworthy but wanted to look if any noted SharePoint issues after the upgrade.
VM

Hi Venu,
There should no issue for SharePoint 2010 with install SP3 for SQL2008R2 (also like comments mentioned in article below), I searched from internal and internet, there seems no document/article mentioned the known issue for SharePoint about this, you can
back up your environment and test the SP3 in a test environment before touching the production environment.
https://habaneroconsulting.com/insights/SharePoint-SQL-Server-Support-Matrix#.VSTY-nkfr4Y
http://blogs.msdn.com/b/glsmall/archive/2014/12/03/list-of-fixes-in-sql-server-2008-r2-sp3.aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Using upgrade advisor on a database with compatibility level 80 on SQL Server 2008

Hi All,
My DB compatibility level is 80 which is on SqL server 2008, however I want to upgrade the database server to sql 2014.
Now in my case the upgrade advisor of SQL 2014 is not detecting the DB which is in 80 compatibility level and hence I cannot proceed with the upgrade (as I do not want to rollback).
So what exactly can I do in this situation? any help would be appreciated
aa

What Olaf said Or if possible change compatibility level of database to 100 and try. I guess since you want to upgrade there wont be any issue in changing. Well if anything happens you can safely change it back to 80
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

SQL Server reporting services error "URl has already been reserved" while doing upgrade from SQL server 2008 R2 to SQL server 2012

"URl has already been reserved".
Reporting services for port 80 and 443 works fine both for reports and reportingserver on SQL server 2008 R2. But when I try to upgrade from SQL server 2008 R2 to 2012 this error pops up. How to make sure before upgrading regarding reporting services that
URL reserves and SSL are fine or how to fix reporting services are upgrade like repair install.
Thanks

Hi yashmitl,
In your case, please running the following command to check the current URL reservations on http.sys.
netsh http show urlacl
Then, please delete the URL reservation by executing the following command try to resolve the issue.
netsh http delete urlacl <url>
There is a similar issue, you can refer to it.
http://social.technet.microsoft.com/Forums/en-US/d5204dd3-e26d-4592-8ef0-a94005fc46a5/the-url-has-already-been-reserved?forum=sqlreportingservices
Hope this helps.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

Upgrading SQL Server from 2008 to 2012 doesn't respect existing install / instance paths

Basic Information : Running Microsoft Windows Server 2008 with MS SQL Server 2008 (version 10.0.5869), trying to upgrade to SQL Server 2012. Currently working in a cloned
VM of our production server (so I can try things and not worry about affecting our production system).
Current server setup:
C Drive: Operating System (About 7 GB of 50 GB free)
J Drive: Program Files (About 65 GB of 78 GB free)
F Drive: SQL Databases (About 120 GB of 195 GB free)
Issue: I am trying to do an upgrade of our existing MS SQL Server 2008 install. I am using the GUI method, and choosing "Upgrade from SQL Server, 2005, SQL Server
2008, or SQL Server 2008 R2" in the Setup GUI:
All the checks & rules run with no issues. When I get to the "Instance Configuration" screen in the setup GUI, it is not respecting where my SQL Server instance is already installed (which is on the J drive). Instead it wants to install EVERYTHING
(including Instance Directory, which should be on the F drive, and the install folder, which should be on the J drive) on the C drive under C:\Program Files\ and there is no option in the GUI to change that, as it's grayed out.
I tried using a Configuration File to do the upgrade, but when I tried to specify the specific paths, it says those variables are not allowed to be used in an upgrade. If I allow the install to go through, it seems to install fine, but only leaves me with about
1.5 GB free on the OS drive (Drive C) and all of SQL Server is now installed on Drive C, which is not what I want or need.
Looking in the Registry Editor, I can see that under HKLM\SOFTWARE\Microsoft\Microsoft
SQL Server\MSQL11.MSSQLSERVER\ that the SqlProgramDir key
has changed from "F:\" to "C:\Program Files\Microsoft SQL Server\" and that the SQLPath and SQLDataRoot have
changed from "F:\MSSQL10.MSSQLSERVER\MSSQL" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL". SQLBinRoot has
also been changed "F:\MSSQL10.MSSQLSERVER\MSSQL\Binn" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn".
It doesn't seem to want to follow where the existing Install and Instance Directories are. Am I missing something here? I've done a decent amount of research, but can't find anything that talks about this. So I'm at a loss as to what to do from here.

I haven't touched the registry. Here is the ConfigurationFile.ini from the original install (I've scrubbed sensitive info out of it) showing the paths:
;SQLSERVER2008 Configuration File
[SQLSERVER2008]
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.
INSTANCEID="MSSQLSERVER"
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.
FEATURES=SQLENGINE,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Setup will not display any user interface.
QUIET="False"
; Setup will display progress only without any user interaction.
QUIETSIMPLE="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="False"
; Specify the root installation directory for native shared components.
INSTALLSHAREDDIR="J:\Program Files\Microsoft SQL Server"
; Specify the root installation directory for the WOW64 shared components.
INSTALLSHAREDWOWDIR="J:\Program Files (x86)\Microsoft SQL Server"
; Specify the installation directory.
INSTANCEDIR="F:"
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
SQMREPORTING="False"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).
INSTANCENAME="MSSQLSERVER"
; Agent account name
AGTSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Auto-start service after installation.
AGTSVCSTARTUPTYPE="Automatic"
; Startup type for Integration Services.
ISSVCSTARTUPTYPE="Automatic"
; Account for Integration Services: Domain\User or system account.
ISSVCACCOUNT="NT AUTHORITY\SYSTEM"
; The name of the account that the Analysis Services service runs under.
ASSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Controls the service startup type setting after the service has been created.
ASSVCSTARTUPTYPE="Automatic"
; The collation to be used by Analysis Services.
ASCOLLATION="Latin1_General_CI_AS"
; The location for the Analysis Services data files.
ASDATADIR="F:\MSAS10.MSSQLSERVER\OLAP\Data"
; The location for the Analysis Services log files.
ASLOGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Log"
; The location for the Analysis Services backup files.
ASBACKUPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Backup"
; The location for the Analysis Services temporary files.
ASTEMPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Temp"
; The location for the Analysis Services configuration files.
ASCONFIGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Config"
; Specifies whether or not the MSOLAP provider is allowed to run in process.
ASPROVIDERMSOLAP="1"
; Specifies the list of administrator accounts that need to be provisioned.
ASSYSADMINACCOUNTS=""
; Startup type for the SQL Server service.
SQLSVCSTARTUPTYPE="Automatic"
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
FILESTREAMLEVEL="0"
; Set to "1" to enable RANU for SQL Server Express.
ENABLERANU="False"
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"
; Account for SQL Server service: Domain\User or system account.
SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Windows account(s) to provision as SQL Server system administrators.
SQLSYSADMINACCOUNTS=""
; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication.
SECURITYMODE="SQL"
; Provision current user as a Database Engine system administrator for SQL Server 2008 Express.
ADDCURRENTUSERASSQLADMIN="False"
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
TCPENABLED="1"
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
NPENABLED="0"
; Startup type for Browser Service.
BROWSERSVCSTARTUPTYPE="Disabled"
; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
RSSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled
RSSVCSTARTUPTYPE="Automatic"
; Specifies which mode report server is installed in.
; Default value: “FilesOnly”
RSINSTALLMODE="DefaultNativeMode"

Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014

Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014 ?

What sort of databases do you have OLTP? Data warehouse? What requirements do you have for High Availability?
The main features for SQL 2012/2014, as I see it:
o Support for window functions, which makes it possible to write fast queries for running totals, sliding windows etc.
o Columnstore indexes, which can speed up your data warehouse enormously. But of no interest for OLTP. Only writable in SQL 2014.
o AlwaysOn and Availability Groups, a vastly improve story for high availability and disaster recovery.
o try_convert/try_cast, you can now easily filter out values from a column which does not convert to a number. A small but essential feature.
o In memory-OLTP, a new in-memory engine in SQL 2014. This far with very limited feature set, and quite specialised.
Of the points above, the second and third require Enterprise Edition, the first and fourth are in all editions. For the last, I don't think Microsoft has announced anything yet.
There are also new stuff in the BI area, but that's out of my league.
And, oh, there is a new licensing model - which I think is holding more than one customer back.
Erland Sommarskog, SQL Server MVP, [email protected]

Want to know what is improvement in FILEstram storage feature from SQL SERVER 2008 to SQL SERVER 2014

Hi All ,
want to know what is improvement in FILEstram storage feature from SQL SERVER 2008 to SQL SERVER 2014
Regards,
Manish

Hello Manish,
See
What's New in SQL Server 2012
What's New in SQL Server 2014
Nothing really new around that feature.
Olaf Helper
[ Blog] [ Xing] [ MVP]

MOSS 2007 SP1 & SQL Server 2008 upgrade plan into MOSS 2010 and SQL Server 2008 R2 ?

Hi All,
I've got the following setup in one single server:
Windows Server 2008 Standard
SQL Server 2008 Standard
SharePoint Server 2007 Enterprise SP1
that I'd like to upgrade into the following:
Windows Server 2008 R2 Standard
SQL Server 2008 R2 SP1 ?
SharePoint Server 2010 Enterprise
can i just perform CA farm level backup then import it on the new SharePoint server ? is there any caveat that i should pay attention to ? (eg. non working site list or web parts ? )
thanks.
/* Infrastructure Support Engineer */

Backup/import will not work for upgrade. As mentioned on the other thread, you need to perform a database attach upgrade to move to a separate 2010 from from a 2007 farm. For information about upgrading to SharePoint Server 2010, see the upgrade guide:
http://technet.microsoft.com/en-us/library/cc303420.aspx

Upgrade sql server 2008 to 2014

Similar Messages

Maybe you are looking for