1. To view the PK/FK relationships in Enterprise Manager, you can create a
Diagram for the database. It is probably easier to see the PK/FK
relationships in Query Analyzer by running sp_help 'table name' .
2. The text file you attached is a script of all the tables in a particular
database. This can be done using Enterprise Manager as follows:
1. Right-click a database. Choose All Tasks -> Generate SQL Script.
2. Click Show All
3. Select the objects you want to script.
4. Click the Formatting and Options tab to set additional scripting
5. Click OK and save the file.
3. CLUSTERED and FILLFACTOR has nothing to do with a SQL Server/Windows
cluster rather how the indexes in a table are structured. The CLUSTERED
keyword shows that the index is clustered, meaning that the physical order
of the rows in the table is the same as the logical (indexed) order of the
key values. In other words, the lowest level of the tree are actually the
data pages of the table itself. This is why there can be only one clustered
index per table. On the other hand, a NONCLUSTERED index, the lowest level
of the tree contains a pointer to that tells SQL Server where to find the
data corresponding to that index key. Since a non-clustered index does not
affect the way data pages are organized, multiple non-clustered indexes can
exist for a given table.
FILLFACTOR specifies a percentage that indicates how full SQL Server should
make the leaf level of each index page during index creation. This
percentage is no maintained. It is based on the data already present when
the index is built.
SQL Server 2000 Books Online Topic "Create Index"
_create_64l4.asp) has more information reagrding the CLUSTERED and
Hope this helps,
Farooq Mahmud [MS SQL Support]
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit