identity-column

hey all. I have a table in my DB that has about a thousand records in it. I would like to reset the identity column so that all of the ID's are sequential again. I was looking at this but I'm ASSuming that it only works on an empty table Current Table ID | Name 1 Joe 2 Phil 5 Jan 88 Rob Desired Table ID | Name 1 Joe 2 Phil 3 Jan 4 Rob Thanks in advance The easiest way would be to make a copy of the current table, fix up any parentid issues, drop it and then rename the new one. You could also temporarily remove the IDENTITY and try the folowing: ;WITH TBL AS ( SELECT *, ROW_NUMBER(ORDER BY ID)

Is it possible to reseed an auto increment column in a SQLite database, and if so, how is this done? ie. The equivalent of DBCC CHECKIDENT ('MyTable', RESEED, 1) in SQL Server. Garett In SQLite there is a table named SQLITE_SEQUENCE, which tracks the largest RowId value that a table has. You can do insert, updates and deletes on this table. For example, to mimic similar functionality as the TRUNCATE TABLE statement SQL Server you could something like: DELETE FROM MyTableName; DELETE FROM SQLITE_SEQUENCE WHERE NAME = 'MyTableName'; In the above example all data from MyTableName is removed, and

I would like to learn how to fetch list of all tables that has identity columns from a MS SQL database. SELECT [schema] = s.name, [table] = t.name FROM sys.schemas AS s INNER JOIN sys.tables AS t ON s.[schema_id] = t.[schema_id] WHERE EXISTS ( SELECT 1 FROM sys.identity_columns WHERE [object_id] = t.[object_id] ); select COLUMN_NAME, TABLE_NAME from INFORMATION_SCHEMA.COLUMNS where TABLE_SCHEMA = 'dbo' and COLUMNPROPERTY(object_id(TABLE_NAME), COLUMN_NAME, 'IsIdentity') = 1 order by TABLE_NAME Eric Burcham I like this approach because it uses a join instead of a WHERE EXISTS or a call to

Which should i use to get last inserted record id in sql server 2005? I searched stackoverflow and i found this, SQL: How to get the id of values I just INSERTed? Comment of the best answer: there are known bugs with SCOPE_IDENTITY() in sql server 2005, not sure about 2008, the OUTPUT clause can return a set of IDs if necessary... Select SCOPE_IDENTITY() as Id from Table I am uisng sql server 2005... Any suggestion I'm not entirely sure what these "knows bugs" in SCOPE_IDENTITY() should be. The only thing I'm currently aware of is here: Six reasons you should be nervous about parallelism

"There can only be one IDENTITY column per table" Why is it so? Take a scenario of a vehicle, there exists a chasis number which is unique as well as the registration number which turns out to be unique. To depict this scenario in sql server we need a custom implementation for on of the columns. Conversely, in Oracle you can have as many sequences as you want on a table. Why is there a restriction on the IDENTITY Column, any specific reasons? The scenario of having a vehicle schema is something imaginary am questioning myself as to why there's a restriction on the identity column. An Identity

Oracle 12 introduced nice feature (which should have been there long ago btw!) - identity columns. So here's a script: CREATE TABLE test ( a INTEGER GENERATED ALWAYS AS IDENTITY PRIMARY KEY, b VARCHAR2(10) ); -- Ok INSERT INTO test (b) VALUES ('x'); -- Ok INSERT INTO test (b) SELECT 'y' FROM dual; -- Fails INSERT INTO test (b) SELECT 'z' FROM dual UNION ALL SELECT 'zz' FROM DUAL; First two inserts run without issues providing values for 'a' of 1 and 2. But the third one fails with ORA-01400: cannot insert NULL into ("DEV"."TEST"."A") . Why did this happen? A bug? Nothing like this is mentioned