I’ve published a new open-source project in my GitHub account, dubbed “sp_GenerateTableDDLScript“.
This is basically a stored procedure that can be used to generate a CREATE TABLE script in T-SQL for a given table in Microsoft SQL Server.
Download & Installation
You may install this procedure in your SQL Server instance by downloading (or copy-and-pasting) the script sp_GenerateTableDDLScript.sql and running it in the master database, and then use the following command to turn it into a system stored procedure, thus making it usable anywhere in the instance:
EXECUTE sp_MS_marksystemobject 'sp_GenerateTableDDLScript'
Example use case 1: Creating a table in an archive database, without foreign keys and identity property:
DECLARE @CMD NVARCHAR(MAX) EXEC sp_GenerateTableDDLScript 'Sales.OrderDetails', 'ArchiveDB.Sales.OrderDetails', @CMD OUTPUT, @IncludeForeignKeys = 0, @IncludeIdentity = 0 SELECT @CMD
Example use case 2: Duplicating a table within the same database:
DECLARE @CMD NVARCHAR(MAX) EXEC sp_GenerateTableDDLScript 'Sales.OrderDetails', 'Sales.OrderDetails_New', @CMD OUTPUT, @ConstraintsNameAppend = '_New' SELECT @CMD
Example use case 3: Duplicating a table as a temporary table, without computed columns:
DECLARE @CMD NVARCHAR(MAX) EXEC sp_GenerateTableDDLScript 'Sales.OrderDetails', '#temp_OrderDetails', @CMD OUTPUT, @ConstraintsNameAppend = '_Temp', @IncludeComputedColumns = 0 SELECT @CMD
@TableName SYSNAME, -- The name of the source table. This parameter is mandatory. If the table's schema is not default (dbo), then please specify the schema name as well as part of the parameter. @NewTableName SYSNAME = NULL, -- The name of the new (target) table. You may also include database and schema as part of the name. If not specified, same name as source table will be used. @Result NVARCHAR(MAX) OUTPUT, -- Output textual parameter that will contain the result TSQL command for creating the table. @IncludeDefaults BIT = 1, -- Set whether to include default constraints @IncludeCheckConstraints BIT = 1, -- Set whether to include check constraints @IncludeForeignKeys BIT = 1, -- Set whether to include foreign key constraints @IncludeIndexes BIT = 1, -- Set whether to include indexes @IncludePrimaryKey BIT = 1, -- Set whether to include primary key constraints @IncludeIdentity BIT = 1, -- Set whether to include identity property @IncludeUniqueIndexes BIT = 1, -- Set whether to include unique index constraints @IncludeComputedColumns BIT = 1, -- Set whether to include computed columns (if not, they will also be automatically ignored by constraints and indexes) @UseSystemDataTypes BIT = 0, -- Set whether to use system data type names instead of user data type names @ConstraintsNameAppend SYSNAME = '' -- This is an optional text string to append to constraint names, in order to avoid the duplicate object name exception. This is useful when creating the new table within the same database.
- The source table must exist, otherwise an exception will be raised.
- The script does not check whether the target table already exists, it falls on you to make sure that it doesn’t before running the result script.
- The script does not check whether constraint names already exist, it falls on you to use the
@ConstraintsNameAppendparameter to generate unique names.
- The script (at the moment) does NOT support the following (more info at the issues page):
- Column Sets
- Collations different from Database Default
- Filestream columns
- Sparse columns
- Not for replication property
- XML document collections
- Rule objects
- Non-default Filegroups
- In-Memory tables
At this time, this script was successfully tested on the following Microsoft SQL Server versions, but it should work on versions as old as 2008 and newer:
If you wish to contribute by testing on additional versions, you’re more than welcome to do so, and submit your results to our GitHub Issues page.
This is an open-source project, and therefore you may freely submit your own issue and pull requests, if you wish to contribute.
Any contribution is welcome.
You may view the currently opened issues at the GitHub Issues page.
The script is mainly based off of the sp_ScriptTable stored procedure originally published by Tim Chapman in this URL: