-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> thanks, but does that mean that inserts into other tables
> which uses the
> identity key are also blocked during this period, since it
> can't update
> @@IDENTITY ??
The "magic" of MSSQL server ensures that @@IDENTITY will always work
the way it's "supposed" to. That's to say that as long as your
SELECT @@IDENTITY is submitted to the database on the same connection
as you INSERT & is sent immediately after the INSERT, then you'll get
the right identity value back.
MS made sure that @@IDENTITY is maintain per table & per connection.
You should be safe using it regardless of how much traffic your site
has, and it will NOT lock inserts to other tables.
Best regards,
Zac Bedell
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.2 for non-commercial use <http://www.pgp.com>
Comment: Please use PGP!!!
iQA/AwUBOS5zuQraVoMWBwRBEQJUkACgyZI7pFYsXUy0sPcugy6DZDh3GvcAnRH6
4BzNmSiyJxYsgLPKJIIFl1xQ
=uG4x
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
