SQL Server Errors or Failures Error: 1729 to Error: 1762

SQLServerF1

 

Error: 1729, Severity: 16,
Cannot create table ‘%.*ls’ because the partitioning column ‘%.*ls’ uses a FILESTREAM column.

Error: 1730, Severity: 16,
Creating or altering compressed table ‘%.*ls’ failed because the uncompressed row size would be %d, including %d bytes of internal overhead. This exceeds the maximum allowable table row size of %d bytes.

Error: 1731, Severity: 16,
Cannot create the sparse column ‘%.*ls’ in the table ‘%.*ls’ because an option or data type specified is not valid. A sparse column must be nullable and cannot have the ROWGUIDCOL, IDENTITY, or FILESTREAM properties. A sparse column cannot be of the follo

Error: 1732, Severity: 16,
Cannot create the sparse column set ‘%.*ls’ in the table ‘%.*ls’ because a table cannot have more than one sparse column set. Modify the statement so that only one column is specified as COLUMN_SET FOR ALL_SPARSE_COLUMNS.

Error: 1733, Severity: 16,
Cannot create the sparse column set ‘%.*ls’ in the table ‘%.*ls’ because a sparse column set must be a nullable xml column. Modify the column definition to allow null values.

Error: 1734, Severity: 16,
Cannot create the sparse column set ‘%.*ls’ in the table ‘%.*ls’ because the table already contains one or more sparse columns. A sparse column set cannot be added to a table if the table contains a sparse column.

Error: 1736, Severity: 16,
The column ‘%.*ls’ in the table ‘%.*ls’ cannot be referenced in a CHECK constraint or computed column definition because the column is a sparse column set. A sparse column set cannot be referenced in a a CHECK constraint or computed column definition.

Error: 1738, Severity: 10,
Cannot create table ‘%.*ls’ with only a column set column and without any non-computed columns in the table.

Error: 1750, Severity: 10,
Could not create constraint. See previous errors.

Error: 1752, Severity: 16,
Column ‘%.*ls’ in table ‘%.*ls’ is invalid for creating a default constraint.

Error: 1753, Severity: 16,
Column ‘%.*ls.%.*ls’ is not the same length or scale as referencing column ‘%.*ls.%.*ls’ in foreign key ‘%.*ls’. Columns participating in a foreign key relationship must be defined with the same length and scale.

Error: 1754, Severity: 16,
Defaults cannot be created on columns with an IDENTITY attribute. Table ‘%.*ls’, column ‘%.*ls’.

Error: 1755, Severity: 16,
Defaults cannot be created on columns of data type timestamp. Table ‘%.*ls’, column ‘%.*ls’.

Error: 1756, Severity: 10,
Skipping FOREIGN KEY constraint ‘%.*ls’ definition for temporary table. FOREIGN KEY constraints are not enforced on local or global temporary tables.

Error: 1757, Severity: 16,
Column ‘%.*ls.%.*ls’ is not of same collation as referencing column ‘%.*ls.%.*ls’ in foreign key ‘%.*ls’.

Error: 1758, Severity: 16,
Only a single constraint can be added or dropped online with no other operations in the same statement.

Error: 1759, Severity: 16,
Computed column ‘%.*ls’ in table ‘%.*ls’ is not allowed to be used in another computed-column definition.

Error: 1760, Severity: 16,
Constraints of type %ls cannot be created on columns of type %ls.

Error: 1761, Severity: 16,
Cannot create the foreign key “%.*ls” with the SET NULL referential action, because one or more referencing columns are not nullable.

Error: 1762, Severity: 16,
Cannot create the foreign key “%.*ls” with the SET DEFAULT referential action, because one or more referencing not-nullable columns lack a default constraint.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *