• There is no "magic number" for fill factor, as it depends of your Index and table's activity. If the Index is static, I would recommend leaving default fill factor. If not, start with 80 or something like that and keep and eye on fragmentation every week. You will see how much your weekend's job is helping with the new FILL factor.

    In terms of rebuilding Indexes with less than 1k pages, forcing a rebuild on those shows little or no effect in performance gain, so do not worry about those. Skipping those will have no side effects. If you Google it, you will find lot of Microsoft articles about it.

    Last but not least, why reinvent the wheel? 🙂 ... unless you are really bored, there are tons of awesome solutions online for Index Maintenance and jobs. My favorite is Ola's solution. Here's the link:

    http://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html

    It creates smart jobs. So it will skip those Indexes with low page count of low fragmentation. You can also put your own parameters or customize. It keep a history of the job's activity.

    Have fun!