<div>
WOW! Thank you very much!!!!! That was very fast. However, the first part works just jut but the second part is being ignorer. So, if I remove AssignedTo from TERRITORIES the trigger does not clear the AssignedTo in Data and does not remove the DateAssigned on TERRITORIES :-(
</div>


<div>
can you please clarify &quot;remove&quot;, how exactly does this happen? do you set NULL or an empty string?<br />
if it's an empty string, this needs to be handled differently
</div>


<div>
Just some comments:<br />
<br />
Why do you store the e-mail address in a separate table? This is redundancy and can lead to an anomaly.<br />
<br />
Consider this:<br />
<br />
1. User A with e-mail address a@a.com is assigned to a territory A.<br />
Contenent of DATA: Territory A, E-Mail a@a.com<br />
<br />
2. User A changes his e-mail address, e.g. got married, to b@a.com.<br />
Contenent of DATA: Territory A, E-Mail a@a.com<br />
<br />
Now any mail maybe send to a dead mailbox.<br />
<br />
Why not using a view instead?<br />
<br />
And then: Assigning a NULL to AssignedTo is a data model error. You should have two tables. One defining the territories and on the assignments. When an assignment is canceled, then the row must be deleted from the assignments table. This would also solve the DateAssigned NULL problem.
</div>


<div>
You are correct Guy, after testing the trigger by updating the AssignedTo field using the application it works just fine, so the app does actually set the field to NULL. &nbsp;Before, I was testing the trigger directly in SQL (editing) by manually removing the AssignedTo value.
</div>


<div>
<div class="content wysiwyg-content">
Hello, I need help in writing a Trigger that will fire when the field AssignedTo if update in table TERRITORIES<br />
This are the tables and fields I am working with:<br />
TERRITORIES, AssignedTo, DateAssigned, Territory<br />
USERS, LastFirst, eMail<br />
DATA AssignedTo, Territory<br />
<br />
This is the way the process needs to work:<br />
<br />
1. When TERRITORIES.AssignedTo is updated by a user <br />
2. IF Not Is Null TERRITORIES.AssignedTo Then<br />

<div class="indent">
3. TERRITORIES.DateAssigned = GetDate()
</div>
<div class="indent">
4.Then find USERS.LastFirst = TERRITORIES.AssignedTo and read the column called eMail for this user
</div>
<div class="indent">
5. Then update DATA.AssignedTo with that user eMail where TERRITORIES.Territory = DATA.Territory
</div>
6. Else ‘ It the TERRITORIES.AssignedTo changes from a name to Null<br />

<div class="indent">
7. TERRITORIES.DateAssigned = Null
</div>
<div class="indent">
8. DATA.AssignedTo = Null where TERRITORIES.Territory = DATA.Territory
</div>
9. End If<br />
<br />
Let me know if you need clarification in any of the pseudo steps
</div>
</div>


Hello, I need help in writing a Trigger that will fire when the field AssignedTo if update in table TERRITORIES
This are the tables and fields I am working with:
TERRITORIES, AssignedTo, DateAssigned, Territory
USERS, LastFirst, eMail
DATA AssignedTo, Territory

This is the way the process needs to work:

1. When TERRITORIES.AssignedTo is updated by a user 
2. IF Not Is Null TERRITORIES.AssignedTo Then
3. TERRITORIES.DateAssigned = GetDate()
4.Then find USERS.LastFirst = TERRITORIES.AssignedTo and read the column called eMail for this user
5. Then update DATA.AssignedTo with that user eMail where TERRITORIES.Territory = DATA.Territory
6. Else ‘ It the TERRITORIES.AssignedTo changes from a name to Null
7. TERRITORIES.DateAssigned = Null
8. DATA.AssignedTo = Null where TERRITORIES.Territory = DATA.Territory
9. End If

Let me know if you need clarification in any of the pseudo steps

Help writing SQL Trigger

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.