SQL Server - Autonumber identity

Hi all,
does toplink support the sql server autonumber identity?
actually i try to add a new record to a table where the primarykey is an autonumber (incremented automatically by 1 with every insert) and i keep get a toplink exception saying that a null primary key value can't be inserted
thanks

I suspect it is the security as specified in the message. E.g .your DBA set the ID columns so no user can override values in it.
And I suggest you 1st put the data into a staging table, then push it to the destination, this does not resolve the issue, but ensures better processing.
Arthur
MyBlog
Twitter

Similar Messages

Moving Access table with an autonumber key to SQL Server table with an identity key

I have an SSIS package that is moving data from an Access 2010 database to a SQL Server 2008 R2 database. Two of the tables that I am migrating have identity keys in the SQL Server tables and I need to be able to move the autonumber keys to the SQL
Server tables. I am executing a SQL Script to set the IDENTITY_INSERT ON before I execute the Data Flow task moving the data and then execute a SQL Script to set the IDENTITY_INSERT OFF after executing the Data Flow task.
It is failing with an error that says:
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was
done.".
Error: 0xC020901C at PGAccountContractDetail, PGAccountContractDetail [208]: There was an error with input column "ID" (246) on input "OLE DB Destination Input" (221). The column status returned was: "User does not have permission to
write to this column.".
Error: 0xC0209029 at PGAccountContractDetail, PGAccountContractDetail [208]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (221)" failed because error code 0xC020907C occurred, and the
error row disposition on "input "OLE DB Destination Input" (221)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information
about the failure.
Error: 0xC0047022 at PGAccountContractDetail, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "PGAccountContractDetail" (208) failed with error code 0xC0209029 while processing input "OLE DB
Destination Input" (221). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted
before this with more information about the failure.
Any ideas on what is causing this error? I am thinking it is the identity key in SQL Server that is not allowing the update. But, I do not understand why if I set IDENTITY_INSERT ON.
Thanks in advance for any help/guidance provided.

I suspect it is the security as specified in the message. E.g .your DBA set the ID columns so no user can override values in it.
And I suggest you 1st put the data into a staging table, then push it to the destination, this does not resolve the issue, but ensures better processing.
Arthur
MyBlog
Twitter

How to get JDev 10.1.2/ADF working with MS SQL Server Identity Column

Hello JDevTeam & JDevelopers,
I want to use JDev/ADF with a MS SQL Server 2005 database that contains tables employing IDENTITY Columns.
Using JDev/ADF and DBSequence with an Oracle database employing before triggers/sequences accomplishes what I am trying to do except I want to accomplish the same thing using a MSSQL Server 2005 database. Unfortunately I cannot change the database.
I have been able to select records but I am unable to insert records (due to my lack of knowledge) when using MS/SQL Server Identity Columns with JDev/ADF.
The following are the steps taken thus far.
Step1: Create table named test in the 2005 MSSQL Server (see script below).
Step2: Register 3rd Party JDBC Driver with JDeveloper; Using use Tools/Manage Libraries. Create a new entry in User Libraries with the following;
     Library Name     = Ms2005Jdbc
     Class Path     = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu\sqljdbc.jar
     (note: Latest TYPE 4 JDBC driver for Microsoft SQL Server 2005 - free at http://msdn.microsoft.com/data/ref/jdbc/)
Step3:Create New Database Connection;
     Connection Name = testconn1
     Type = Third Party JDBC Driver
     Authentication Username = sa, Password = password, Check Deploy Password
     Connection
          Driver Class = com.microsoft.sqlserver.jdbc.SQLServerDriver
          Library = Ms2005Jdbc
          Classpath = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu
          URL = jdbc:sqlserver://192.168.1.151:1433;instanceName=sqlexpress;databaseName=test
     Test Connection = Success!
Step5: Create a new application workspace using Web Application default template
Step6: In Model project, Create new Business Components Diagram.
Step7: Create new Entity Object. Goto to connections/testconn1, open tables and drag table test onto the diagram.
Step8: Generate Default Data Model Components by right-clicking on Entity Object. Except all the defaults.
When I test the Appmodule I select the view object and can scroll through all the records without error. If I try to insert a record, I get JBO-27014: Attribute testid in test is required.
Going back to the EntityObject I deselect the Mandatory attribute and re-run the test. Now when I try to insert it accepts the value for testname but it does not update the PK testid like it would using an "JDev/ADF/DBSequence/Oracle database/before trigger/sequence" solution.
Going back to the EntityObject and selecting refresh on insert does not solve this problem either. Changing the URL connection string and adding "SelectMethod=cursor" did not help and changing the SQl Flavor to SQLServer produced errors in the Business Components Browser. I've tried overriding isAttributeChanged() and other things as well.
I am totally stuck! Can anyone provide a solution?
Thanks for you help,
BG...
Create table named test
use [testdb]
go
set ansi_nulls on
go
set quoted_identifier on
go
create table [test](
     [testid] [int] identity(0,1) not null,
     [testname] [nvarchar](50) collate sql_latin1_general_cp1_ci_as not null,
constraint [pk_test] primary key nonclustered
     [testid] asc
)with (pad_index = off, ignore_dup_key = off) on [primary]
) on [primary]

