I have tried fillfactors of 0 (default), 50% and 25% and I have not seen any change in performance, page splits or fragmentation. I've also tried removing all the...

Changing the PRIMARY KEYS to NONCLUSTERED has made no difference at all. I am seeing the exact same performance, page splits and indexx fragmentation.

1. no triggers

2. no constraints

In fact, there is nothing in the schema except for tables and indexes.

The fillfactor default is not 50%, it's 0 or 100 which basically amount to...

Yip, there are no blocking locks or deadlocks.

The primary reason for this data load was so that I would have data to test queries with but the process of loading...

No, I can't do that. The database is going to be in production and the indexes will be required. I understand your point though, if this was a...

quite bizarre. Even after changing the fillfactor to 50%, I am getting a lot of page splits and my indexes are still fragmented after only a couple of minutes...

I think with the high number of page splits I am seeing couple with the high percentage of fragmentation, I am going to mess with the fillfactor. There doesn't...

My data load is loading a lot of data in quick order. I think I have done an OK job of sizing the files, is it possible for me...

The files are set to allow autogrowth but I sized them so that they don't need to grow. I also just checked and each file still has plenty of...

There are actually as many as 5 tables tables being populated and they do have a bunch of indexes on them. The data load consists of only inserts. ...

Thanks, Scott. That's what I did. I took all the "other" indexes and put then in the [indexes] group while leaving the PK in [tables].

Thanks for the response!

Cheers, Max