upgrade from SQL 2008 SP3 to SQL server 2014 with SP1

SQL Server 2014 Software Requirements

SQL Server 2014 also has a few software requirements beyond the base operating system. The primary software requirements are:

The .NET Framework 3.5 SP1 is required when you select Database Engine, Reporting Services, Master Data Services, Data Quality Services, Replication, or SSMS. This is not installed by the SQL Server setup process.
The .NET Framework 4.0. This is installed by the SQL Server setup process.
PowerShell 2.0 or higher is required if you have installed the database engine or SSMS.
The Windows Installer service must be running.
For more information about the prerequisites for installing SQL Server 2014 you can refer to Hardware and Software Requirements for Installing SQL Server 2014.

Upgrading Using the SQL Server Installation Wizard

http://sqlmag.com/sql-server-2014/migrating-sql-server-2014

noon.

reserve keyword means what application has to modify before it runs good on new SQL server.

reserve keyword means what application has to modify before it runs good on new SQL server.

If things are done properly you should have all the code in the SQL Server side (mainly functions and stored procedures) so the MSSQL 2014 Upgrade Advisor can verify the code and warn you about things that won't work if you migrate.

If you have SQL code in your application I don't think there's an utility that can check it for you, so the best thing to do is to create a development environment with the application working with a copy of the database migrated to MSSQL 2014. Then a complete test should be performed to guarantee that the application works properly with the new database version.

"If things are done properly you should have all the code in the SQL Server side (mainly functions and stored procedures) so the MSSQL 2014 Upgrade Advisor can verify the code and warn you about things that won't work if you migrate."

but we want to do it earlier and our SQL server 2014 server not here yet.

"If you have SQL code in your application I don't think there's an utility that can check it for you, so the best thing to do is to create a development environment with the application working with a copy of the database migrated to MSSQL 2014."

yes, this is another option. by the experience of MySQL upgrade, we need to have reserve keyboard and a test platform for developer to deploy the same code to test it .

"Then a complete test should be performed to guarantee that the application works properly with the new database version. "

what complete test you mean by this ?

but we want to do it earlier and our SQL server 2014 server not here yet.

You don't need to have MSSQL 2014 to run the Upgrade Advisor. Download it from here and run it against you MSSQL 2008 instance.

what complete test you mean by this ?

Means that you need to go through ALL options in you application so you don't miss nothing.

"You don't need to have MSSQL 2014 to run the Upgrade Advisor. Download it from here and run it against you MSSQL 2008 instance."

ah,,, I just recall that you are doing this project, very good.  

"Means that you need to go through ALL options in you application so you don't miss nothing. "

basically setup a test platform and let them test it is already that, just open that and let then test it.

so reserved keyword you mean no necessary ?

basically setup a test platform and let them test it is already that, just open that and let then test it.

Absolutely correct.

so reserved keyword you mean no necessary ?

I'm not sure if I understood the question. Can you give me examples of reserved keyword?

"I'm not sure if I understood the question. Can you give me examples of reserved keyword? "

like which T-SQL function still exists on new version of SQL server, etc, so that their SP is not going to fail because they used some function depreciated.

but that one is not SQL 2014, right?

"Anyway, there's almost no changes from MSSQL 2012 to MSSQL 2014 in T-SQL area. "


that's why ?

Yes and yes. Don't forget that What's New section it's always related to the last version, so you'll need to check first in MSSQL 2012 to be aware what's new from MSSQL 2008.

"Yes and yes. Don't forget that What's New section it's always related to the last version, so you'll need to check first in MSSQL 2012 to be aware what's new from MSSQL 2008."

I am confused but that link only show up to SQL 2012, so we can only see any thing change up to 2012 from 2008 ?

I am confused but that link only show up to SQL 2012, so we can only see any thing change up to 2012 from 2008 ?

Correct. I also added in the same comment the link for What's new in MSSQL 2014 so you can compare.

"I didn't referred What's new on MSSQL 2014 in purpose because there you can see only new things related to MSSQL 2012 and not MSSQL 2008. Anyway, there's almost no changes from MSSQL 2012 to MSSQL 2014 in T-SQL area."

but that one more on DBA side other than programmer side.