Figured it out!
When using the MS SQL Server 2000 Database with the MS JDBC 2000 Driver you specify the SQL Flavor to SQLServer. However setting the SQL Flavor to SQLServer with MS SQL Server 2005 Database and the MS JDBC 2005 Driver will *** fail ***.
When working with the MS SQL Server 2005 Database and the MS JDBC 2005 Driver you set the SQL Flavor to SQL92 and the Type Map to Java.
If using a named instance like I am you would specify the URL = jdbc:sqlserver://<db host ip address>:<listening port>;instanceName=<your instance name>;selectMethod=cursor;databaseName=<your database name> (note: leave out the < >)
The 2005 Driver Class is different then the 2000 and is specified as com.microsoft.sqlserver.jdbc.SQLServerDriver
Note: In a default MS SQL Server 2005 installation the listening port will change *** everytime *** the host is restarted! You can override this though.
For the primary key you need to deselect the Mandatory attribute in the EntityObject editor.
Set Refresh on insert/update = no.
Set Updateable = never.
Now my Primary Keys which get their values from the Identity Column are working with ADF in a predictable way.
Simple enough but I have been away from this stuff for awhile.
BG...

INSERTING DATA INTO A SQL SERVER 2005 TABLE, WHICH HAS A IDENTITY COLUMN

Hi All,
I have to insert the data into a SQL SERVER 2005 Database table.
I am able to insert the data into a normal SQL Server table.
When I am trying to insert the data into a SQL Server table, which has a identity column (i.e. auto increment column in Oracle) I am getting error saying that can't insert value explicitly when IDENTITY_INSERT is set to OFF.
Had anybody tried this??
There are some SRs on this issue, Oracle agreed that it is a bug. I am wondering if there is any workaround from any one of you (refer Insert in MS-SQL database table with IDENTITY COLUMN
Thanks
V Kumar

Even I had raised a SR on this in October 2008. But didn't get any solution for a long time, finally I had removed the identity column from the table. I can't to that now :).
I am using 10.1.3.3.0 and MS SQL SERVER 2005, They said it is working for MS SQL SERVER TABLE, if the identity column is not a primary key and asked me to refer to note 744735.1.
I had followed that note, but still it is not working for me.
But my requirement is it should work for a MS SQL SERVER 2005 table, which has identity column as primary key.
Thanks
V Kumar

Is there any way to activate the keep identity setting when using a Transfer SQL Server Object Task?

