Like most things, it depends. I like doing it locally because then
there's only one trip to the server and I have the guid available when I
need it.
You can also call a stored procedure to do your insert with an output
parameter to return the newly created guid.
Frank.
Frank Cazabon
On 17/10/2012 04:22 PM, MB Software Solutions, LLC wrote:
On 10/17/2012 4:18 PM, Frank Cazabon wrote:
@@Identity is only for identity fields. I always generate my own GUID
locally and insert that along with the rest of the data. My guess is
that you are going to have to query based on the data that you just put
into the record (do you have a candidate key?) to get the id
I thought having the DB generate the PK was a good/preferred way but I
guess not. Tried inserting my own made-up value (for example) and got
this:
insert into MyTable (ID,VendorName) values ('MS','Microsoft');
"Conversion failed when converting from a character string to
uniqueidentifier."
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
