Purge old events of databases "historical".

Hello

We look at some events in our historical databases see purge.  We've got floating pools that refresh on logoff user for the databases become big enough (> 30 GB).  I saw KB 1025914, but which refers the vCenter tasks and events.  Does anyone have experience with databases event_data_historical (and event_historical)?

Thank you

Troy

I am posting this because I hade the same question. My database of the event proved to be HUGE. Since we decided that we didn't need the old data, I decided to find a way to purge some data.

The sql query, I used is gross, but it worked. I'm not anything close to a person of sql query.

delete from [View-Event].[dbo].[v_event_data_historical]  where EventID in (select EventID from [View-Event].[dbo].[v_event_historical] where Time < DATEADD(day,-30,getdate()))
delete from [View-Event].[dbo].[v_event_historical] where Time < DATEADD(day,-30,getdate())

Our database is called event so our table prefixes are v_ and you will need to change your settings.

the

Time < DATEADD(day,-30,getdate()

is what I use to get specify anything older then 30 days. You want to change it to match your desires of retention.

I created a sql job to run this monthly to keep my size of database failure.

I'm sure there are better ways to do it, but it's the best I could come up with in the 20 minutes of time I had to work on it.

Justin

Tags: VMware

Similar Questions

  • Purge old data

    Hi all


    My database for EBS 11.5.10.2 size becomes very large and my users say they don't need data that is older than 5 years. Is it possible to erase the old data?


    Thank you very much

    Saeed,

    There is no direct way and/or support to delete old data. However, you can consult the following notes to clean your instance Oracle Apps redundant files and purge the database that is no longer necessary (and can be purged).

    Note: 274666.1 - cleaning one Instance of applications 11i of unnecessary files
    https://metalink2.Oracle.com/MetaLink/PLSQL/ml2_documents.showDocument?p_database_id=not&P_ID=274666.1

    Note: 732713.1 - purge strategy e-Business Suite 11i
    https://metalink2.Oracle.com/MetaLink/PLSQL/ml2_documents.showDocument?p_database_id=not&P_ID=732713.1

    Kind regards
    Hussein

  • Purge of events prior to a date specified on a Palm Z22 driver

    I want to remove (purge) of my calendar all events prior to a certain date. Any ideas how?

    Thank you.

    I should have said, DateBk 6 allows you to purge events prior to any date Select you.  Give it a try.

  • Conversion from an old file of database 2001

    Microsoft Open XML converter program open an old database file called "database.ddb" created in 2001 can be used with a current research program called "Anakiv7.1?"

    Suggestions appreciated.

    Herbaceous plant.

    Hello
     
     
    DDB is device-Dependent Bitmap. This file is saved in a proprietary format defined by the manufacturer of the video card. DDB files are not intended to be opened manually, even if they may be considered with an image editor third-party support. I'm not sure on Anakiv7.1 I would ask you to search for software on World Wide Web using your search engine favorite.
     
    WARNING:
    Using third-party software, including hardware drivers can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee that problems resulting from the use of third-party software can be solved. Software using third party is at your own risk.
     
    I hope this helps.

    Thank you, and in what concerns:
    Shekhar S - Microsoft technical support.

    Visit our Microsoft answers feedback Forum and let us know what you think.
    If this post can help solve your problem, please click the 'Mark as answer' or 'Useful' at the top of this message. Marking a post as answer, or relatively useful, you help others find the answer more quickly.

  • Purge old definitions of employment

    I have a problem in our development environment.  There are literally 4 x the number of definitions due to some copy and pasting of the working groups all over with hundreds of jobs in their.  I have now tons and tons of duplicates that are not active definitions.  Along the lines of like 40 k definitions developing for 10 k production I jobs care really all.

    I meet some performance issues and support is telling me that even inactive tasks have an important impact on performance.  Point of saying "well with the 40 k definitions, you are a great implementation and need more hearts, RAM, etc." by the SP2 performance tuning guide.  We are running 6.2.1.315

    In this logic, it seems that it would be more prudent to permanently purge definitions the 30 k that I don't need.  Does anyone has experiences in this sense?

    Jobs are already inactive, and I really I'm looking to do is purge them completely so that I'm back to a number of definitions (active and inactive handsets) that my hardware is scaled for already.  I am struggling already with the assertion that inactive jobs give me as much a performance hit as active jobs regarding the definition of the size of the implementation.

    Thank you!

    There is a new feature in the works that will allow to import and export the job definitions in XML files.

    Once they release that you will be able to export jobs unwanted for what is effectively a offline store and remove them from your active instances. Unlike now, you will have a useful recovery method if you still want to restore these defs job.

    Except that on the best thing to think about is that you capture instant database to keep a record of what's there and start pruning what whether you don't want or need. A copy of everything that you might want to keep your instance of Prod to DEV/UAT before starting to drop transportation stuff.

    Then, once you have identified Production repeat the exercise on DEV/UAT.

    I also recommend that you perhaps to reduce the retention for task time run story at least you can stand.

    See you soon

  • EM Event: WARNING: &lt; database Instance - &gt; officer down

    Hello

    by modernizing the plugins for the Patch Bundle WHO 12 and applying the BP on agents, I get a lot of emails with this issue - namely, a mail of each database instance and each listener running on the host computer.

    Content of the email is the following:
    Host = < host name >
    Target = Instance of database type
    Name of the target = < database name >
    Categories = availability
    Message = Agent down
    Severity = warning
    ...
    Availability status Agent down
    Rule name = database availability and critical States, target availability event rule
    Owner rule = SYSMAN

    Blackout on the host leads to WHO is not unable to do the upgrades - obviously an agent of blackout is not able to do. Wait what puzzles me in the rule mentioned in the letter, the incidents should only be created for the target type being down (i.e. for the instance database when the database is out of service and so on) as one.

    I'd rather not down all targets on a host UNLESS the agent because it does not age with our number of hosts and dbs, does anyone know what rule is responsible for the position and how they could be removed temporarily effectively?

    Also, please change your notification rules and subscribe to only mortals/critical events that will prevent this notification to database with the officer down.

    We are working on the event agent sends do not first place.

    (Jayakumar Sadras)

    Published by: user760389 on April 25, 2012 22:13

  • List - remove the old events in bulk

    One of my sites has several thousand former events and we need a way to be able to archive them and remove them from the hosting platform. It would be great if we could download them and then remove them in bulk.

    Also, anyone know what the correct process is now to add to the wish list?

    see you soon

    Deb

    You cannot export the actual events, but you can export customer report and booking Site Settings > custom reports. BTW, bookings have been renamed to events in the main menu but elsewhere, they are always qualified bookings.

    But you need to remove one events.

    m

  • Purge old data from the Vcenter Server - take 2

    I noticed this problem actually preceded in 2010 and appeared to trim back them:

    Try to download the files from these two KB, but the links seem to be dead.

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1025914

    File name: VCDB_Purge_MSSQL.zip

    And same thing here:

    http://KB.VMware.com/kb/2009918

    File name: 2009918_rebuild.zip

    A search in the download area provided no help.

    Any thoughts?

    Thank you

    James

    I just tried to download the files in question and it worked for me.

    I have attached it to this post, just in case.

  • Purge old data from the Vcenter Server

    Guys,

    I've been looking at a few questions and found the artcle I need to follow however I have a problem that is files are not connected correctly and I can't download attachments. Someone happens to have a copy or know where I can get one? The article in question is:

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1000125

    The file is: VCDB_PURGE_MSSQL.zip

    A search in the downloads section has not proven successful

    Thank you guys!

    looking for an attachment? The albums if file for vCenter 2.x and the bottom is for vCenter4.x

  • Event database configuration

    I plan on using a database of the event in our view vmware at current address environment, but I don't see anything in the installation guide on best practices for the design, execution, etc.  Our DBA wanted to let me know so I thought I'd see if anyone here is using this feature.  It is my understanding that events are recorded in the DB, which I want to use as an aid to troubleshooting and the user should things go wrong.  I really me who need to keep the events to the extent of the back 1 week see.  Someone who has already implemented this knows generally what size get the DBs and if it is possible to purge old events to manage their size?  Also, I would be interested to know the granularity of events that are the subject of a follow-up.  Thanks in advance

    Event database contains all the historical events of your view brokers so over time, it could become very large.

    There is no recommendation for the event of database sizing in 4.5 documentation. However it should not grow at a significant rate, unless there is a problem that results in thousands of events are triggered by the sight or if you have a huge floating pool environment, which will result in the commissioning and deleting linked clones periodically.

    In the event database, there are two parties, history and other is under tension. These are two different tables. Only events live can see in broker for connections and the other in an archived form. The amount of events live can be configured (as up to six months). The remaining part in the DB can be controlled by scripts SQL.

  • Is there a way to keep iCal all events no matter how old they are?

    It seems that iCal keeps only the events for a year.  I don't want them removed unless I do it myself.  If this is not possible, I would like a calendar app that did this and has an iPhone and Apple Watch app and synchronize via iCloud.  If anyone as any suggestions about this, I'd love to hear it.  I really like iCal, however.  That's what I've always used.  Thank you!

    For many years, I used an iCloud calendar on my Mac, the iPhone and the iPad.  I always update Apple software the day updates are published.

    Your post brought me to review my calendar on the Mac.  I found (surprise) an event in August, 2010 that I forgot to delete.  This event does not appear on my iPhone or iPad, because in both cases I have settings > Mail, Contacts, calendar > events Sync game to a few weeks.

    This Mac calendar program (iCal has not existed for several years) does not in itself the purge old events.

  • set the elimination date?

    I would like to purge old events, but older that they allow is 1 month. Is it possible to purge events 6 months or more?

    There is a possible way to purge events 6 months and even years.

    You must do on the computer and Treo/PDA.

    Here are the steps: on the Treo, you must set the time back to what date you want to purge the elements. Let you want to delete items, a year or 6 months from now on. Go to Prefs - select Date time & - under automatically value: select nothing (by default, it should indicate the Date, time and time zone)-change the date to 3/26 /08 Now, return to your calendar and it should appear at Wednesday, March 26, 2008. All you have to do at this stage is to switch to daily view, and then select the drop down - menu you will see Record - Edit - Options - under folder select Purge... and choose how you want to delete. Please uncheck the box that says - copy Archive save to PC.

    -------------------

    On the computer to do the same thing. Set the time of the computer from which date to purge the items to. All you have to do is basically follow the steps I have provided above.

    After completing please change the time to the correct settings.

    Message relates to: Centro (Sprint)

  • How to remove the alarms and events database of Citadel?

    Hello

    I use LV 2010 with DSC.

    I made a mistake in my program and I wrote too much data event and alarm at the Citadel. Database *.mdf/*.ldf files are quite large > 1 G. Normally, I connect only two alarms per day. I want to delete all events alarm + data before a certain time of stamps for example. 1.1.2011. How can I do? I tried to use MAX and perform the operation so I wrote small program which reach the data from temporary database and then remove it. Yet I can find old events and alarms... I am able to remove the traces of old but not the events/alarms. How do I remove the alarms and events?

    Thanks, Jim

    Hi Jim,.

    Have you seen this:

    http://forums.NI.com/T5/lookout/how-can-I-delete-alarm-and-event-data-from-a-Citadel5-database/m-p/5...

    Not sure if it is valid with the current version, but worth it.

  • Purge the database default...

    Is there a way to purge old records in the database by default... SQL CE?

    We need to upgrade to a full version of SQL, but until I would serve some data from the previous month, so I can at least see activity yesterday.

    Thanks for the help!

    -Evan

    Hey Evan,

    Here's the article for SQL Server:

    http://communities.quest.com/docs/doc-14838

    Your retention settings (Configuration-> retention settings) will only be applied when you stop and start your server service NMS Quest (ptserverservice.exe).

    Apart from this, stop the services you can manually delete all the files in data .sdf file. DO NOT DELETE ptdb.sdf. This file contains all of your devices, policies and other settings.

    c:\programdata\quest software\nms\nms server\nms db\

    Best regards

    Jonas

  • FDM Hyperion - Purging database

    We currently have 2 databases SQL to FDM and we noticed one of the databases is growing quite rapidly. Is there a way to purge data in this database? He is currently at more than 100 concerts in volume.

    First thing first...

    Know what hold of your data tables. :-) (And it of just not in the database, be sure to read to the bottom...)

    If it comes to SQL Server, the following query returns a list of tables to sort descending according to the reserved size...
    ----------

    create table #Temp (
        name nvarchar(128),
        [rows] char(11),
        reserved varchar(18),
        data varchar(18),
        index_size varchar(18),
        unused varchar(18)
        )  

insert into #Temp     exec sp_msforeachtable 'sp_spaceused ''?'''  

select * from #Temp order by cast(replace(reserved,' kb','') as int) desc

    ----------------------------
    If it comes to Oracle, the following should work.

    NOTE: I've not tested this. I do not use Oracle DB and I used Google on this one...

    COLUMN TABLE_NAME FORMAT A32
COLUMN OBJECT_NAME FORMAT A32
COLUMN OWNER FORMAT A10  

SELECT
     owner, table_name, TRUNC(sum(bytes)/1024/1024) Meg
FROM
     (SELECT segment_name table_name, owner, bytes
        FROM dba_segments
        WHERE segment_type = 'TABLE'
       UNION ALL
      SELECT i.table_name, i.owner, s.bytes
       FROM dba_indexes i, dba_segments s
       WHERE s.segment_name = i.index_name  AND   s.owner = i.owner  AND   s.segment_type = 'INDEX'
       UNION ALL
      SELECT l.table_name, l.owner, s.bytes
        FROM dba_lobs l, dba_segments s
        WHERE s.segment_name = l.segment_name  AND   s.owner = l.owner  AND   s.segment_type = 'LOBSEGMENT'
       UNION ALL
      SELECT l.table_name, l.owner, s.bytes
        FROM dba_lobs l, dba_segments s
        WHERE s.segment_name = l.index_name  AND   s.owner = l.owner  AND   s.segment_type = 'LOBINDEX')
        WHERE owner in UPPER('&owner')
      GROUP BY table_name, owner
      HAVING SUM(bytes)/1024/1024 > 10  /* Ignore really small tables */
      ORDER BY SUM(bytes) desc
 ;

    ---------

    Looking at an older version of a production application, I see the following distribution, although I can't say that all apps follow the same type of movement...
    (NOTE: I removed all the tables by using less than 1 MB of storage.)
    NOTE 2: It is System 9 and to use only some of the fields UD; Therefore, your mileage may vary on the structure of storage in this regard)

    name     rows     reserved     data     index_size     unused
tDataSeg3     279937          275184 KB     246952 KB     20592 KB     7640 KB
tLogActivity     685657          209888 KB     197192 KB     8432 KB     4264 KB
tDataSeg11     182200          193904 KB     175048 KB     13608 KB     5248 KB
tDataMapSeg26     481254          175992 KB     170112 KB     680 KB     5200 KB
tDataSeg14     178079          170992 KB     152416 KB     13320 KB     5256 KB
tDataMapSeg3     481556          154008 KB     146888 KB     544 KB     6576 KB
tDataMap     195123          151904 KB     61568 KB     64472 KB     25864 KB
tDataSeg7     151501          143856 KB     127936 KB     11168 KB     4752 KB
tDataMapSeg16     312707          105328 KB     98808 KB     384 KB     6136 KB
tDataSeg26     89242           101232 KB     89968 KB     7128 KB     4136 KB
tDataMapSeg11     273304          98912 KB     94208 KB     376 KB     4328 KB
tDataSeg32     91495           93104 KB     82616 KB     7176 KB     3312 KB
tDataMapSeg19     283639          88440 KB     81808 KB     312 KB     6320 KB
tDataMapSeg20     248051          87736 KB     82640 KB     344 KB     4752 KB
tDataMapSeg32     248865          85864 KB     83704 KB     352 KB     1808 KB
tDataSeg18     81340           81904 KB     71800 KB     6624 KB     3480 KB
tDataSeg30     81035           81072 KB     71528 KB     6464 KB     3080 KB
tDataMapSeg36     229741          80048 KB     73280 KB     304 KB     6464 KB
tDataMapSeg34     219324          78760 KB     71632 KB     304 KB     6824 KB
tDataMapSeg27     221756          75104 KB     69352 KB     272 KB     5480 KB
tDataSeg19     77515           74288 KB     65048 KB     5912 KB     3328 KB
tDataMapSeg18     191459          72096 KB     62264 KB     264 KB     9568 KB
tDataSeg43     72226           69872 KB     61176 KB     5528 KB     3168 KB
tDataSeg50     70821           69680 KB     61112 KB     5600 KB     2968 KB
tDataMapSeg30     185428          68400 KB     61400 KB     256 KB     6744 KB
tDataSeg27     70278           67888 KB     59216 KB     5400 KB     3272 KB
tDataSeg16     68043           67888 KB     59544 KB     5280 KB     3064 KB
tDataSeg10     66404           66096 KB     57328 KB     5448 KB     3320 KB
tDataSeg6     65131           62640 KB     54536 KB     5136 KB     2968 KB
tDataSeg17     62619           62000 KB     53848 KB     5160 KB     2992 KB
tDataMapSeg25     182191          61288 KB     54848 KB     224 KB     6216 KB
tDataSeg4     63183           60144 KB     52440 KB     4856 KB     2848 KB
tDataSeg13     59129           59568 KB     51120 KB     5136 KB     3312 KB
tDataCheck     83979           59168 KB     50768 KB     5216 KB     3184 KB
tDataMapSeg35     155093          58536 KB     52120 KB     216 KB     6200 KB
tDataSeg44     56930           55280 KB     48224 KB     4384 KB     2672 KB
tDataSeg28     52973           53552 KB     46064 KB     4464 KB     3024 KB
tDataSeg40     53716           50992 KB     43760 KB     4272 KB     2960 KB
tDataSeg45     46505           50864 KB     43944 KB     3960 KB     2960 KB
tDataMapSeg17     133623          48744 KB     40480 KB     168 KB     8096 KB
tDataMapSeg40     132736          46952 KB     39328 KB     168 KB     7456 KB
tDataSeg5     46120           46448 KB     39512 KB     4072 KB     2864 KB
tDataSeg38     45780           46320 KB     39784 KB     3824 KB     2712 KB
tDataMapSeg28     133729          46256 KB     38632 KB     168 KB     7456 KB
tDataSeg20     44443           45872 KB     39512 KB     3704 KB     2656 KB
tDataSeg25     45071           45808 KB     38776 KB     4144 KB     2888 KB
tDataMapSeg21     132169          45408 KB     37928 KB     160 KB     7320 KB
tDataSeg34     43714           44848 KB     38072 KB     4000 KB     2776 KB
tDataMapSeg14     120765          44776 KB     36344 KB     152 KB     8280 KB
tDataMapSeg24     124262          44640 KB     37520 KB     168 KB     6952 KB
tDataMapSeg33     129193          44064 KB     38648 KB     160 KB     5256 KB
tDataMapSeg13     112591          43680 KB     35256 KB     152 KB     8272 KB
tDataSeg47     42138           43488 KB     37352 KB     3432 KB     2704 KB
tDataSeg21     42383           43376 KB     36232 KB     3888 KB     3256 KB
tDataMapSeg10     118447          42976 KB     35416 KB     152 KB     7408 KB
tDataSeg29     43008           42864 KB     36952 KB     3600 KB     2312 KB
tDataSeg23     41458           41520 KB     36184 KB     3232 KB     2104 KB
tDataSeg33     38297           41376 KB     35784 KB     3032 KB     2560 KB
tDataSeg39     38325           39792 KB     33728 KB     3520 KB     2544 KB
tDataSeg49     39926           39536 KB     33648 KB     3136 KB     2752 KB
tDataMapSeg29     104805          38688 KB     32416 KB     144 KB     6128 KB
tDataSeg35     36451           37744 KB     32040 KB     3208 KB     2496 KB
tDataSeg22     35486           37040 KB     31296 KB     3088 KB     2656 KB
tDataMapSeg7     92215           35816 KB     28752 KB     128 KB     6936 KB
tDataMapSeg31     92202           35360 KB     28616 KB     136 KB     6608 KB
tDataMapSeg45     93919           35184 KB     29552 KB     128 KB     5504 KB
tDataSeg36     35311           35184 KB     29200 KB     3064 KB     2920 KB
tDataMapSeg50     84859           33384 KB     26720 KB     128 KB     6536 KB
tDataMapSeg4     82558           33376 KB     25744 KB     120 KB     7512 KB
tDataSeg37     31768           32752 KB     27568 KB     2712 KB     2472 KB
tDataMapSeg9     82775           32224 KB     26264 KB     120 KB     5840 KB
tDataMapSeg43     90283           32160 KB     27368 KB     136 KB     4656 KB
tDataMapSeg22     83091           32104 KB     25664 KB     120 KB     6320 KB
tDataSeg2     31335           30384 KB     25120 KB     2752 KB     2512 KB
tDataMapSeg5     81919           30240 KB     24064 KB     120 KB     6056 KB
tDataMapSeg39     78626           28640 KB     22912 KB     104 KB     5624 KB
tDataMapSeg47     81916           28512 KB     24328 KB     104 KB     4080 KB
tDataMapSeg23     73815           28512 KB     23600 KB     112 KB     4800 KB
tDataSeg9     27965           28400 KB     23560 KB     2584 KB     2256 KB
tDataMapSeg15     67203           26848 KB     20816 KB     96 KB     5936 KB
tDataMapSeg38     74979           26720 KB     22464 KB     112 KB     4144 KB
tDataMapSeg12     66532           26720 KB     20376 KB     104 KB     6240 KB
tDataMapSeg6     68627           26336 KB     20160 KB     104 KB     6072 KB
tDataMapSeg2     64820           25952 KB     20816 KB     96 KB     5040 KB
tDataMapSeg44     70004           25832 KB     20016 KB     96 KB     5720 KB
tDataMapSeg49     73613           25200 KB     20584 KB     88 KB     4528 KB
tDataSeg24     25070           25008 KB     21048 KB     2152 KB     1808 KB
tDataMapSeg37     57634           22496 KB     17536 KB     88 KB     4872 KB
tDataArchive     33012           21216 KB     9376 KB     6600 KB     5240 KB
tDataMapSeg42     53057           20704 KB     15432 KB     80 KB     5192 KB
tDataSeg12     19301           20336 KB     16616 KB     1816 KB     1904 KB
tDataSeg31     18537           18992 KB     15672 KB     1584 KB     1736 KB
tDataSeg46     17973           18800 KB     15384 KB     1744 KB     1672 KB
tDataSeg48     18481           18288 KB     14896 KB     1736 KB     1656 KB
tDataMapSeg8     40631           17952 KB     13408 KB     80 KB     4464 KB
tDataSeg42     15766           16880 KB     13568 KB     1536 KB     1776 KB
tDataMapSeg48     40179           16352 KB     12256 KB     64 KB     4032 KB
tDataSeg41     13274           14320 KB     11696 KB     1216 KB     1408 KB
tDataSeg8     12027           13152 KB     10368 KB     1144 KB     1640 KB
tDataMapSeg46     28647           12584 KB     9840 KB     56 KB     2688 KB
tDataSeg15     9418            10288 KB     8136 KB     832 KB     1320 KB
tDataMapSeg41     23887           9504 KB     7048 KB     48 KB     2408 KB
tLogProcess     10878           5808 KB     3240 KB     1040 KB     1528 KB
tCtrlMetaCaptionsTranslated     44830           4752 KB     4696 KB     56 KB     0 KB
tSecObjectItems_Locale     16371           2768 KB     2664 KB     72 KB     32 KB
tCtrlMetaData     13463           2528 KB     1528 KB     904 KB     96 KB

    So, unsurprisingly, most of the data is sitting in the data Segments and Segments of card data; However, the activity log is #2 in my database.

    Activity log is probably relatively safe to clean under the assumption that meet you the requirements of audit/SOX with your cleaning info. (i.e. empty each year, etc.)

    At the point of the other displays; However, the other tables will really cut into data and maps for the data. You must take a decision as to if it is something from which your group is ok. Perhaps you take the approach of windows and delete the old data after a period of xx?

    Finally, do not discount the raw data files, log files, temporary files and 'export' that are generated by FDM. In a relatively small application, we have accumulated almost 200 000 files over a period of 3 years. Don't forget to keep an eye on these files. Even if they are for the most part, small files, they occupy space! As for the database, I recommend an approach where you delete some of the files or even compress them into one archive for guard duty.

    Hope that helps.

    P. S.

    If you decide you want to clean up the data, the column PeriodKey in the DataMapSeg / DataSeg tables indicates if the data comes from. (i.e. the 00:00:00.000 2008-06-30) You can use this to run a script to clean up the tables for the data before a certain date, etc..

    Published by: beyerch2 on July 3, 2012 09:16

Maybe you are looking for