Is there any way to add the "Keep Identity" option to the tables selected for transfer in a Transfer SQL Server Object Task? It seems that would be very useful, yet I can't find an easily available setting for it. I would prefer to
accomplish this within the Transfer SQL Server Object Task since it can copy any new fields added to the source tables, as opposed to having to rebuild a custom Data Flow Task any time a table structure is altered. I thought setting "CopyPrimaryKeys"
to True would do the trick, but I found that only ensures that the column settings are transferred; when the transfer happens, the destination id column is populated based on the specified seed and increment value, not what's actually in the source table.
I'd like to point out that replication isn't really an option here. This is a package that runs a few times a day to keep some data on our website up to date with data in our protected corporate environment.

IIRW there is FastLoadKeepIdentity specifies
whether to keep an identity in OLEDB destination
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Is it possible to Deploy a SSIS package to catalog with a Sql Server Identity in SQL Server 2012 programmly ?

Hi,
how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
This question has worried me for days.
Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
Or just an new solution instead of using the catalog.deploy_project?
best wishes from Qingyuan Lee.

Sorry, my description may be confusable.
I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
In fact, I don't care about the authority.
I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
so, using EXECUTE AS to change the execution context is accaptable.
The requirement for a Windows Authentication Account makes sense.
I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
Thanks very much for your help.

Passing SQL Server identity attributes values into adf entity objects

Hi all.
I'm using Jdeveloper 10g for developing an ADF Swing application based on MS SQL Server DB.
Does anyone know if it is possible to pass SQL Server identity attributes values into the correspondent attrributes of adf entity objects, like we do with Oracle DB Sequence.
The problem is that i should somhow implement cascade deleting of detail view objects, so i should use the composition association. But since i cant fill the primary key attribute with appropriate value (that is actually a ms sql server db sequence value) i always get
the following exception: oracle.jbo.InvalidOwnerException: JBO-25030 as i try to create a new pair of master/detail objects.
Thanks in advance.
Alex.

The approach is good. but i still dont understand how i can address the sql server db sequence (identity field) programmatically...
The code offered
SequenceImpl sequence = new SequenceImpl("PRODUCTS_SEQ",getDBTransaction());
setProdId(sequence.getSequenceNumber());
generates something like this:
select deq_name.nextval from dual
but this syntax works for oracle only... and not for sql server...
Edited by: Timin on Mar 26, 2009 6:34 AM
Edited by: Timin on Mar 26, 2009 10:25 AM

MS SQL Server 2014: Error inserting into Temp table with index and identity field

In this thread, I mentioned a problem with SQL Server 2014:
SQL Server 2014: Bug with IDENTITY INSERT ON
The question was answered, it is a bug. To keep you informed on this issue, I open this discussion.
Problem:
The code below works perfectly fine on MS SQL Server 2008 R2 and MS SQL Server 2012, but gives an error every second time the proc is executed on MS SQL Server 2014. If I do not define any index on the temp table, the problem disappears. Defining the index
after the insert, does not help.
SET NOCOUNT ON
GO
IF EXISTS (SELECT 1 FROM sys.procedures WHERE name = 'usp_Test') DROP PROC dbo.usp_Test;
GO
CREATE PROC dbo.usp_Test AS
BEGIN
SET NOCOUNT ON
CREATE TABLE #Source(ID integer NOT NULL);
INSERT INTO #Source VALUES (1), (2), (3);
CREATE TABLE #Dest (ID integer IDENTITY(1,1) NOT NULL);
CREATE INDEX #IDX_Dest ON #Dest (ID);
PRINT 'Check if the insert might cause an identity crisis';
SELECT 'Source' AS SourceTable, * FROM #Source;
SELECT 'Destination' AS DestTable, * FROM #Dest;
SET IDENTITY_INSERT #Dest ON;
PRINT 'Do the insert';
INSERT INTO #Dest (ID) SELECT ID FROM #Source;
PRINT 'Insert ready';
SET IDENTITY_INSERT #Dest OFF;
SELECT * FROM #Dest;
DROP TABLE #Source;
DROP TABLE #Dest;
END;
GO
PRINT 'First execution of the proc, everything OK';
EXEC dbo.usp_Test;
PRINT '';
PRINT 'Second execution of the proc, the insert fails.';
PRINT 'Removing the index #IDX_Dest causes the error to disappear.';
EXEC dbo.usp_Test;
GO
DROP PROC dbo.usp_Test;
GO

