opc.three (10/9/2012)
Appropriate for all? No. Pick a spot, maybe 90, monitor fragmentation, and adjust up or down.
Will do that... the problem is that our SW is installed on several customers with different work methodology, we can have customers with 100 rows per table, 1.000 or 10.000 and even 1.000.000.
But since the ones that complaint are the ones with large databases probably it's worth just looking into those cases..
I would be careful using a variable length column in a PK, especially if their values are not static. Test, test, test.
Our PK are usually always INT IDENTITY or GUID, never a NVARCHAR.
We only have indexes over columns with NVARCHAR but not PKs. All lookups, FKs, are made usings INTs or GUIDs
Thanks,
Pedro