If I right click on an index, the properties context menu is grayed out as well as the "New Index...", "Disable", and "Delete". If I right click on a table and click modify, I can add and edit indexes from there just fine. Strangely enough "Included Columns" is grayed out though.
Management Studio - Index properties grayed out
Hot Topic
- bottom row
- NOD32 - SQL 2000 connection error - DNS?
- ProcessAdd for dimensions
- how to prevent ordering of records....
- Error on custom data mining plugin: content type mismatch
- SqlBackUp() vs Volume Shadow Copy Service
- How to countrows from subreport and present on mainreport
- .Net CF 2.0 Error , "Can't find PInvoke DLL 'dbnetlib.dll'."
- Replication in SQL server2005
- Dataflow with 2 lookup using the same Table
SQL Server
- Upgrade to SQL Server 2005 - ODBC Timeout Problem
- Need help in creating SSIS package
- How to update my program with a database
- Remove SP1 or install SP2 Dec. CTP
- Numerous windows open during debugging
- Server Registration
- How to send Notifications to WinForm?
- Unable to connect to the remote server
- SQL Server Management Studio and SQLCompact
- connecting to remote server
Management Studio - Index properties grayed out
Slippyr4
Was the database designer or table designer opened at the time We prevent the index dialogs from being launched when the table is being designed.
The database and table designers work by making the state of the tables (including indexes) match the internal model in the designers. This includes index and constraint definitions. Reconciling the state on the server to the state in the model can "undo" any change made outside the designer environment. For example, if you open the table designer in one instance of Management Studio and make a change (say, add a column) and at the same time change an index on that table using another instance of Management Studio, when you save the changes in the table designer, it will recreate the index with its previous definition (after warning you) because the old index is what the table designer loaded into its internal model when it launched.
In a pre-release version of SQL Server 2005, we didn't prevent the index dialogs from being launched when the table or database designers were designing the index' table, and we got exactly this kind of "last save wins" behavior, which really confused users.
Hope this helps,
Steve
Evan Mulawski