I am trying to do this:
ALTER TABLE CompanyTransactions DROP COLUMN Created
But I get this:
Msg 5074, Level 16, State 1, Line 2
The object ‘DF__CompanyTr__Creat__0CDAE408’ is dependent on column ‘Created’.
Msg 4922, Level 16, State 9, Line 2
ALTER TABLE DROP COLUMN Created failed because one or more objects access this column.
This is a code first table. Somehow the migrations have become all messed up and I am trying to manually roll back some changed.
I have no idea what this is:
DF__CompanyTr__Creat__0CDAE408
asked Apr 21, 2017 at 18:11
Casey CrookstonCasey Crookston
12.9k24 gold badges106 silver badges192 bronze badges
1
You must remove the constraints
from the column before removing the column. The name you are referencing is a default constraint
.
e.g.
alter table CompanyTransactions drop constraint [df__CompanyTr__Creat__0cdae408];
alter table CompanyTransactions drop column [Created];
answered Apr 21, 2017 at 18:14
4
The @SqlZim’s answer is correct but just to explain why this possibly have happened. I’ve had similar issue and this was caused by very innocent thing: adding default value to a column
ALTER TABLE MySchema.MyTable ADD
MyColumn int DEFAULT NULL;
But in the realm of MS SQL Server a default value on a colum is a CONSTRAINT. And like every constraint it has an identifier. And you cannot drop a column if it is used in a CONSTRAINT.
So what you can actually do avoid this kind of problems is always give your default constraints a explicit name, for example:
ALTER TABLE MySchema.MyTable ADD
MyColumn int NULL,
CONSTRAINT DF_MyTable_MyColumn DEFAULT NULL FOR MyColumn;
You’ll still have to drop the constraint before dropping the column, but you will at least know its name up front.
answered Jan 30, 2018 at 19:13
malloc4kmalloc4k
1,7043 gold badges22 silver badges22 bronze badges
1
As already written in answers you need to drop constraints (created automatically by sql) related to all columns that you are trying to delete.
Perform followings steps to do the needful.
- Get Name of all Constraints using sp_helpconstraint which is a system stored procedure utility — execute following
exec sp_helpconstraint '<your table name>'
- Once you get the name of the constraint then copy that constraint name and execute next statement i.e
alter table <your_table_name>
(It’ll be something like this only or similar format)
drop constraint <constraint_name_that_you_copied_in_1> - Once you delete the constraint then you can delete 1 or more columns by using conventional method i.e
Alter table <YourTableName> Drop column column1, column2
etc
answered Dec 27, 2018 at 10:34
vibs2006vibs2006
5,9183 gold badges39 silver badges39 bronze badges
When you alter column datatype
you need to change constraint key
for every database
alter table CompanyTransactions drop constraint [df__CompanyTr__Creat__0cdae408];
Salman Zafar
3,8164 gold badges20 silver badges43 bronze badges
answered Jul 4, 2019 at 6:46
1
You need to do a few things:
- You first need to check if the constrain exits in the information schema
- then you need to query by joining the sys.default_constraints and sys.columns
if the columns and default_constraints have the same object ids - When you join in step 2, you would get the constraint name from default_constraints. You drop that constraint. Here is an example of one such drops I did.
-- 1. Remove constraint and drop column
IF EXISTS(SELECT *
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = N'TABLE_NAME'
AND COLUMN_NAME = N'LOWER_LIMIT')
BEGIN
DECLARE @sql NVARCHAR(MAX)
WHILE 1=1
BEGIN
SELECT TOP 1 @sql = N'alter table [TABLE_NAME] drop constraint ['+dc.name+N']'
FROM sys.default_constraints dc
JOIN sys.columns c
ON c.default_object_id = dc.object_id
WHERE dc.parent_object_id = OBJECT_ID('[TABLE_NAME]') AND c.name = N'LOWER_LIMIT'
IF @@ROWCOUNT = 0
BEGIN
PRINT 'DELETED Constraint on column LOWER_LIMIT'
BREAK
END
EXEC (@sql)
END;
ALTER TABLE TABLE_NAME DROP COLUMN LOWER_LIMIT;
PRINT 'DELETED column LOWER_LIMIT'
END
ELSE
PRINT 'Column LOWER_LIMIT does not exist'
GO
answered Aug 7, 2019 at 20:16
In addition to accepted answer, if you’re using Entity Migrations for updating database, you should add this line at the beggining of the Up()
function in your migration file:
Sql("alter table dbo.CompanyTransactions drop constraint [df__CompanyTr__Creat__0cdae408];");
You can find the constraint name in the error at nuget packet manager console which starts with FK_dbo.
answered Oct 17, 2020 at 15:10
ninbitninbit
5306 silver badges24 bronze badges
I had the same problem and this was the script that worked for me with a table with a two part name separated by a period «.».
USE [DATABASENAME]
GO
ALTER TABLE [TableNamePart1].[TableNamePart2] DROP CONSTRAINT [DF__ TableNamePart1D__ColumnName__5AEE82B9]
GO
ALTER TABLE [TableNamePart1].[ TableNamePart1] DROP COLUMN [ColumnName]
GO
answered Nov 8, 2020 at 14:01
I needed to replace an INT primary key with a Guid. After a few failed attempts, the EF code below worked for me. If you hyst set the defaultValue… you end up with a single Guid a the key for existing records.
protected override void Up(MigrationBuilder migrationBuilder)
{
migrationBuilder.DropUniqueConstraint("PK_Payments", "Payments");
migrationBuilder.DropColumn(
name: "PaymentId",
table: "Payments");
migrationBuilder.AddColumn<Guid>(
name: "PaymentId",
table: "Payments",
type: "uniqueidentifier",
defaultValueSql: "NewId()",
nullable: false);
}
answered Apr 24, 2021 at 6:56
Copy the default constraint name from the error message and type it in the same way as the column you want to delete.
answered Mar 18, 2022 at 1:39
1
I had the same problem, I could not remove migrations, it would show error that something is already applied, so i changed my DB name in appsettings, removed all migrations, and then added new migration and it worked. Dont understand issue completely, but it worked
answered Jan 17 at 14:42
I fixed by Adding Dropping constraint inside migration.
migrationBuilder.DropForeignKey(
name: "FK_XX",
table: "TableX").
and below recreates constraint.
migrationBuilder.AddForeignKey(
name: "FK_XX",
table: "TableX",
column: "ColumnX",
onDelete: ReferentialAction.Restrict);
answered Feb 7 at 9:11
I have a database where I have to convert all varchar
datatype columns to nvarchar
type. I have been able to convert all tables except one. Before converting into nvarchar
datatype I am dropping all constraints like foreign key, primary key, unique key, check constraints, default constraints and indexes. I also have deleted all the data before altering to nvarchar
.
The problem is that I am getting the error
ALTER TABLE ALTER COLUMN «Permanent Address» failed because one or more objects access this column.
when I am executing the drop and create table statements it is working there but while converting to nvarchar
with ALTER
command I am getting the error
I have the following scripts
—The actual table deifinition
USE [Customer]
GO
--Permanent_Address is a computed column
CREATE TABLE [dbo].[Customer_Contact](
[Customer_id] int NOT NULL,
[Present_Address] [varchar](250) NOT NULL,
[Permanent_Address] AS ([Present_Address]))
--Alter statement to convert from varchar to nvarchar
ALTER TABLE [Customer_Contact] ALTER COLUMN [Present Address] NVARCHAR(250) NOT NULL
ALTER TABLE [Customer_Contact] ALTER COLUMN [Permanent_Address] NVARCHAR(250) NOT NULL
Result-: ALTER TABLE ALTER COLUMN «Permanent Address» failed because one or more objects access this column.
--Drop and Create the table script
IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[Customer_Contact]') AND type in (N'U'))
DROP TABLE [dbo].[Customer_Contact]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Customer_Contact](
[Customer_id] int NOT NULL,
[Present_Address] [Nvarchar](250) NOT NULL,
[Permanent_Address] AS ([Present_Address]))
--The table is created successfully with Nvarchar Datatype
I am trying to do this:
ALTER TABLE CompanyTransactions DROP COLUMN Created
But I get this:
Msg 5074, Level 16, State 1, Line 2
The object ‘DF__CompanyTr__Creat__0CDAE408’ is dependent on column ‘Created’.
Msg 4922, Level 16, State 9, Line 2
ALTER TABLE DROP COLUMN Created failed because one or more objects access this column.
This is a code first table. Somehow the migrations have become all messed up and I am trying to manually roll back some changed.
I have no idea what this is:
DF__CompanyTr__Creat__0CDAE408
asked Apr 21, 2017 at 18:11
Casey CrookstonCasey Crookston
12.9k24 gold badges106 silver badges192 bronze badges
1
You must remove the constraints
from the column before removing the column. The name you are referencing is a default constraint
.
e.g.
alter table CompanyTransactions drop constraint [df__CompanyTr__Creat__0cdae408];
alter table CompanyTransactions drop column [Created];
answered Apr 21, 2017 at 18:14
4
The @SqlZim’s answer is correct but just to explain why this possibly have happened. I’ve had similar issue and this was caused by very innocent thing: adding default value to a column
ALTER TABLE MySchema.MyTable ADD
MyColumn int DEFAULT NULL;
But in the realm of MS SQL Server a default value on a colum is a CONSTRAINT. And like every constraint it has an identifier. And you cannot drop a column if it is used in a CONSTRAINT.
So what you can actually do avoid this kind of problems is always give your default constraints a explicit name, for example:
ALTER TABLE MySchema.MyTable ADD
MyColumn int NULL,
CONSTRAINT DF_MyTable_MyColumn DEFAULT NULL FOR MyColumn;
You’ll still have to drop the constraint before dropping the column, but you will at least know its name up front.
answered Jan 30, 2018 at 19:13
malloc4kmalloc4k
1,7043 gold badges22 silver badges22 bronze badges
1
As already written in answers you need to drop constraints (created automatically by sql) related to all columns that you are trying to delete.
Perform followings steps to do the needful.
- Get Name of all Constraints using sp_helpconstraint which is a system stored procedure utility — execute following
exec sp_helpconstraint '<your table name>'
- Once you get the name of the constraint then copy that constraint name and execute next statement i.e
alter table <your_table_name>
(It’ll be something like this only or similar format)
drop constraint <constraint_name_that_you_copied_in_1> - Once you delete the constraint then you can delete 1 or more columns by using conventional method i.e
Alter table <YourTableName> Drop column column1, column2
etc
answered Dec 27, 2018 at 10:34
vibs2006vibs2006
5,9183 gold badges39 silver badges39 bronze badges
When you alter column datatype
you need to change constraint key
for every database
alter table CompanyTransactions drop constraint [df__CompanyTr__Creat__0cdae408];
Salman Zafar
3,8164 gold badges20 silver badges43 bronze badges
answered Jul 4, 2019 at 6:46
1
You need to do a few things:
- You first need to check if the constrain exits in the information schema
- then you need to query by joining the sys.default_constraints and sys.columns
if the columns and default_constraints have the same object ids - When you join in step 2, you would get the constraint name from default_constraints. You drop that constraint. Here is an example of one such drops I did.
-- 1. Remove constraint and drop column
IF EXISTS(SELECT *
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = N'TABLE_NAME'
AND COLUMN_NAME = N'LOWER_LIMIT')
BEGIN
DECLARE @sql NVARCHAR(MAX)
WHILE 1=1
BEGIN
SELECT TOP 1 @sql = N'alter table [TABLE_NAME] drop constraint ['+dc.name+N']'
FROM sys.default_constraints dc
JOIN sys.columns c
ON c.default_object_id = dc.object_id
WHERE dc.parent_object_id = OBJECT_ID('[TABLE_NAME]') AND c.name = N'LOWER_LIMIT'
IF @@ROWCOUNT = 0
BEGIN
PRINT 'DELETED Constraint on column LOWER_LIMIT'
BREAK
END
EXEC (@sql)
END;
ALTER TABLE TABLE_NAME DROP COLUMN LOWER_LIMIT;
PRINT 'DELETED column LOWER_LIMIT'
END
ELSE
PRINT 'Column LOWER_LIMIT does not exist'
GO
answered Aug 7, 2019 at 20:16
In addition to accepted answer, if you’re using Entity Migrations for updating database, you should add this line at the beggining of the Up()
function in your migration file:
Sql("alter table dbo.CompanyTransactions drop constraint [df__CompanyTr__Creat__0cdae408];");
You can find the constraint name in the error at nuget packet manager console which starts with FK_dbo.
answered Oct 17, 2020 at 15:10
ninbitninbit
5306 silver badges24 bronze badges
I had the same problem and this was the script that worked for me with a table with a two part name separated by a period «.».
USE [DATABASENAME]
GO
ALTER TABLE [TableNamePart1].[TableNamePart2] DROP CONSTRAINT [DF__ TableNamePart1D__ColumnName__5AEE82B9]
GO
ALTER TABLE [TableNamePart1].[ TableNamePart1] DROP COLUMN [ColumnName]
GO
answered Nov 8, 2020 at 14:01
I needed to replace an INT primary key with a Guid. After a few failed attempts, the EF code below worked for me. If you hyst set the defaultValue… you end up with a single Guid a the key for existing records.
protected override void Up(MigrationBuilder migrationBuilder)
{
migrationBuilder.DropUniqueConstraint("PK_Payments", "Payments");
migrationBuilder.DropColumn(
name: "PaymentId",
table: "Payments");
migrationBuilder.AddColumn<Guid>(
name: "PaymentId",
table: "Payments",
type: "uniqueidentifier",
defaultValueSql: "NewId()",
nullable: false);
}
answered Apr 24, 2021 at 6:56
Copy the default constraint name from the error message and type it in the same way as the column you want to delete.
answered Mar 18, 2022 at 1:39
1
I had the same problem, I could not remove migrations, it would show error that something is already applied, so i changed my DB name in appsettings, removed all migrations, and then added new migration and it worked. Dont understand issue completely, but it worked
answered Jan 17 at 14:42
I fixed by Adding Dropping constraint inside migration.
migrationBuilder.DropForeignKey(
name: "FK_XX",
table: "TableX").
and below recreates constraint.
migrationBuilder.AddForeignKey(
name: "FK_XX",
table: "TableX",
column: "ColumnX",
onDelete: ReferentialAction.Restrict);
answered Feb 7 at 9:11
There are a variety of causes for the message shown in the title of this post. Manually creating statistics for a column is one such cause. This post shows how that works, and what you need to do to get around the error. Columns that have manually-created statistics attached cannot have their properties modified without first dropping the stats object – this is to ensure the stats object accurately reflects the content of the column. SQL Server returns an error message stating “ALTER TABLE ALTER COLUMN failed because one or more objects access this column.” I ran into this limitation recently when attempting to modify the datatype for a column from varchar
to nvarchar
. This database has auto create statistics disabled. As a result, manually creating statistics objects is critical to ensuring good query performance.
Have a failed column or three!
The Error Message
When attempting to modify a column that has a manually created statistics object attached, you receive the following “ALTER TABLE ALTER COLUMN failed” error message:
Msg 5074, Level 16, State 1, Line 36 The statistics '<name>' is dependent on column '<col>'. Msg 4922, Level 16, State 9, Line 36 ALTER TABLE ALTER COLUMN <col> failed because one or more objects access this column.
Interestingly, if SQL Server has auto-created a stats object on a column, and you subsequently modify that column, you receive no such error. SQL Server silently drops the statistics object, and modifies the column. The auto-created stats object is not automatically recreated until a query is executed that needs the stats object. This difference in how auto-created stats and manually created stats are treated by the engine can make for some confusion.
Ads by Google, Paying the Rent:
The Script
Consider the following minimally complete and verifiable example code that can be used to reproduce the problem:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 |
SET NOCOUNT ON; USE master; GO —Create a new, blank database for our test IF EXISTS (SELECT 1 FROM sys.databases d WHERE d.name = ‘test_stats_alter’) BEGIN ALTER DATABASE test_stats_alter SET SINGLE_USER WITH ROLLBACK IMMEDIATE; DROP DATABASE test_stats_alter; END CREATE DATABASE test_stats_alter; ALTER DATABASE test_stats_alter SET AUTO_CREATE_STATISTICS OFF; ALTER DATABASE test_stats_alter SET AUTO_UPDATE_STATISTICS OFF; GO USE test_stats_alter; GO CREATE TABLE dbo.stats_test ( id int NOT NULL IDENTITY(1,1) PRIMARY KEY CLUSTERED , d varchar(30) NOT NULL ); CREATE TABLE dbo.dates ( d varchar(30) NOT NULL ) GO —Insert a bunch of rows to allow the query optimizer to perform actual work. INSERT INTO dbo.stats_test (d) SELECT CONVERT(datetime, DATEADD(DAY, CONVERT(int, CRYPT_GEN_RANDOM(2)), ‘1900-01-01T00:00:00’)) FROM sys.syscolumns sc1 CROSS JOIN sys.syscolumns sc2 INSERT INTO dbo.dates (d) SELECT CONVERT(datetime, DATEADD(DAY, CONVERT(int, CRYPT_GEN_RANDOM(2)), ‘1900-01-01T00:00:00’)) FROM sys.syscolumns sc1 GO —Manually create a stats object CREATE STATISTICS stats_test_st1 ON dbo.stats_test(d) WITH FULLSCAN, NORECOMPUTE; GO —Attempt to alter the column with the manual stats object defined. —This will fail with Msg 5074, Level 16, State 1, Line xx ALTER TABLE dbo.stats_test ALTER COLUMN d nvarchar(30) NOT NULL; GO |
SQL Server returns this error:
Msg 5074, Level 16, State 1, Line 47 The statistics 'stats_test_st1' is dependent on column 'd'. Msg 4922, Level 16, State 9, Line 47 ALTER TABLE ALTER COLUMN d failed because one or more objects access this column.
Let’s continue on:
50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 |
—drop the stats object DROP STATISTICS dbo.stats_test.stats_test_st1; GO —Allow SQL Server to automatically create statistics ALTER DATABASE test_stats_alter SET AUTO_CREATE_STATISTICS ON; ALTER DATABASE test_stats_alter SET AUTO_UPDATE_STATISTICS ON; GO —Coerce SQL Server into automatically creating a stats object. —This is a complex enough query that SQL Server recognizes a —stats object would be helpful for good performance. SELECT st.id , st.d INTO dbo.stats_test_output FROM dbo.stats_test st LEFT JOIN dbo.dates d ON st.d = d.d WHERE st.d > ‘2017-06-01T00:00:00’; GO —See if SQL Server in fact created an auto-stats object on —the column. SELECT * FROM sys.stats st INNER JOIN sys.objects o ON st.object_id = o.object_id WHERE o.name = ‘stats_test’; GO |
╔════════════╦════════════════════════════════╦══════════════╗ ║ name ║ name ║ auto_created ║ ╠════════════╬════════════════════════════════╬══════════════╣ ║ stats_test ║ PK__stats_te__3213E83FF58F8430 ║ 0 ║ ║ stats_test ║ _WA_Sys_00000002_21B6055D ║ 1 ║ ╚════════════╩════════════════════════════════╩══════════════╝
—attempt to alter the table, which succeeds. ALTER TABLE dbo.stats_test ALTER COLUMN d nvarchar(30) NOT NULL; GO —check to see if the auto-created stats object still exists SELECT * FROM sys.stats st INNER JOIN sys.objects o ON st.object_id = o.object_id WHERE o.name = ‘stats_test’; |
The auto-created stats object has been silently dropped:
╔════════════╦════════════════════════════════╦══════════════╗ ║ name ║ name ║ auto_created ║ ╠════════════╬════════════════════════════════╬══════════════╣ ║ stats_test ║ PK__stats_te__3213E83FF58F8430 ║ 0 ║ ╚════════════╩════════════════════════════════╩══════════════╝
In Summary
Manually adding statistics objects can be a blessing for performance, however you need to recognize the limitations this creates for future object modifications.
If you have auto_create_statistics turned off, you probably want to update your stats objects on a regular basis to ensure good performance. See my statistics update job for details about how to do that.
Read the other articles in our series on SQL Server Internals.
If you found this post useful, please
consider donating a small amount
to help keep the lights on and site running.
Всем привет.
Пытаюсь изменить тип столбца с varchar(50) на :
T-SQL | ||
|
Выдает ошибку:
Сообщение 5074, уровень 16, состояние 1, строка 1
объект «f_AddressObjectStringSmart» зависит от столбец «Name».
Сообщение 4922, уровень 16, состояние 9, строка 1
Ошибка ALTER TABLE ALTER COLUMN Name, так как один или несколько объектов обращаются к данному столбцу.
f_AddressObjectStringSmart — функция, в ней поправил используемое поле.
Вопрос как уйти от этой ошибки и выполнить скрипт.