Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tpcolson
Starting Member
5 Posts |
Posted - 2011-06-29 : 21:31:30
|
| have the following schema:[dbo].[tbl_Events][Event_ID] [uniqueidentifier] NOT NULL (PK)[Location_ID] [uniqueidentifier] NULL (FK)[Observation] [nvarchar][dbo].[tbl_Locations][Event_ID] [uniqueidentifier] NOT NULL[Location_ID] [uniqueidentifier] NULL (PK)[Notes] [nvarchar]Locations is the parent table with a relationship to events through Location ID. Location_ID is set to be NewID() on create in Locations, and Event_ID is set to be NewID() on create in events. The table, relationship, and PK format is non-changeable due to organizational policy governing replication. I'm looking for advice on how to define an insert trigger that will create a new row in events, with the location_id pulled from the parent location table, and a new unique event_id. E.g., when (by outside application with no ability to embed sql code) a new location record is created, it gets a location_id of 8170daed-92c8-47f1-98ca-147800329686, and the trigger creates a new event record also with a location_ID of 8170daed-92c8-47f1-98ca-147800329686 and an event_ID of cfed8fe8-b5be-4f78-b366-008672e39637. |
|
|
|
|
|