BEGIN TRANSACTION
SET QUOTED_IDENTIFIER ON
GO
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
GO
COMMIT
BEGIN TRANSACTION
CREATE TABLE dbo.Tmp_Orders_4
(
"Order Number" int NOT NULL,
"Order Date" datetime NOT NULL,
Payterms varchar(10) NOT NULL
) ON "default"
GO
IF EXISTS(SELECT * FROM dbo.Orders)
EXEC(`INSERT INTO dbo.Tmp_Orders_4("Order Number", "Order Date", Payterms)
SELECT "Order Number", "Order Date", CONVERT(varchar(10), Payterms) 
ÂFROM dbo.Orders TABLOCKX')
GO
DROP TABLE dbo.Orders
GO
EXECUTE sp_rename `dbo.Tmp_Orders_4', `Orders'
GO
ALTER TABLE dbo.Orders ADD CONSTRAINT
PK_Orders PRIMARY KEY NONCLUSTERED
(
"Order Number"
) ON "default"
GO
COMMIT

I'm not going to examine the entire code listing, but I did want to outline a very robust feature of the Database Designer. You can use the Database Designer to change the column data types of tables that contain existing data. This code listing shows the Transact-SQL that creates a temporary table named Tmp_Orders_4. This temporary table is used to insert any data that resides in the Orders table and convert it to the new data type. The original Orders table with the old data type for the Payterms column is then deleted. Finally, the Tmp_Orders_4 table that contains the order information with the new data type is renamed to Orders. The Database Designer creates all this logic for you, which should make DBAs appreciate the robustness of the Database Designer even more.