We have a vendor app that has a SQL Server 2005 database. During data entry, app writes data to a table that has no clustered indexes on it. It has a number of indexes on the table, though.
I used the Maintenance Plan wizard to rebuild the indexes on that table.
During performance testing, we started running into deadlock issues. The deadlock graph shows that this particular table without a clustered index is the one being contended for.
I then used the Maintenance Plan wizard to rebuild the indexes with fillfactor 80. No deadlocks now. Any ideas why this fillfactor would make a difference?