Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Are you looking for something like this?</p> <pre><code>WITH cte AS ( SELECT * FROM ( SELECT t.*, ROW_NUMBER() OVER (PARTITION BY RequestNo ORDER BY LastActionDate) rnum FROM Table1 t ) q ) SELECT c1.RequestNo, c1.usercode, COALESCE(c2.LastActionDate, c1.LastActionDate) ReceivedDate, c1.LastActionDate, c1.ActionType, DATEDIFF(day, COALESCE(c2.LastActionDate, c1.LastActionDate), c1.LastActionDate) Aging FROM cte c1 LEFT JOIN cte c2 ON c1.RequestNo = c2.RequestNo AND c1.rnum = c2.rnum + 1 ORDER BY RequestNo, LastActionDate </code></pre> <p>Output:</p> <pre> | REQUESTNO | USERCODE | RECEIVEDDATE | LASTACTIONDATE | ACTIONTYPE | AGING | |-----------|----------|---------------------------------|---------------------------------|--------------------|-------| | REQ1 | 407 | December, 14 2012 09:47:00+0000 | December, 14 2012 09:47:00+0000 | Saved | 0 | | REQ1 | 407 | December, 14 2012 09:47:00+0000 | December, 14 2012 09:48:00+0000 | Submitted | 0 | | REQ1 | 407 | December, 14 2012 09:48:00+0000 | December, 14 2012 09:48:00+0000 | Approved | 0 | | REQ1 | 203 | December, 14 2012 09:48:00+0000 | December, 17 2012 09:54:00+0000 | Reviewed | 3 | | REQ1 | 242 | December, 17 2012 09:54:00+0000 | December, 18 2012 10:29:00+0000 | WF Setup in Dev. | 1 | | REQ1 | 203 | December, 18 2012 10:29:00+0000 | December, 18 2012 15:14:00+0000 | Transport to prod. | 0 | | REQ1 | 242 | December, 18 2012 15:14:00+0000 | December, 18 2012 15:16:00+0000 | Completed | 0 | | REQ2 | 407 | December, 27 2012 10:36:00+0000 | December, 27 2012 10:36:00+0000 | Submitted | 0 | | REQ2 | 456 | December, 27 2012 10:36:00+0000 | December, 27 2012 11:18:00+0000 | Approved | 0 | | REQ2 | 407 | December, 27 2012 11:18:00+0000 | December, 27 2012 11:27:00+0000 | Approved | 0 | | REQ2 | 203 | December, 27 2012 11:27:00+0000 | December, 27 2012 17:34:00+0000 | Reviewed | 0 | | REQ2 | 242 | December, 27 2012 17:34:00+0000 | December, 28 2012 14:07:00+0000 | WF Setup in Dev. | 1 | | REQ2 | 203 | December, 28 2012 14:07:00+0000 | December, 28 2012 14:11:00+0000 | Transport to prod. | 0 | | REQ2 | 242 | December, 28 2012 14:11:00+0000 | December, 28 2012 21:27:00+0000 | Completed | 0 | | REQ3 | 407 | December, 27 2012 11:32:00+0000 | December, 27 2012 11:32:00+0000 | Submitted | 0 | | REQ3 | 456 | December, 27 2012 11:32:00+0000 | December, 27 2012 11:33:00+0000 | Approved | 0 | | REQ3 | 407 | December, 27 2012 11:33:00+0000 | December, 27 2012 11:34:00+0000 | Approved | 0 | | REQ3 | 203 | December, 27 2012 11:34:00+0000 | December, 27 2012 17:33:00+0000 | Reviewed | 0 | | REQ3 | 242 | December, 27 2012 17:33:00+0000 | December, 27 2012 18:33:00+0000 | WF Setup in Dev. | 0 | | REQ3 | 203 | December, 27 2012 18:33:00+0000 | December, 28 2012 13:43:00+0000 | Transport to prod. | 1 | | REQ3 | 242 | December, 28 2012 13:43:00+0000 | January, 03 2013 14:56:00+0000 | Completed | 6 | </pre> <p>Here is <strong><a href="http://sqlfiddle.com/#!3/7bab1/12" rel="nofollow">SQLFiddle</a></strong> demo</p>
    singulars
    1. This table or related slice is empty.
    1. PODate Aging Report + Cummulative
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USpeterm
    1. USpeterm
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COyes it help, but need to compute the difference between the dates, then the cumulative dates the requests has been processed
      singulars
      1. PO
      1. USnigel
    2. COSee updated answer. `Aging` is added. Can you explain in details how `Cummulative` is supposed to be calculated?
      singulars
      1. PO
      1. USpeterm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload