LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (December 1999, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 10 Dec 1999 16:19:33 GMT
Reply-To:     Xlr82sas <xlr82sas@AOL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Xlr82sas <xlr82sas@AOL.COM>
Organization: AOL http://www.aol.com
Subject:      Re: Reading Oracle Clinical data using SAS

My experience with summarizing large multiyear FDA 'Lab Studies' was different. Have you tried to summarize 15-20 lab tests ( ie WBC, HGB etc White Blood Cell Counts) for 5000 patients over three years. Pass thru to Oracle Clinical was at least an order of magnitude slower than using native SAS tables.

For a quick synopsis of the entities and process flow for adverse event reports through Oracle Clinical you might visit my site.

Have you done any benchmarking comparing native SAS tables to Pass thru to Oracle.

The heart of the Oracle Clinical design ( 2 years ago) was a very skinny long table. A single column, contained both character and numeric data ( in character format, I think). I counted about 5 or 6 levels of indirection ( views) before you got to this table. Lab data, demographic data etc were all in this one table. Obviously this table can get very large.

Perhaps you can throw enough hardware at this design to quick responses.

I have tried to have constructive discussions on the Oracle design with others, but after I tell them my findings they stop responding. Roger J DeAngelis CompuCraft Inc XLR82SAS@aol.com ( Accelerate to SAS ) http://members.aol.com/xlr82sas/utl.html


Back to: Top of message | Previous page | Main SAS-L page