Server Management Studio Bug? | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Server Management Studio Bug?

Trying to move a PK from one file to a different file on a 2000 server database here is what the new SMS scripts out: USE [Database]
GO
ALTER TABLE [dbo].[customer_vendor_intl_traffic_fact] ADD CONSTRAINT [PK_customer_vendor_intl_traffic_fact] PRIMARY KEY CLUSTERED
(
[id] ASC
) ON [Indexes]
GO
And here is what the old EM scripts out
CREATE UNIQUE CLUSTERED
INDEX [PK_customer_vendor_intl_traffic_fact] ON [dbo].[customer_vendor_intl_traffic_fact] ([id])
WITH
DROP_EXISTING
ON [Indexes] Of course the statement fails in SMS because there is already one PK.
Is this because the SMS is not really designed for 2000?

There is a lot of difference between the working fashion of SQL 2k and 2k5 tools.
Because the access to system tables is addressed entierly different in SQL2005 as compared to SQL 2k. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>