Huge amount of Staging logs when sorting large Custom Tables

My initial thought would be what logic are you using to manually determine the order? Can you do something else other than ItemOrder for sorting and then when you use the data add an order by some other column than ItemOrder.

If not, not sure if staging would be the best way to sync this data because it's going to have to create an update task for each item that was changed. If it is creating multiple tasks for each item, you might be able to reduce that to just a task for each item in its last order.

You might want to look into compare for Kentico, might speed syncing things up.

Lastly, you might be able to build something custom to sync the data, using something like Red Gate's SQL compare.

At the moment I'm using standard Custom Table ordering, nothing more. But the data in the tables has a strange orering... some items must be in the beginning, with a custom order field (some, it's sometimes hundreds) and the other is automatically ordered afterwards.

I can think of other scenarios where ordering manually huge a table is important, and the issue becomed annoying even with just 50 rows in the table.

If there was a drag&drop interface with 1 synch operation for drag&drop action, it would be totally fine, but as I wrot it seems Kentico doesn't support it.

Compare for Kentico and other DB aligning solutions are way to complex to manage something like this, that I consider should have been thought of when designing the feature.

Nevertheless, I'll try to create a custom layout and a module as I described above. It's a little shame, since it'll be overly time consumed. It seemed strange to me this kind of issue has never been considered, and I was hoping in a built-in solution.

So, in the end I couldn't solve this in an elegant way, but I implemented a temporary solution that may help someone else, in the future. So, I simply attached a Custom Handler to the ChangeOrder event, inside which I check for the tables I want to prevent staging synchronization during change order of elements, and simply turn off the logging for the request. It'll still log Create, Update, Delete events in table, so it'll not affect functioality too much.

Downsize is that, to appluy the sorting of elements to the next enviroment through Staging, once you finish to sort the elements you need to manually synch the entire Custom Table object. This takes just a couple of seconds, even for 500 rows, so it's not a huge issue for me.

Next step will be creating a custom layout for those tables, and adding a "Synch entire table" button at the top ;) Hope this'll help anyone trying to address the same issue.

using CMS.Base;
using CMS.CustomTables;
using CMS.DataEngine;
using CMS.DocumentEngine;
using CMS.EventLog;
using CMS;

[assembly: RegisterModule(typeof(CustomHandlerModule))]
public class CustomHandlerModule : Module
{    
    public CustomHandlerModule() : base("CustomHandlerModule") { }

    protected override void OnInit()
    {   
        base.OnInit();
        EventLogProvider.LogInformation("Manage_ChangeOrder", "INFORMATION", "Custom Handler begin Init");                 
        ObjectEvents.ChangeOrder.Before += Manage_ChangeOrder;                    
    }

    private void Manage_ChangeOrder(object sender, ObjectChangeOrderEventArgs e)
        {           
            string tablename = e.Object.TypeInfo.ObjectType.ToLower();
            EventLogProvider.LogInformation("Manage_ChangeOrder", "INFORMATION", string.Format("Tablename {0}",tablename ));

            switch(tablename)
            {
                /*Use [namespace].[classname] from your custom table*/
                case "customtableitem.[namespace].[classname]": e.Using(new CMSActionContext(){LogSynchronization = false});break;
                /*other cases for other tables to manage, here*/
                default: break;
            }
        }
}