Update once only most current record that meets conditions

Question

Want to only allow the most current date with the stateID of 1 to update once and not update after the intial update when running sql code over again. 
changeTypeID containerID    stateID dateEntered                               note
UPDATE          900172-0800  5       2014-09-23 04:38:29.313            Pallet #71809
UPDATE          900172-0800  1       2014-11-20 09:17:51.017 
UPDATE          900172-0800  10      2014-11-24 15:03:32.177   900172-0800->Destroyed
UPDATE          900172-0800  10      2014-11-24 15:04:00.777   900172-0800->Destroyed
UPDATE          900172-0800  10      2014-11-24 15:05:44.763   900172-0800->Destroyed
SELECT containerID
INTO #Temp
      ContainerHistory
      WHERE dateEntered >= DATEADD(DAY, DATEDIFF(DAY, 0, CURRENT_TIMESTAMP) -1, 0)
        AND dateEntered < DATEADD(DAY, DATEDIFF(DAY, 0, CURRENT_TIMESTAMP), 0)
        AND stateID = 1 ORDER BY dateEntered DESC ????
UPDATE ContainerStates
  SET stateID = 10,
   dateEntered = getdate(),
   note = containerID + '->Destroyed'
  WHERE containerID IN (
   SELECT barCode AS containerID FROM #Temp WHERE containerExpired = 1

Answer 1

>> Want to only allow the most current date with the state_id of 1 to update once and not update after the initial update when running SQL code over again. <<
Please follow basic Netiquette and post the DDL we need to answer this. Do you know how to follow industry and ANSI/ISO standards? You should follow ISO-11179 rules for naming data elements. You hjave noi idea what that means.  Avoid dialect in favor of
ANSI/ISO Standard SQL. 
There is no such attribute as a “change_type_id” in RDBMS. You can have a “<something>_id” “<something>_type” but not a weird mix of attribute proprieties. Likewise, “state_id” makes no sense. If you meant a status, then you need two dates to show
when that state of being applied to the entity. 
To track the history of, say, Foobars we need to see time as a continuum and model it as (begin_date, end_date) pairs that define when a foobar had a particular value. Here is the skeleton. 
CREATE TABLE Foobar_History 
(foo_id CHAR(9) NOT NULL, 
 start_date DATE NOT NULL, 
 end_date DATE, --null means current 
 CHECK (start_date <= end_date),
 foo_status INTEGER NOT NULL, 
 PRIMARY KEY (foo_id, start_date)); 
When the end_date is NULL, that state of being is still current. You use a simple query for the status on any particular date;
SELECT * 
  FROM Foobar
 WHERE @in_cal_date
     BETWEEN start_date
      AND COALESCE (end_date, CURRENT_TIMESTAMP);
There are more tricks in the DDL to prevent gaps, etc
CREATE TABLE Events
(event_id CHAR(10) NOT NULL,
 previous_event_end_date DATE NOT NULL  
 CONSTRAINT Chained_Dates  
  REFERENCES Events (event_end_date), 
 event_start_date DATE NOT NULL, 
 event_end_date DATE UNIQUE, -- null means event in progress
  PRIMARY KEY (event_id, event_start_date), 
 CONSTRAINT Event_Order_Valid 
  CHECK (event_start_date <= event_end_date), 
 CONSTRAINT Chained_Dates 
  CHECK (DATEADD(DAY, 1, previous_event_end_date) = event_start_date)
-- CHECK (previous_event_end_date + INTERVAL '01' DAYS) = event_start_date)
-- disable the Chained_Dates constraint
ALTER TABLE Events NOCHECK CONSTRAINT Chained_Dates;
GO
-- insert a starter row
INSERT INTO Events(event_id, previous_event_end_date, event_start_date, event_end_date)
VALUES ('Foo Fest', '2010-01-01', '2010-01-02', '2010-01-05');
GO
-- enable the constraint in the table
ALTER TABLE Events CHECK CONSTRAINT Chained_Dates;
GO
-- this works
INSERT INTO Events(event_id, previous_event_end_date, event_start_date, event_end_date)
VALUES ('Glob Week', '2010-01-05', '2010-01-06', '2010-01-10');
-- this fails
INSERT INTO Events(event_id, previous_event_end_date, event_start_date, event_end_date)
VALUES ('Snoob', '2010-01-09', '2010-01-11', '2010-01-15'); 
What you did post is awful. Why did you append “->Destroyed” to an identifier? This is redundant AND destroys the integrity of the original encoding. Why do you use a local temp table? This mimics a  1950's scratch tape and no SQL programmer would use
it. Why would a note repeat another column? 
Please read this and try again. 
https://www.simple-talk.com/sql/t-sql-programming/state-transition-constraints/
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL