SQL 2014 E10? Blank Title 131993


The SQL 2014 in-memory OTLP engine does not work with Epicor ERP tables, today.  We did some prototyping and got some good results in the posting engine, but the changes are pretty invasive and need to go through some significant design/dev/test.  That said, we like what we saw.

The in-memory OLTP engine is only available in the Enterprise Edition of SQL Server, which is diabolically expensive.  Also, the tables you put in memory can't have columns with off-page types (nvarbinary, ntext, etc.) or even rowversion (timestamp) columns.  The indexes also have to be re-thought (no clustered indexes).  And then the locking constructs are different too.  

So, you can't just move some tables to memory and watch the system run faster.  For Epicor, there is a lot of code rework we have to do -- and we have to make sure the system still works on regular editions of SQL Server.  All that said, we see benefits and we are working on defining a "SQL Enterprise deployment option" that would install some optimizations unique to SQL Enterprise. But it's not on our delivery roadmap yet -- hopefully we can get more scoping work done soon and then we can work out a delivery plan. 

But one thing you might investigate is Buffer Pool Extensions.  This SQL 2014 feature lets you allocate space on an SSD which SQL will use for memory expansion (kind of like Windows Vista attempted to do with memory sticks).  But if your system is already fully SSD and/or you have a FusionIO board, it won't make a difference. All of our test rigs are either 100% HDD or have FusionIO + SSD, so we haven't done any testing yet.  But BPE is available in all editions of SQL Server.




Anyone know if E10 will be fine with SQL 2014? Microsoft is being a bit overzealous in their licencing...

Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

E: jose@...
http://www.josecgomez.com

     Â


Quis custodiet ipsos custodes?

Can you use SQL 2014?

 

My reason for asking….

 

I was in the beta program for E10 and had an issue with the initial install. I had SQL Server 2012 on Windows Server 2008R2…

 

Tech said the issue was due to a version mismatch. They recommend matching the version\

Year of SQL with windows server. To my knowledge, Windows server 2014 is not out…

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 10:51 AM
To: Vantage
Subject: [Vantage] SQL 2014 E10?

 

 

Anyone know if E10 will be fine with SQL 2014? Microsoft is being a bit overzealous in their licencing...


Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

They recommend matching the version\Year of SQL with windows server.

 

 

That is quite possibly the most ridiculous thing I have ever heard.

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 10:56 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?

 




Can you use SQL 2014?

 

My reason for asking….

 

I was in the beta program for E10 and had an issue with the initial install. I had SQL Server 2012 on Windows Server 2008R2…

 

Tech said the issue was due to a version mismatch. They recommend matching the version\

Year of SQL with windows server. To my knowledge, Windows server 2014 is not out…

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 10:51 AM
To: Vantage
Subject: [Vantage] SQL 2014 E10?

 

 

Anyone know if E10 will be fine with SQL 2014? Microsoft is being a bit overzealous in their licencing...


Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 




It is in the install guide. I know it sounds crazy but it solved my issue!

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 11:12 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?

 

 

They recommend matching the version\Year of SQL with windows server.

 

 

That is quite possibly the most ridiculous thing I have ever heard.

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 10:56 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?

 





Can you use SQL 2014?

 

My reason for asking….

 

I was in the beta program for E10 and had an issue with the initial install. I had SQL Server 2012 on Windows Server 2008R2…

 

Tech said the issue was due to a version mismatch. They recommend matching the version\

Year of SQL with windows server. To my knowledge, Windows server 2014 is not out…

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 10:51 AM
To: Vantage
Subject: [Vantage] SQL 2014 E10?

 

 

Anyone know if E10 will be fine with SQL 2014? Microsoft is being a bit overzealous in their licencing...


Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 





I hope Windows switches to releasing server on odd years and SQL on even years just to bug Epicor….

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 8:14 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?


It is in the install guide. I know it sounds crazy but it solved my issue!

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 11:12 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?


They recommend matching the version\Year of SQL with windows server.


That is quite possibly the most ridiculous thing I have ever heard.

From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 10:56 AM
To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
Subject: RE: [Vantage] SQL 2014 E10?






Can you use SQL 2014?

My reason for asking….

I was in the beta program for E10 and had an issue with the initial install. I had SQL Server 2012 on Windows Server 2008R2…

Tech said the issue was due to a version mismatch. They recommend matching the version\
Year of SQL with windows server. To my knowledge, Windows server 2014 is not out…

From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 10:51 AM
To: Vantage
Subject: [Vantage] SQL 2014 E10?


Anyone know if E10 will be fine with SQL 2014? Microsoft is being a bit overzealous in their licencing...

Jose C Gomez
Software Engineer

T: 904.469.1524 mobile
E: jose@...<mailto:jose@...>
http://www.josecgomez.com
[Image removed by sender.]<http://www.linkedin.com/in/josecgomez> [Image removed by sender.] <http://www.facebook.com/josegomez> [Image removed by sender.] <http://www.google.com/profiles/jose.gomez> [Image removed by sender.] <http://www.twitter.com/joc85> [Image removed by sender.] <http://www.josecgomez.com/professional-resume/> [Image removed by sender.] <http://www.josecgomez.com/feed/>

Quis custodiet ipsos custodes?









[Non-text portions of this message have been removed]
What? that is insane what does the Windows Version have to do with SQL... someone was high when they wrote the docs. Sigh


Jose C Gomez
Software Engineer



T: 904.469.1524 mobile

E: jose@...
http://www.josecgomez.com

     Â


Quis custodiet ipsos custodes?


On Fri, Aug 22, 2014 at 12:01 PM, 'Tom J. Christie' tchristie@... [vantage] <vantage@yahoogroups.com> wrote:

Â
<div>
  
  
  <p>I hope Windows switches to releasing server on odd years and SQL on even years just to bug Epicor….


Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 8:14 AM

To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?


It is in the install guide. I know it sounds crazy but it solved my issue!

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 11:12 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?


They recommend matching the version\Year of SQL with windows server.


That is quite possibly the most ridiculous thing I have ever heard.



From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com]


Sent: Friday, August 22, 2014 10:56 AM


To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>


Subject: RE: [Vantage] SQL 2014 E10?







Can you use SQL 2014?

My reason for asking….

I was in the beta program for E10 and had an issue with the initial install. I had SQL Server 2012 on Windows Server 2008R2…

Tech said the issue was due to a version mismatch. They recommend matching the version\
Year of SQL with windows server. To my knowledge, Windows server 2014 is not out…



From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com]


Sent: Friday, August 22, 2014 10:51 AM


To: Vantage


Subject: [Vantage] SQL 2014 E10?



Anyone know if E10 will be fine with SQL 2014? Microsoft is being a bit overzealous in their licencing...

Jose C Gomez
Software Engineer

T: 904.469.1524 mobile
E: jose@...<mailto:jose@...>
http://www.josecgomez.com
[Image removed by sender.]<http://www.linkedin.com/in/josecgomez> [Image removed by sender.] <http://www.facebook.com/josegomez> [Image removed by sender.] <http://www.google.com/profiles/jose.gomez> [Image removed by sender.] <http://www.twitter.com/joc85> [Image removed by sender.] <http://www.josecgomez.com/professional-resume/> [Image removed by sender.] <http://www.josecgomez.com/feed/>

Quis custodiet ipsos custodes?








[Non-text portions of this message have been removed]

</div>
 


<div style="color:#fff;min-height:0;"></div>

We are running SQL 2014 / Server 2012 in our test environment w/ no issues.

 

Brenda

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 12:14 PM
To: Vantage
Subject: Re: [Vantage] SQL 2014 E10?

 

 

What? that is insane what does the Windows Version have to do with SQL... someone was high when they wrote the docs. Sigh



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 

On Fri, Aug 22, 2014 at 12:01 PM, 'Tom J. Christie' tchristie@... [vantage] <vantage@yahoogroups.com> wrote:

 

I hope Windows switches to releasing server on odd years and SQL on even years just to bug Epicor….

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 8:14 AM

To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?


It is in the install guide. I know it sounds crazy but it solved my issue!

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 11:12 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?


They recommend matching the version\Year of SQL with windows server.


That is quite possibly the most ridiculous thing I have ever heard.

From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com]

Sent: Friday, August 22, 2014 10:56 AM

To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>

Subject: RE: [Vantage] SQL 2014 E10?






Can you use SQL 2014?

My reason for asking….

I was in the beta program for E10 and had an issue with the initial install. I had SQL Server 2012 on Windows Server 2008R2…

Tech said the issue was due to a version mismatch. They recommend matching the version\
Year of SQL with windows server. To my knowledge, Windows server 2014 is not out…

From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com]

Sent: Friday, August 22, 2014 10:51 AM
To: Vantage
Subject: [Vantage] SQL 2014 E10?


Anyone know if E10 will be fine with SQL 2014? Microsoft is being a bit overzealous in their licencing...

Jose C Gomez
Software Engineer

T: 904.469.1524 mobile

E: jose@...<mailto:jose@...>
http://www.josecgomez.com
[Image removed by sender.]<http://www.linkedin.com/in/josecgomez> [Image removed by sender.] <http://www.facebook.com/josegomez> [Image removed by sender.] <http://www.google.com/profiles/jose.gomez> [Image removed by sender.] <http://www.twitter.com/joc85> [Image removed by sender.] <http://www.josecgomez.com/professional-resume/> [Image removed by sender.] <http://www.josecgomez.com/feed/>

Quis custodiet ipsos custodes?








[Non-text portions of this message have been removed]

 

Thanks brenda


Jose C Gomez

Software Engineer


T: 904.469.1524 mobile

E: jose@…

http://www.josecgomez.com
     Â


Quis custodiet ipsos custodes?


On Fri, Aug 22, 2014 at 12:39 PM, brenda mohr brenda@... [vantage] <vantage@yahoogroups.com> wrote:

Â
<div>
  
  
  <p>

We are running SQL 2014 / Server 2012 in our test environment w/ no issues.

Â

Brenda

Â

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 12:14 PM
To: Vantage
Subject: Re: [Vantage] SQL 2014 E10?

Â

Â

What? that is insane what does the Windows Version have to do with SQL... someone was high when they wrote the docs. Sigh



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile

E: jose@...
http://www.josecgomez.com
 Â
   Â


Quis custodiet ipsos custodes?

Â

On Fri, Aug 22, 2014 at 12:01 PM, 'Tom J. Christie' tchristie@... [vantage] <vantage@yahoogroups.com> wrote:

Â

I hope Windows switches to releasing server on odd years and SQL on even years just to bug Epicor….

Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> | tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 8:14 AM

To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?


It is in the install guide. I know it sounds crazy but it solved my issue!

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, August 22, 2014 11:12 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL 2014 E10?


They recommend matching the version\Year of SQL with windows server.


That is quite possibly the most ridiculous thing I have ever heard.

From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com]

Sent: Friday, August 22, 2014 10:56 AM

To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>

Subject: RE: [Vantage] SQL 2014 E10?






Can you use SQL 2014?

My reason for asking….

I was in the beta program for E10 and had an issue with the initial install. I had SQL Server 2012 on Windows Server 2008R2…

Tech said the issue was due to a version mismatch. They recommend matching the version\
Year of SQL with windows server. To my knowledge, Windows server 2014 is not out…

From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com]

Sent: Friday, August 22, 2014 10:51 AM
To: Vantage
Subject: [Vantage] SQL 2014 E10?


Anyone know if E10 will be fine with SQL 2014? Microsoft is being a bit overzealous in their licencing...

Jose C Gomez
Software Engineer

T: 904.469.1524 mobile

E: jose@...<mailto:jose@...>
http://www.josecgomez.com
[Image removed by sender.]<http://www.linkedin.com/in/josecgomez> [Image removed by sender.] <http://www.facebook.com/josegomez> [Image removed by sender.] <http://www.google.com/profiles/jose.gomez> [Image removed by sender.] <http://www.twitter.com/joc85> [Image removed by sender.] <http://www.josecgomez.com/professional-resume/> [Image removed by sender.] <http://www.josecgomez.com/feed/>

Quis custodiet ipsos custodes?








[Non-text portions of this message have been removed]

Â

</div>
 


<div style="color:#fff;min-height:0;"></div>

We are running our test on Win 2012R2 and SQL2014 as well. All seems good so far.

Sorry if this reply gets duplicated -- had some issues posting to the group...


SQL 2014 works fine with ERP 10.  

 

There are no known issues in using any version of SQL Server 2008 R2 or later with any version of Windows Server 2008 R2 or later.  The “matching release years” described in the release requirements simply reflects the configurations Epicor uses for regression testing as well as the rigs we have setup in Product Support to troubleshoot customer problems.

 

Here are two SQL 2014 issues I recall in 10.0.600, both which (I believe) have since been fixed in 10.0.700.0:

 

The Enterprise Search installer set the index DB compatibility to an ancient version of SQL that SQL 2014 does not allow.  The workaround is to create the DB on another machine (maybe using a Developer license of SQL 2012 R2) and then restoring that DB to your SQL 2014 server.

 

The process that creates a new company in an existing ERP database may throw timeout errors on SQL 2014.  This was diagnosed as a change in the query optimizer that poorly handles functions embedded in WHERE expressions:

 

Slow in SQL 2014

select * from a where func(a.b) = @c

 

Fast in SQL 2014

select * from a where a.b = func(@c)

 

This is generally a bad query design anyway, but SQL 2014 really hates the top example.  We’ve patched the query and inspected our code for any other instances in 700 (it’s a very rare pattern in our code).  If you need a workaround, just set the DB compatibility on your ERP database to SQL 2012 and the timeouts go away.  There are no other side-effects in the ERP system for setting the DB compatibility.

 

SQL 2014 works fine with ERP 10 (see below about two known issues). 

 

As far as matching the O/S and SQL versions, there are no known issues in using any version of SQL Server 2008 R2 or later with any version of Windows Server 2008 R2 or later.  The “matching release years” described in the release requirements simply reflects the configurations Epicor uses for regression testing as well as the rigs we have setup in Product Support to troubleshoot customer problems.

 

Here are the two issues I recall in 10.0.600, which have since been fixed in 10.0.700.0:

 

The Enterprise Search installer set the index DB compatibility to an ancient version of SQL that SQL 2014 does not allow.  The workaround is to create the DB on another machine (maybe using a Developer license of SQL 2012 R2) and then restoring that DB to your SQL 2014 server.

 

The process that creates a new company in an existing ERP database may throw timeout errors on SQL 2014.  This was diagnosed as a change in the query optimizer that poorly handles functions embedded in WHERE expressions:

 

Slow in SQL 2014

select * from a where func(a.b) = @c

 

Fast in SQL 2014

select * from a where a.b = func(@c)

 

This is generally a bad query design anyway, but SQL 2014 really hates the top example.  We’ve patched the query and inspected our code for any other instances in 700 (it’s a very rare pattern in our code).  If you need a workaround, just set the DB compatibility on your ERP database to SQL 2012 and the timeouts go away.  There are no other side-effects in the ERP system for setting the DB compatibility.

 

 



This message has been scanned for malware by Websense. www.websense.com

E10 works with SQL 2014 with no issues.at least i know E10.600.3 version of AFR replication,EPM, SC does not work with SQL 2014.

Sorry if this is a duplicate response -- I sent this on Thursday via email, but it looks like it was lost in the plumbing.

SQL 2014 works fine with ERP 10 (see below about two known issues with the ERP 10 GA release). 

 

As far as matching the O/S and SQL versions, there are no known issues in using any version of SQL Server 2008 R2 or later with any version of Windows Server 2008 R2 or later.  The “matching Windows/SQL versions” described in the docs simply reflects the configurations Epicor uses for regression testing as well as the rigs we have setup in Product Support to troubleshoot customer problems. 

 

Here are the two issues I recall in 10.0.600, which have since been fixed in 10.0.700.0:

 

The Enterprise Search installer set the index DB compatibility to an ancient version of SQL that SQL 2014 does not allow.  The workaround is to create the DB on another machine (maybe using a Developer license of SQL 2012 R2) and then restoring that DB to your SQL 2014 server.

 

The process that creates a new company in an existing ERP database may throw timeout errors on SQL 2014.  This was diagnosed as a change in the SQL query optimizer that poorly handles functions embedded in WHERE expressions:

 

Slow in SQL 2014

select * from a where func(a.b) = @c

 

Fast in SQL 2014

select * from a where a.b = func(@c)

 

This is generally a bad query design anyway, but SQL 2014 really hates the top example.  We’ve patched the query and inspected our code for any other instances in 700 (it’s a very rare pattern in our code).  If you need a workaround, just set the DB compatibility on your ERP database to SQL 2012 and the timeouts go away.  There are no other side-effects in the ERP system for setting the DB compatibility.


Thanks Erik very helpful.
Does the memory tables work with epicor? I saw a demo at insights, just wondering if it has been tested
Thanks

On Aug 27, 2014 4:42 PM, "Erik Johnson ejohnson@... [vantage]" <vantage@yahoogroups.com> wrote:

Â
<div>


  <p>

SQL 2014 works fine with ERP 10 (see below about two known issues).Â

Â

As far as matching the O/S and SQL versions, there are no known issues in using any version of SQL Server 2008 R2 or later with any version of Windows Server 2008 R2 or later. The “matching release years” described in the release requirements simply reflects the configurations Epicor uses for regression testing as well as the rigs we have setup in Product Support to troubleshoot customer problems.

Â

Here are the two issues I recall in 10.0.600, which have since been fixed in 10.0.700.0:

Â

The Enterprise Search installer set the index DB compatibility to an ancient version of SQL that SQL 2014 does not allow. The workaround is to create the DB on another machine (maybe using a Developer license of SQL 2012 R2) and then restoring that DB to your SQL 2014 server.

Â

The process that creates a new company in an existing ERP database may throw timeout errors on SQL 2014. This was diagnosed as a change in the query optimizer that poorly handles functions embedded in WHERE expressions:

Â

Slow in SQL 2014

select * from a where func(a.b) = @c

Â

Fast in SQL 2014

select * from a where a.b = func(@c)

Â

This is generally a bad query design anyway, but SQL 2014 really hates the top example. We’ve patched the query and inspected our code for any other instances in 700 (it’s a very rare pattern in our code). If you need a workaround, just

set the DB compatibility on your ERP database to SQL 2012 and the timeouts go away. There are no other side-effects in the ERP system for setting the DB compatibility.

Â

Â



This message has been scanned for malware by Websense. www.websense.com

</div>




<div style="color:#fff;min-height:0;"></div>