Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
In this article
Applies to:
SQL Server 2016 (13.x) and later versions
Azure SQL Database
Azure SQL Managed Instance
SQL database in Microsoft Fabric
You can rename a table column in SQL Server by using SQL Server Management Studio or Transact-SQL.
Renaming a column doesn't automatically rename references to that column. You must modify any objects that reference the renamed column manually. For example, if you rename a table column and that column is referenced in a trigger, you must modify the trigger to reflect the new column name. Use sys.sql_expression_dependencies to list dependencies on the object before renaming it.
Renaming a column doesn't automatically update the metadata for any objects which SELECT
all columns (using *
) from that table. For example, if you rename a table column, and that column is referenced by a non-schema-bound view or function that selects all columns (using *
), the metadata for the view or function continues to reflect the original column name. Refresh the metadata using sp_refreshsqlmodule or sp_refreshview.
Requires ALTER
permission on the object.
- In Object Explorer, connect to an instance of Database Engine.
- In Object Explorer, right-click the table in which you want to rename columns and choose Rename.
- Type a new column name.
- In Object Explorer, right-click the table to which you want to rename columns and choose Design.
- Under Column Name, select the name you want to change and type a new one.
- On the File menu, select Save table name.
You can also change the name of a column in the Column Properties tab. Select the column whose name you want to change and type a new value for Name.
The following example renames the column ErrorTime
in the table dbo.ErrorLog
to ErrorDateTime
in the AdventureWorksLT
database.
EXEC sp_rename 'dbo.ErrorLog.ErrorTime', 'ErrorDateTime', 'COLUMN';
Note the output warning, and verify other objects or queries aren't broken:
Caution: Changing any part of an object name could break scripts and stored procedures.
For more information, see sp_rename.