Paging performance problem with huge data

Posts   
 
    
nevernet
User
Posts: 67
Joined: 01-Feb-2010
# Posted on: 16-Nov-2011 04:14:08   

Hello

the LLBLGen version is 2.6 i just found that it's not using row_number to paging, it was created template table to paging

the code looks like:


void BindData()
    {
        DS.FilterToUse = GetFilter();
        DS.SorterToUse = GetSorter();

        DS.Refetch = true;

        DS.DataBind();

        upList.Update();
    }

the DS is LLBLGen datasource control, and it will be used for GridView.

if there a way to improve the performance?

Thank you

Walaa avatar
Walaa
Support Team
Posts: 14983
Joined: 21-Aug-2005
# Posted on: 16-Nov-2011 09:11:14   

Do you have "SqlServerDQECompatibilityLevel" set anywhere in your application configuration file?

Did you Enable Paging on the LLBLGenProDataSource?

nevernet
User
Posts: 67
Joined: 01-Feb-2010
# Posted on: 18-Nov-2011 03:56:34   

the follow description is from Manual:

DQE Compatibility mode(SqlServer only) With the arrival of SqlServer 2005 and its new features, it was required to make the SqlServer DQE be configurable so it could generate SQL which was optimal for the database type used. To set the compatibility mode of the SqlServer DQE in the .config file of your application, add the following element to the appSettings section of your application's .config file:

<add key="SqlServerDQECompatibilityLevel" value="number" />

where number is either 0, 1 or 2: 0 for SqlServerCompatibilityLevel.SqlServer7 1 for SqlServerCompatibilityLevel.SqlServer2000 2 for SqlServerCompatibilityLevel.SqlServer2005 3 for SqlServerCompatibilityLevel.SqlServerCe3x (Sqlserver CE 3.0 and 3.1) 4 for SqlServerCompatibilityLevel.SqlServerCe35

The default is 1, or SqlServer2000 so omitting this tag will result in the SqlServer 2000 compatibility mode. Setting the compatibility level controls the sequence retrieval logic to use by default (@@IDENTITY on Sqlserver 7 or SCOPE_IDENTITY() on 2000/2005), the ability to use NEWSEQUENTIALID() (SqlServer 2005) and the SQL produced for a paging query: a temptable approach is used on SqlServer 7 or 2000, and a CTE approach is used on SqlServer 2005.

why there is no option for SQLServer 2008?

Thank you

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 18-Nov-2011 05:36:00   

nevernet wrote:

why there is no option for SQLServer 2008?

SqlServerCompatibilityLevel.SqlServer2005 is for 2005 and also for 2008/2008 R2, which doesn't require a separate compatibility level.

David Elizondo | LLBLGen Support Team
nevernet
User
Posts: 67
Joined: 01-Feb-2010
# Posted on: 18-Nov-2011 05:52:13   

Got it, Thank you very much!

nevernet
User
Posts: 67
Joined: 01-Feb-2010
# Posted on: 22-Nov-2011 02:22:43   

this is a problem i have already tagged this post as resolved, but when someone replied this post, it was become to unsolved.

is it right?

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 22-Nov-2011 05:06:15   

nevernet wrote:

this is a problem i have already tagged this post as resolved, but when someone replied this post, it was become to unsolved.

is it right?

Yes, when someone post the thread is re-opened, this is to ease things for you if you want to back to the issue. We also stayed in the guidelines that people should not re-open old or solved threads.

Unfortunately the spammers won't follow the guidelines disappointed

David Elizondo | LLBLGen Support Team