There is some progress. Communication from a former Microsoft employee tells us this:
Shivendra Vishal
Engineer at Microsoft
I am no longer with MS, and I do not have code access, however from the public symbols, I could make out following:
sqlmin!SetidentI2I4+0x1f3:
000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] ds:00000000`00000000=????????????????
ExceptionAddress: 000007fef4d865d3 (sqlmin!SetidentI2I4+0x00000000000001f3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
This is a read AV and from registers it is clear that we were trying to move the value of location pointed by qword of register rax which is not valid:
rax=0000000000000000 rbx=0000000000000038 rcx=0000000000001030
rdx=0000000000000006 rsi=00000001f55def98 rdi=00000000106fd070
rip=000007fef4d865d3 rsp=00000000106fcf40 rbp=00000000106fcfe9
r8=0000000000000000 r9=00000001f55def60 r10=00000001f55defa0
r11=00000000106fcd20 r12=0000000000000000 r13=0000000000000002
r14=00000001f49c3860 r15=00000001f58c0040
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
The stack is:
# Child-SP RetAddr Call Site
00 00000000`106fcf40 000007fe`f30c1437 sqlmin!SetidentI2I4+0x1f3
01 00000000`106fd050 000007fe`f474e7ce sqlTsEs!CEsExec::GeneralEval4+0xe7
02 00000000`106fd120 000007fe`f470e6ef sqlmin!CQScanUpdateNew::GetRow+0x43d
03 00000000`106fd1d0 000007fe`f08ff517 sqlmin!CQueryScan::GetRow+0x81
04 00000000`106fd200 000007fe`f091cebe sqllang!CXStmtQuery::ErsqExecuteQuery+0x36d
05 00000000`106fd390 000007fe`f091ccb9 sqllang!CXStmtDML::XretDMLExecute+0x2ee
06 00000000`106fd480 000007fe`f08fa058 sqllang!CXStmtDML::XretExecute+0xad
07 00000000`106fd4b0 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
08 00000000`106fd5f0 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
09 00000000`106fd7e0 000007fe`f152cfaa sqllang!CSQLSource::Execute+0x86c
0a 00000000`106fd9b0 000007fe`f152c9e8 sqllang!CStmtExecProc::XretLocalExec+0x25a
0b 00000000`106fda30 000007fe`f152a1d8 sqllang!CStmtExecProc::XretExecExecute+0x4e8
0c 00000000`106fe1e0 000007fe`f08fa058 sqllang!CXStmtExecProc::XretExecute+0x38
0d 00000000`106fe220 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
0e 00000000`106fe360 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
0f 00000000`106fe550 000007fe`f0902267 sqllang!CSQLSource::Execute+0x86c
10 00000000`106fe720 000007fe`f0909087 sqllang!process_request+0xa57
11 00000000`106feee0 000007fe`f2bf49d0 sqllang!process_commands+0x4a3
12 00000000`106ff200 000007fe`f2bf47b4 sqldk!SOS_Task::Param::Execute+0x21e
13 00000000`106ff800 000007fe`f2bf45b6 sqldk!SOS_Scheduler::RunTask+0xa8
14 00000000`106ff870 000007fe`f2c136ff sqldk!SOS_Scheduler::ProcessTasks+0x279
15 00000000`106ff8f0 000007fe`f2c138f0 sqldk!SchedulerManager::WorkerEntryPoint+0x24c
16 00000000`106ff990 000007fe`f2c13246 sqldk!SystemThread::RunWorker+0x8f
17 00000000`106ff9c0 000007fe`f2c13558 sqldk!SystemThreadDispatcher::ProcessWorker+0x3ab
18 00000000`106ffa70 00000000`775d59ed sqldk!SchedulerManager::ThreadEntryPoint+0x226
19 00000000`106ffb10 00000000`7780c541 kernel32!BaseThreadInitThunk+0xd
1a 00000000`106ffb40 00000000`00000000 ntdll!RtlUserThreadStart+0x21
Unassembling the function:
000007fe`f4d8658e 4c8b10 mov r10,qword ptr [rax]
000007fe`f4d86591 4533e4 xor r12d,r12d
000007fe`f4d86594 410fb7d5 movzx edx,r13w
000007fe`f4d86598 4533c9 xor r9d,r9d
000007fe`f4d8659b 4533c0 xor r8d,r8d
000007fe`f4d8659e 488bc8 mov rcx,rax
000007fe`f4d865a1 4489642420 mov dword ptr [rsp+20h],r12d
000007fe`f4d865a6 41ff5230 call qword ptr [r10+30h]
000007fe`f4d865aa 8b5597 mov edx,dword ptr [rbp-69h]
000007fe`f4d865ad 4c8b10 mov r10,qword ptr [rax]
000007fe`f4d865b0 4489642438 mov dword ptr [rsp+38h],r12d
000007fe`f4d865b5 4489642430 mov dword ptr [rsp+30h],r12d
000007fe`f4d865ba 458d442401 lea r8d,[r12+1]
000007fe`f4d865bf 4533c9 xor r9d,r9d
000007fe`f4d865c2 488bc8 mov rcx,rax
000007fe`f4d865c5 c644242801 mov byte ptr [rsp+28h],1
000007fe`f4d865ca 4488642420 mov byte ptr [rsp+20h],r12b
000007fe`f4d865cf 41ff5250 call qword ptr [r10+50h]
000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] <=================== AV happened over here
000007fe`f4d865d6 488bc8 mov rcx,rax
000007fe`f4d865d9 4c8bf0 mov r14,rax
000007fe`f4d865dc ff5268 call qword ptr [rdx+68h]
000007fe`f4d865df 488d55e7 lea rdx,[rbp-19h]
000007fe`f4d865e3 4c8b00 mov r8,qword ptr [rax]
000007fe`f4d865e6 488bc8 mov rcx,rax
000007fe`f4d865e9 41ff5010 call qword ptr [r8+10h]
000007fe`f4d865ed f6450a04 test byte ptr [rbp+0Ah],4
I remember few issues with scan2ident function, I am not sure if they have fixed it however it appears that this is intoduced to SQL 2014 and we need help from MS to get this resolved as it needs code analysis.
It is not getting simulated for other versions of SQL apart from SQL 2014.
Also to add, interestingly, the value of rax is not visibly changed and it was successfully passed on to rcx, which has a valid value, so something should have changed the value of rax inside call to function using call qword ptr [r10+50h], and looking at this
it appears that it might be a list of functions and we are going at particular offset [50h]. So, bottom line is that the call to function qword ptr [r10+50h], should be changing something in rax, and debugging/analyzing this code might give us some more idea.

JPA and SQL Server 2005's Identity Don't Play Nice

I am hoping someone with a little more senior knowledge of JPASQL Server 2005 can point me in the right direction involving SQL Server 2005.
What I am discovering is JPA and SQL Server 2005 do not playing nice together when you use the IDENTITY capability for
a primary key. Let me explain. "...when using the IDENTITY as the generator type, the value for the identity field MAY NOT be
available BEFORE the entity data is saved in the database because typically it is generated when a record is committed."
My problem is this.
I have two separate entities using another entity, for example a car has a wheel and a truck has a wheel. I can go through the steps
of persisting the car and the wheel with no problem. My problem begins when I try to
find the wheel (by wheel description) for the truck. The query finds the wheel, but does not return the primary key for wheel.
Therefore, using the PK inside a query generates this error:
java.lang.IllegalArgumentException: An instance of a null PK has been incorrectly provided for this find operation. What has been my appraoch to get the entity to commit to the database is to use the following sequence for the Entity Manager.
entityManager.persist(wheel);
entityManager.flush(); I have assumed to this point this action would persist my data because I have been able to retrieve the PK immidately after these steps.
However, multiple actions taking place within the same transaction, appears to render the persist and flush steps useless. My initial thought
is to wrap the wheel creation within a new transaction so when the method/transaction completes, the data would be in the database. This
has not worked.
I hope I have explained this clear for others to follow. I apologize in advance if I have not. Any suggestions are greatly appreciated.

I am hoping someone with a little more senior knowledge of JPASQL Server 2005 can point me in the right direction involving SQL Server 2005.
What I am discovering is JPA and SQL Server 2005 do not playing nice together when you use the IDENTITY capability for
a primary key. Let me explain. "...when using the IDENTITY as the generator type, the value for the identity field MAY NOT be
available BEFORE the entity data is saved in the database because typically it is generated when a record is committed."
My problem is this.
I have two separate entities using another entity, for example a car has a wheel and a truck has a wheel. I can go through the steps
of persisting the car and the wheel with no problem. My problem begins when I try to
find the wheel (by wheel description) for the truck. The query finds the wheel, but does not return the primary key for wheel.
Therefore, using the PK inside a query generates this error:
java.lang.IllegalArgumentException: An instance of a null PK has been incorrectly provided for this find operation. What has been my appraoch to get the entity to commit to the database is to use the following sequence for the Entity Manager.
entityManager.persist(wheel);
entityManager.flush(); I have assumed to this point this action would persist my data because I have been able to retrieve the PK immidately after these steps.
However, multiple actions taking place within the same transaction, appears to render the persist and flush steps useless. My initial thought
is to wrap the wheel creation within a new transaction so when the method/transaction completes, the data would be in the database. This
has not worked.
I hope I have explained this clear for others to follow. I apologize in advance if I have not. Any suggestions are greatly appreciated.

Equivalent to SQL Server IDENTITY columns in Oracle 8i?

Under SQL Server, my app frequently keys tables using IDENTITY columns which are also used as the only column in the tables primary key. After an INSERT, I typically retrieve the value assigned to the IDENTITY column using:
SELECT @@IDENTITY
I need to port my app to Oracle 8i and wonder if there is a similar concept available. I checked out ROWID and UROWID but they don't sound quite right.
Any idea?

You can use the sequence directly in your insert
without use a trigger
For example:
SQL> Create table nn ( c1 number, c2 varchar2(34));
Table created.
SQL>
SQL> CREATE SEQUENCE customers_seq
2 START WITH 5
3 INCREMENT BY 1
4 NOCACHE
5 NOCYCLE;
Sequence created.
SQL>
SQL> insert into nn values (customers_seq.nextval, 'jjj');
1 row created.
SQL> insert into nn values (customers_seq.nextval, 'mmm');
1 row created.
SQL> select * from nn;
C1 C2
5 jjj
6 mmm
SQL>
[email protected]
Joel P�rez

Problem in EOImpl.doDML() ,with Identity column in MS SQL server.

Hello,
I'm using JDeveloper 11.1.1.4.0
My application is working with MS SQL Server.
One of the tables in the database has its PK as Identity column.
EO is created with the corresponding attribute as Primary Key.
Upon calling doDML() in EOImpl, it generates an insert statement and attempts to insert in the PK field as well. MS SQL does not allow insertion in PK field and throws exception.
I tried setting some configuration on EO PK attribute, but in vein. Also there is no other 'unique' column in table that can be setup as PK in EO.
Appreciate your suggestions.
Regards,
Amar

i think better to Oracle datbase as I am afraid of that Oracle won't be able to see your problem against sql server due to sql server is not their product!

What is Oracle's alternative to IDENTITY Column in SQL Server/ DB2

What is Oracle's alternative to IDENTITY Column(Auto Increment Column) in SQL Server/ DB2 ? Is Sequence and Trigger the only way out for this?
Why is Oracle not creating anything like an Identitiy column in SQL Server?

What is Oracle's alternative to IDENTITY Column(Auto
Increment Column) in SQL Server/ DB2 ? Is Sequence
and Trigger the only way out for this?Of course not, you can use in your inserts sequences as well:
insert into blahh values (my_seq.nextval, ...) and use returniong clause to get the value back if necessary
You can use them in insert with subselects
insert into blah
select my_seq.nextval, ...
from ....
>
Why is Oracle not creating anything like an Identitiy
column in SQL Server?Because they are different companies with different people and thoughts and existing mechanism is sufficient i.e. one can even argue that it is even more flexible than identity btw ;)
Gints Plivna
http://www.gplivna.eu

Reset Identity Column Value in SQL Server depending on whats being inserted

I have a SQL Server 2008 database with a table that has an ID field that has an identity increment and seed of 1.
This work great as each new record created automatically gets a new and distinct number.
Now when I insert certain new records I need to be able to make that value start at 10001 and then the next would be 10002 etc.
But this is only for certain inserts.
Is there a way to control the identity seed & increment on the fly via a query maybe?
So some inserts would follow 1,2,3,4,5,6,7 depending on whats being inserted
and others would follow 10001,10002,10003 depending on whats being inserted.
is this possible?

Make it a different field. Don't mess with your PK.
Make sure you have a plan for when you get 10000 records in this table.

Identity Field in MS SQL Server

Hi All,
I'm new in JDBC. I'm trying to get the autogenerated value from an identity column in SQL Server, after an INSERT operation.
I was looking around and I found there is an smart way:
stmt.executeUpdate(str, Statement.RETURN_GENERATED_KEYS);
ResultSet rs = stmt.getGeneratedKeys();
but the executeUpdate reports an UnsupportedOperationException.
I'm using jdbc-odbc-bridge.
What am I missing?
thanks in advance
arturo

>
but the executeUpdate reports an
UnsupportedOperationException.
I'm using jdbc-odbc-bridge.
What am I missing?Your driver does not do that.

SQL Server 2014 Bug - with Clustered Index On Temp Table with Identity Column

Hi,
Here's a stored procedure. (It could be shorter, but this will show the problem.)
CREATE PROCEDURE dbo.SGTEST_TBD_20141030 AS
IF OBJECT_ID('TempDB..#Temp') IS NOT NULL
DROP TABLE #Temp
CREATE TABLE #Temp
Col1 INT NULL
,Col2 INT IDENTITY NOT NULL
,Col3 INT NOT NULL
CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
SET IDENTITY_INSERT #Temp ON;
RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
INSERT INTO #Temp (Col1, Col2, Col3)
SELECT 1,2,3
RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
SET IDENTITY_INSERT #Temp OFF;
In SQL Server 2014, If I execute this (EXEC dbo.SGTEST_TBD_20141030) It works. If I execute it a second time - It fails hard with:
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
In SQL Server 2012, I can execute it over and over, with no problem. I've discovered two work-a-rounds:
1) Add "WITH RECOMPILE" to the SP CREATE/ALTER statement, or
2) Declare the cluster index in the TABLE CREATE statement, e.g. ",UNIQUE CLUSTERED (COL2)"
This second option only works though, if the column is unique. I've opted for the "WITH RECOMPILE" for now. But, thought I should share.

Hi,
I did not get any error Message:
CREATE TABLE #Temp
Col1 INT NULL
,Col2 INT IDENTITY NOT NULL
,Col3 INT NOT NULL
CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
SET IDENTITY_INSERT #Temp ON;
RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
INSERT INTO #Temp (Col1, Col2, Col3)
SELECT 1,2,3
RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
SET IDENTITY_INSERT #Temp OFF;
SELECT * FROM #Temp
OUTPUT:
Col1 Col2
Col3
1 2 3
1 2 3
1 2 3
Select @@version
--Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Thanks Shiven:) If Answer is Helpful, Please Vote

SQL Server - Autonumber identity

Similar Messages

Maybe you are looking for