Hi,

We are using LLBLGen v. 3.1 Final (released March 12th, 2012) with a custom driver provided by you in this thread (https://www.llblgen.com/tinyforum/Attachments.aspx?SourceType=1&MessageID=130864) .

We currently upgraded our .NET Framework from v 3.5 to v 4.5 and or SQL Servers from 2008 R2 to 2014.

We are having some performance problems (mainly with the Database) after this upgrade and we were wondering if some of them might be caused by the SqlServerDQECompatibilityLevel (which is set to 2005 / 2008 ).

Is there any way possible to setup our current version of LLBLGen to use compatibility mode for SQL 2014 to see if this fixes anything?

We are currently investigating the breaking changes that occured after this release, but this might take a while in our case.

Thanks in advance,

Florin

SqlServerCompatibilityLevel.SqlServer2012 (=6), exists from v.3.5.

Could you please test with LLBLGen v.3.5 (that's a free and smooth migration), at least for testing this issue?

Also could you please shed some light on the performance problems.

Hi Walaa,

Can I use the same Trial licence I got for v. 4.2 for v. 3.5? I want to try to upgrade the LLBLGen version to see if this fixes my problems.

Also I saw that one of the braking changes for 3.5 is that some signatures from CommonEntitiBase have been modified (Ex. using IEntitiCore instead of IEntity and IEntity2). I need to fix this code manually or it will be regenerated in the new format?

Thanks in advance,

Florin

Florin wrote:

Hi Walaa,

Can I use the same Trial licence I got for v. 4.2 for v. 3.5?

No, but you can upgrade to 3.5 without charge, as you have a 3.x license.

I want to try to upgrade the LLBLGen version to see if this fixes my problems.

Also I saw that one of the braking changes for 3.5 is that some signatures from CommonEntitiBase have been modified (Ex. using IEntitiCore instead of IEntity and IEntity2). I need to fix this code manually or it will be regenerated in the new format? Florin

The change you refer to has effect on your own code, but chances are you don't run into that at all.

The change introduced for the compatibility level is for sqlserver 2012 (and thus 2014), which is about paging: it will create a simpler paging query. However if the slowness isn't regarding the CTE paging system used in the 2005 compatibility level (the one that's the default, so use that instead of 6 in your 3.1 code!) it won't make a difference to move to 2012 compatibility level.

First profile what is really slow, then figure out what causes that particular bottleneck.