Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DavidChel
Constraint Violating Yak Guru
474 Posts |
 Posted - 2008-12-22 : 15:27:23
|
I tried google, but didn't have much luck. What does all this mean? PRIMARY KEY CLUSTERED ([FKey_ID] ASC)WITH FILLFACTOR = 100 ON [PRIMARY])ON [PRIMARY]TEXTIMAGE_ON [PRIMARY]; |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
DavidChel
Constraint Violating Yak Guru
474 Posts |
Posted - 2008-12-22 : 15:40:06
|
quote:
Originally posted by tkizerthe index has a fill factor of 100% and everything is to be put on the primary file group.
Great, can someone now explain the explanation I've quoted?  |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-12-22 : 15:41:37
|
From BOL:quote:
The fill factor option is provided for fine-tuning index data storage and performance. When an index is created or rebuilt, the fill factor value determines the percentage of space on each leaf level page to be filled with data, therefore reserving a percentage of free space for future growth. For example, specifying a fill factor value of 80 means that 20 percent of each leaf-level page will be left empty providing space for index expansion as data is added to the underlying table.The fill factor value is a percentage from 1 to 100. The server-wide default of 0 is the optimal choice in the majority of situations. When fill factor is set to 0, the leaf level is filled to capacity.
You always have the primary filegroup. If you haven't created any additional filegroups, then all of your objects are stored on primary.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
DavidChel
Constraint Violating Yak Guru
474 Posts |
Posted - 2008-12-22 : 15:54:47
|
| Thanks Tara. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
Can someone please explain this?