Indentity Insert -- sql server (alternate)

For example John Smith
8/29/2003 12:25:28 PM

I'm doing a data transfer from Access to SQL Server, I wish to keep the
identity column (autonumber) values as all the data is already related. I
tried the first table append query including the identity column, it worked.
Was this fluke? Will it always work? I was under the impression that I would
have to issue a "set identity_insert on" before doing this. The SQL database
will have absolutely no data before the transfer routines are run.

Nath Wilson
8/29/2003 2:22:31 PM

As long as there arent any duplicated values in what you are trying to
insert into the identity column you should have no problems.

You could also use Access' upsizing wizard to move the tables to SQL
server. This feature is available in A2k, I'm not sure about versions
below that.

http://www.cooldigitec.co.uk/njw/15-AccessToSQLServer7.asp

Is an account of my upsizing experiences.

HTH
--

Nath
www.cooldigitec.co.uk
(Email mangling obvious)

*** Sent via Developersdex http://www.developersdex.com ***

For example John Smith
8/29/2003 4:16:23 PM

[quoted text, click to view]

OK Thanks.

[quoted text, click to view]

It's an app rewrite, the tables are already there and slightly different.

Chuck Grimsby
8/29/2003 10:14:38 PM

No, you can't rely on the Identity field keeping the same number as
the autonumber field.

On Fri, 29 Aug 2003 12:25:28 +0100, "For example John Smith"
[quoted text, click to view]

--
You're Not Losing More Hair, You're Gaining More Scalp.

For example John Smith
9/1/2003 1:30:46 PM

[quoted text, click to view]

It's a big company.

[quoted text, click to view]

A real what?

For example John Smith
9/1/2003 1:46:21 PM

An update on this, it's now failing with the message:

Error 544 - [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert
explicit value for identity column in table 'zstblApplicationFunction' when
IDENTITY_INSERT is set to OFF. (ODBC.QueryDef)Error 3146 - ODBC--call
failed. (DAO.QueryDef)

In Profiler, the SQL trace shows:

<---------------------------------------------------
SET IDENTITY_INSERT "dbo"."zstblApplicationFunction" ON
go
exec sp_executesql N'INSERT INTO "dbo"."zstblApplicationFunction"
("ApplicationFunctionID","SortOrder","ParentApplicationFunctionID","Applicat
ionFunctionName","DisplayName","Hyperlink","FormHelpID","IsMenuItem","IsSubM
enuItem","IsEnforced","SysIsInsert","SysIsSelect","SysIsUpdate","SysIsDelete
","SysIsExecute") VALUES
(@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12,@P13,@P14,@P15)', N'@P1
int,@P2 int,@P3 int,@P4 varchar(50),@P5 varchar(50),@P6 varchar(8000),@P7
int,@P8 bit,@P9 bit,@P10 bit,@P11 bit,@P12 bit,@P13 bit,@P14 bit,@P15 bit',
1, 3, NULL, 'SECURITYMENU', 'Security', NULL, NULL, 1, 0, 0, 0, 1, 0, 0, 0
go
IF @@TRANCOUNT > 0 ROLLBACK TRAN
go
---------------------------------------------------->

If I copy and paste that into Query Analyser it inserts the record. When
Access issues these commands to the server it fails. Odd.

John Bell
9/1/2003 2:07:01 PM

Hi

The problems is the GO after SET IDENTITY_INSERT.. ON

I suggest you do this in a stored procedure.

John

[quoted text, click to view]

For example John Smith
9/1/2003 4:32:28 PM

[quoted text, click to view]

I got another table with an Identity column and this works fine. The GO
doesn't seem to be a problem there (I think they're just put in by Profiler
anyway for the purpose of pasting into QA) and it works OK from QA with the
GOs in place..

A Stored procedure would be difficult as the data is coming from an Access
database although in the case of this particular table it comes from another
SQL database but I did try importing that one to Access and then running the
append query from the Access database. I can look at doing a SP for the ones
that do come from another SQL database (these are new ones added to the
application recently in the re-write) but since I'm on like table 3 out of
60 I'm not that confident the rest will go as smoothly as the first 2.

I'm pasting the troublesome table script below, this may provide a clue,
could be the self join FK that doesn't exist on any table I've transferred
thus far.

--- table script
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[zstblApplicationFunction_zstblApplicationFunction_FK1]')
and OBJECTPROPERTY(id, N'IsForeignKey') = 1)
ALTER TABLE [dbo].[zstblApplicationFunction] DROP CONSTRAINT
zstblApplicationFunction_zstblApplicationFunction_FK1
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[zstblApplicationFunction_zstblPermission_FK1]') and
OBJECTPROPERTY(id, N'IsForeignKey') = 1)
ALTER TABLE [dbo].[zstblPermission] DROP CONSTRAINT
zstblApplicationFunction_zstblPermission_FK1
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[zstblApplicationFunction]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
drop table [dbo].[zstblApplicationFunction]
GO

CREATE TABLE [dbo].[zstblApplicationFunction] (
[ApplicationFunctionID] [int] IDENTITY (1, 1) NOT NULL ,
[SortOrder] [int] NULL ,
[ParentApplicationFunctionID] [int] NULL ,
[ApplicationFunctionName] [varchar] (50) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[DisplayName] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
,
[Hyperlink] [varchar] (512) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[FormHelpID] [int] NULL ,
[IsMenuItem] [bit] NOT NULL ,
[IsSubMenuItem] [bit] NULL ,
[IsEnforced] [bit] NOT NULL ,
[SysIsInsert] [bit] NOT NULL ,
[SysIsSelect] [bit] NOT NULL ,
[SysIsUpdate] [bit] NOT NULL ,
[SysIsDelete] [bit] NOT NULL ,
[SysIsExecute] [bit] NOT NULL ,
[SysTimeStamp] [timestamp] NULL
) ON [PRIMARY]
GO

ALTER TABLE [dbo].[zstblApplicationFunction] WITH NOCHECK ADD
CONSTRAINT [zstblApplicationFunction_PK] PRIMARY KEY CLUSTERED
(
[ApplicationFunctionID]
) WITH FILLFACTOR = 90 ON [PRIMARY]
GO

ALTER TABLE [dbo].[zstblApplicationFunction] ADD
CONSTRAINT [PrimaryKey_UC1] UNIQUE NONCLUSTERED
(
[ApplicationFunctionName]
) WITH FILLFACTOR = 90 ON [PRIMARY]
GO

CREATE INDEX [IDX_ParentApplicationFunctionID] ON
[dbo].[zstblApplicationFunction]([ParentApplicationFunctionID]) WITH
FILLFACTOR = 90 ON [PRIMARY]
GO

CREATE INDEX [zstblApplicationFunction_AK2] ON
[dbo].[zstblApplicationFunction]([DisplayName]) WITH FILLFACTOR = 90 ON
[PRIMARY]
GO

ALTER TABLE [dbo].[zstblApplicationFunction] ADD
CONSTRAINT [zstblApplicationFunction_zstblApplicationFunction_FK1] FOREIGN
KEY
(
[ParentApplicationFunctionID]
) REFERENCES [dbo].[zstblApplicationFunction] (
[ApplicationFunctionID]
),
CONSTRAINT [zstblFormHelp_zstblApplicationFunction_FK1] FOREIGN KEY
(
[FormHelpID]
) REFERENCES [dbo].[zstblFormHelp] (
[FormHelpID]
)
GO

Erland Sommarskog
9/1/2003 8:11:40 PM

For example John Smith (someone@microsoft.com) writes:
[quoted text, click to view]

Hm, this is certainly a desprate idea, but check that you have the
same value for SPID for the commands.

Or, um, wait there is one more possibility. Under which user do you
run this from Access? And from Query Analyzer? SET IDENTITY_INSERT
is not permitted for plain users. Of course you should get an error
message for that too, and maybe you are if you sift through the
error messages.

And, oh, it would be appreciated if you fixed your name and e-mail
address.

--
Erland Sommarskog, SQL Server MVP, sommar@algonet.se

Books Online for SQL Server SP3 at

John Bell
9/1/2003 10:28:21 PM

Hi

Sorry, this is not transaction specific, but you should still put this in a
SP to solve the problems!

John

[quoted text, click to view]

Trevor Best
9/1/2003 11:39:18 PM

On Mon, 1 Sep 2003 20:11:40 +0000 (UTC) in comp.databases.ms-access,
[quoted text, click to view]

I bet it's not the first time someone followed the instructions in
Outlook Express to the letter <g>

--
A)bort, R)etry, I)nfluence with large hammer.

For example John Smith
9/2/2003 1:45:30 PM

[quoted text, click to view]

Bang! Hit the nail squarely on the head, thanks for that pointer. It appears
that Access does issue a SET IDENTITY_INSERT ON command prior to the insert
but doesn't turn it off again afterward. My own passthrough query to turn it
off is running under a different SPID.

So it appears to be an Access bug.

[quoted text, click to view]

sa. I did find an error message to that effect, level 16 but it appears
Access ignores anything lower than 18.

[quoted text, click to view]

I don't wish to dwell on this but...
The fake email is clear, I don't want spam nor do I want to enter into email
correspondance, I've answered as many if not more questions in these groups
than I've asked and have fallen into the trap of taking problems into email
and then the other party expecting me to be their personal programming slave
or I have to ignore or tell the person outright that they're overstepping
the bounds of my generosity, either way it can end in tears (for them, not
me, you see it's for eveyone else's protection <g>). As for the name, one
could use an obvious fake, a fake that looks real or a real name (or a real
one that looks like an obvious fake), you still wouldn't know me from Adam.

Some people post anonymously because they know they are acting the fool and
even use remaillers to hide all trace (I don't BTW), others perhaps,
hypothetically (nudge wink) using a company account don't want bosses or
clients to see them asking questions on a public forum.

Erland Sommarskog
9/2/2003 8:44:17 PM

For example John Smith (someone@microsoft.com) writes:
[quoted text, click to view]

I also answer lot of questions, and sometimes get them in the mail
too, but I have never found it to be a problem with people asking for
too much.

A lot of people these days uses fake names and addresses, which in my
opinion is a pity, because being a long-timer in news I recall the days,
when replying by mail was the natural thing when the discussion was not
really of general interest. This is why I insist on using my real name and
mail address in public.

But even if you use a fake address, there are fake address which are less
appropriate than others. Unless you are a Microsoft emplyoess, I don't
you should use an fake address their domain.
--
Erland Sommarskog, SQL Server MVP, sommar@algonet.se

Books Online for SQL Server SP3 at

Chuck Grimsby
9/3/2003 1:31:25 AM

On Tue, 2 Sep 2003 20:44:17 +0000 (UTC), Erland Sommarskog
[quoted text, click to view]

Or at least, add ".invalid" to the end of the email address, which is
the (RFC) accepted method for saying "this email address is fake".

--
You Will Become Rich And Famous Unless You Don't.

For example John Smith
9/3/2003 9:59:22 AM

[quoted text, click to view]

Noted.

sql server (alternate) : Indentity Insert