Jeff Moden (8/27/2013)
BrerSQL (8/26/2013)
Sequential GUIDs definitely would make sense.I'm not so sure that's true. If the computer is re-booted, the start of a new sequence might not be > the largest guid already in the table. I think you could end up with massive page splits anyway.
Keep in mind this is an Application Session DB.
If the server is re-booted and we experience a planned or unplanned outage as a result, then all rows in this table are useless as this data maintains current application session state. We could truncate the table on startup to off set this issue.
This particular server should rarely go down.
Actually on second thought, FILL FACTOR may not work very well for a table like this unless we perform frequent INDEX REBUILDS.
Note: We have found a VLF issue for this database which could be causing our WRITELOG latency issue. The VLF issue was prety severe. I am in the process of rebuilding this DB with an optimal number/Size of VLF's for this database. I am hoping that we may see an improvement, at least until I can move session off of the server.