Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 308895
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T07:41:32+00:00 2026-05-12T07:41:32+00:00

Here is the situation: I have a database of ‘tickets’, and we track changes

  • 0

Here is the situation:

I have a database of ‘tickets’, and we track changes to the tickets each time they are saved. I am specifically looking at status changes, which track with the following format:

STATUS:{FROM}:{TO}

with {FROM} and {TO} changing to the respective statuses. What I need to do is generate numbers by weeks of the amount of tickets that were ‘open’ (meaning in draft status) at the end of any given week, say for the past 12 weeks. However, you are not limited to ‘closing’ a ticket and then reopening it, or making multiple changes in a single week.

So, what I need to do is modify the SQL below to ONLY consider the most recent “action” for any given entry. This way we avoid the problem of having entries that were ‘closed’ appear in the open count because they had been opened earlier.

SELECT track.historyID
      FROM RS_HistoryTracker track 
     WHERE (track.action = 'STATUS:INITIAL:DRAFT'
            OR track.action = 'STATUS:DELETED:DRAFT'
            OR track.action = 'STATUS:DRAFT:DRAFT')
       AND track.trackDateTime <= @endOfWeek

However, this statement is contained within another select statement, and is used to generate a complete list of history items:

    SELECT COUNT(DISTINCT his.historyID) AS theCount
  FROM RS_History his
 WHERE his.historyID IN 
       (SELECT track.historyID
          FROM RS_HistoryTracker track 
         WHERE (track.action = 'STATUS:INITIAL:DRAFT'
                OR track.action = 'STATUS:DELETED:DRAFT'
                OR track.action = 'STATUS:DRAFT:DRAFT')
           AND track.trackDateTime <= @endOfWeek) 

So how do I make the inner select consider only the most recent tracked ‘action’ that occured up to or on the endOfWeek date? HistoryTracker contains a datetime stamp column.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T07:41:33+00:00Added an answer on May 12, 2026 at 7:41 am

    Looks like this works:

      SELECT query.historyID
        FROM
        (SELECT MAX(track.trackID) AS maxTrackID, track.historyID
        FROM RS_HistoryTracker track
        WHERE track.trackDateTime <= '2009-08-06 23:59:59'
          AND track.action LIKE 'STATUS:%'
        GROUP BY historyID) AS query, RS_HistoryTracker track
        WHERE track.historyID = query.historyID
          AND track.trackID = query.maxTrackID
          AND track.action LIKE 'STATUS:%:DRAFT'
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Here's the situation Over the time I will have a MySQL database with around
Here's the situation. Due to the design of the database I have to work
Here is my situation. I have written a Database application in Java. Now (unfortunately
Here's the situation I'm in: We have a field in our database that contains
So here is the situation. I have a database on a remote server that
I have faced a very strange situation here. I am accessing database (MDB) through
Here's the situation: In my database i have a table with threads, and a
Here's the situation: we have an Oracle database we need to connect to to
Here is the situation we have: a) I have an Access database / application
Here's a situation, i have a list of support tickets that when you click

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.