[Orgmode] Re: Org mode as an helper tool for my job position (DBA)

[Bernt Hansen]

Xavier Maillard <address@hidden> writes:

> Hi,
>

Hi!

> Producing the right org-mode file structure from any script/c code is rather
> simple, in fact, I have done this as a quick and dirty hack for one tool.
>
> Where I am failing is in having a column view of the document (I want to be 
> able
> to only view time spent for each object name to measure the performance of the
> last update statistics run).
>
> What would I need to add for each of the table/index "todo" entry to have this
> information at hand ?
>
> As an example, updating index statistics will present an org file like this 
> one:
>
> #title Update statistics of sql server
>
> * General information
> - start date
> - end date
> - return code
>
> * Index statistics (I want column view from here for each object name)
> ** Index name 1
> informations for index name 1 go here (time spent, etc...)
> ** Index name 2
> * Index name <n>
> ...
>

Here's a sample org file.  Just add properties to the tasks (objects)
you need in the column view and a #+COLUMNS: line describing what fields
to include in the columns.

,----[ Sample org file ]
| #+STARTUP:
| #+COLUMNS: %40ITEM(Task) %30Status(Status) %30TimeSpent(Time Spent){:}
| * General information
| - start date
| - end date
| - return code
| 
| * Index statistics (I want column view from here for each object name)
| ** Index name 1
| informations for index name 1 go here (time spent, etc...)
| :PROPERTIES:
| :TimeSpent: 00:30
| :Status: S42
| :END:
| ** Index name 2
| :PROPERTIES:
| :TimeSpent: 00:17
| :Status: R19
| :END:
| * Index name <n>
| :PROPERTIES:
| :TimeSpent: 02:16
| :Status: 42
| :END:
`----

Hope that helps,

Bernt