2714: There is already an object named in the database
SQL ServerWhat does it mean?
An object with the same name as the one being created (table, view, procedure, etc.) already exists in the database. The CREATE statement failed due to a name conflict.
Why does it happen?
Running the same CREATE script a second time, not dropping the existing object first, a different schema assumption, non-idempotent deployment/migration scripts, or a naming conflict.
How to fix it
Check whether the object exists first: create conditionally with IF OBJECT_ID('dbo.Name') IS NULL, or use CREATE OR ALTER (for procedures/views/functions). If necessary, DROP the existing object and recreate it. Write migration scripts to be idempotent. Verify that you are working in the correct schema/database.
More from this engine
- 2812Could not find stored procedure
- 8623The query processor ran out of internal resources and could not produce a query plan
- 4104The multi-part identifier could not be bound
- 601Could not continue scan with NOLOCK due to data movement
- 50000Custom error raised with RAISERROR
- 3902The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION
- 1101Could not allocate a new page because of insufficient disk space in filegroup