SQL set identity and retain values - sql

I have a problem restoring a table.
I wanted to restore data by copying data from the backup to the table.
The problem is, the PK of the table has the Identity-Property set. So when I inserted the lost rows they got new IDs.
I created a new table without identity and put the data in there.
Now I want to turn on Identity on the PK column, which doesn't work.
Any what I can do or if this is possible at all?

You cannot add IDENTITY property to existing column. Either you insert in existing table with IDENTITY column with IDENTITY_INSERT ON' option or you create a newIDENTITY` column in the new table.
This post might help you

This will solve your problem
[https://stackoverflow.com/a/1049305/6652909]

If you have backup of table then TRUNCATE your table then set primary key then make it auto increment in table and then copy your table and make sure your data of table is entered properly, it worked for me may be it will helpful to you also.

Related

SQL Server : alter the Identity seed

I am migrating data from one database to another. I have my scripts mostly together already, but I am trying to figure out the best way to make one change to a table in the new database.
I have a Customer table. That table has a customer_id column which is the identity column. I want to change the identity seed/increment from (1,1) to (200,1) without changing the customer_ids for the existing data I will be inserting into the table.
Old data is 101-108. Basically we want to keep the old data the same so it matches up with old records in other systems, but we want the new data to start seeding in at 200.
I tried Googling how to do this, but all my Googling came back with results where people wanted to change what column was the identity column, and not just change the identity seed number. Is there a simple query I can use to accomplish what I want to do?
You can use DBCC CHECKIDENT:
DBCC CHECKIDENT ('dbo.customer', RESEED, 200)
This will change the current seed value of the identity column of the specified table. If you need to insert specific identity values, you can SET IDENTITY_INSERT ON in your insert statement.
IDENTITY_INSERT
What I would do unset the new column as an identity (using alter table), then insert the data from the old table, and then reset the new column as the identity again, with whatever increment you want as per the link
https://learn.microsoft.com/en-us/sql/t-sql/statements/create-table-transact-sql-identity-property?view=sql-server-2017

How to reseed identity in Amazon redshift and how to make it auto increment

I am wondering how can we reset/reseed an identity column in Amazon redshift
I also want to make an auto increment column in my table.
You can do something like this while creating the table.
create table test(id bigint identity(1,1))
Adding identity column in existing table is not possible, so you need to re-create a new table and then copy your data from existing table. While re-creating you can reset the identity as column as required.
I too had the similar scenario to rest the Identity column in Redshift especially when the table is truncated. Unfortunately I couldn't find any option to reset the identity column. Using the work around of drop and create the table whenever required to rest but this many not work in all the scenarios.

Is it possible to return a deleted column?

To delete a column in table I am using DROP COLUMN command from Alter Table. After I did it, is it possible (somehow) to return the deleted column?
You can re-add the column easily, syntax depends on the database. As far as recovering the values of the deleted column, you'd need a backup for that if it's not preserved in an open transaction.

Enable an identity column that already has data in it?

Someone disabled the identity column of a table in a SQL DB. Is it possible to re-enable that feature of the column even when there is already data in the table? And maintain the existing identity values?
I know I could copy the data to another table and reinsert it after setting Identity_Insert on.
You cannot switch on the IDENTITY on an existing column, that's just not possible in SQL Server right now (at least up to version 2012).
What you need to do is exactly what you describe:
create the new table in the structure you want, with the IDENTITY column
copy the data from the existing table into the new table, with SET IDENTITY_INSERT ON
drop the old table
rename the new table to the old table name
You can "re-enable" the identity specification in the visual table designer in SQL Server Mgmt Studio, but this really only does those above steps in the background, for you.
Just as *marc_s* said you can use
I dont know if there is any other way to do this but you can use
CREATE TABLE tblNewTable
(
//Put the columns and datatypes of the former table
)
INSERT INTO tblNewTable
AS
SELECT * FROM oldTable
Then drop the table usng
DROP TABLE oldTable
Then recreate the new table and add the identity column, then use
INSERT INTO tblNewRecreatedTable (//Columns of the new created table except the column with the identity
AS
SELECT //Columns of the table you copied the data to except the Columned that you defined identity
I hope it helps

How do I remove an Identity completely

I'm currently putting together some changes in our data model which include changing a column (that happens to be part of the primary key) so that it is no longer an identity. Is there a way to do this short of actually removing and recreating the entire column or table? The autogenerated code from SSMS does just that but I was wondering if there was perhaps a simpler solution.
You cannot remove the Identity property of a column without droping it.
Possible solution steps are:
(a) Add a new column
(b) Update the column with identity column value
(c) Remove the identity column.
Alter Table Tablename Add newColumnname int
Update Table set newColumnname =IdentityColumn
Alter Table TableName Drop IdentityColumnName
Note : If you are talking about switching off the identity property for the time being, check Set IDENTITY_INSERT TableName ON Command
Make sense?
Cheers, John