Legacy application compatibility on SQL Server 2014 with in Memory computing

Posted on 2015-02-10
Medium Priority
Last Modified: 2015-02-12
I would like some experts to comment on and give me some reference links on the following questions.

I know what In memory computing can do to transaction processing and querying in databases and I am looking forward to testing some applications on SQL Server 2014 - that has in memory computing ability.

Q 1   - Generally speaking - if a application that normally runs on SQL 2012 - would it need significant changes to run on SQL 2014 ( or any at all ).
Q2 - reated to Q1,  I mean I am expecting regardless of in memory or not ,  applications could query/update SQL server 2014 data as it used to do on SQL 2012 ?
Q3 - I read somewhere that you can ( the DBA ) nominate some tables to run in memory - does this mean to get the benefit of in memory computing of SQL 2014 - does the DBA have to do the "tweaks" ?

Thanks and reference URLs would b great.
Question by:indikad
  • 2
  • 2
LVL 24

Accepted Solution

Phillip Burton earned 2000 total points
ID: 40602653
Q1 - If an application runs in SQL 2012, it should run in SQL 2014 with few if any changes. However, that is not necessarily true of "in memory", whcih is not switched on by default.
Q2 - See Q1.

Please note that in memory computing has some limitations - see this article and scroll down to "Limitations".

Note particularly that certain types of data types are not supported, and that FOREIGN KEY, CHECK, UNIQUE and IDENTITY are not supported, among others.

Q3 - Yes. It's more than "tweaks" - see thithis article for more details.

Author Comment

ID: 40604574
Hi Phillip,

Thanks for the information it really helps.
Meanwhile I have been reading some articles as well.

With the "Limitations" does that apply ONLY to the In Memory enables editions ? what is your understanding ?  ( I believe SQL standard does not contain In Memory capability ).
LVL 24

Assisted Solution

by:Phillip Burton
Phillip Burton earned 2000 total points
ID: 40605156
No, the "Limitations" apply to tables which are In Memory enabled. It is not enabled by default.

Out of the box, those Limitations do not exist with tables which are not In Memory. They didn't make SQL Server 2014 to make it non-compatible with SQL Server 2012. It's just that there is extra functionality IF YOU WANT IT. If you don't, those limitations do not exist.

Author Closing Comment

ID: 40605265
Thank you.

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Microsoft Access has a limit of 255 columns in a single table; SQL Server allows tables with over 255 columns, but reading that data is not necessarily simple.  The final solution for this task involved creating a custom text parser and then reading…
There is a wide range of advantages associated with the use of ASP.NET. This is why this programming framework is used to create excellent enterprise-class websites, technologies, and web applications.
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.

624 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