mrpolecat,

1st, if you stick to PK then create it before uploading data.

In this case it will insert directly into index, no wasting time for reordering already loaded rows.

And make sure...

RD, does your application begin a transaction when user starts editing the cell?

One thing I can say for sure:

if the system requires 140 million rows downloads every week just to check if there are any changes then it was designed mindlessly.

Index is not a magic wand.

Sometimes quality of design and queries is important as well.

😎

Hard to believe, but PK is an index.

Jez, same advice to you.

Would you mind to open Book on Line and read about aggregate system functions?

COUNT, SUM, etc.

Then use double quotes instead of brackets..

Try to remove brackets from the script.

It's probably the code of your trigger.

Can you post it here?

You can simply show by which column(s) to order:

ORDER BY 1

- orders by 1st column in returning recordset;

ORDER BY 2, 3

- orders by 2nd, them 3rd column in recordset

ORDER BY...

This must be divided into tables:

cn

instanceType

nTSecurityDescriptor

- Instance

objectCategory

objectClass

objectSid

- Object

sAMAccountName

accountExpires

accountNameHistory

aCSPolicyName

- Account

adminCount

adminDescription

adminDisplayName

allowedAttributes

allowedAttributesEffective

allowedChildClasses

allowedChildClassesEffective

- AccountAdmin (not sure, names are not clear)

altSecurityIdentities

assistant

badPasswordTime

badPwdCount

- AccountSecurity

bridgeheadServerListBL

c

canonicalName

catalogs

co

codePage

- ???

etc.

I see at least 15 tables here.

But I can only guess here, without...

halifaxdal,

There is no smart way to deal with stupid design.

255 columns in a table is a clear sign of stupid design.

This thing must be fixed first.

{F1} on your keyboard.

You know, it's not the company I want to be surrounded with.

:hehe: