BIOCHEM Database Application System. Archival Account Database Dictionary. Edited January 2006
|
|
|
- Arleen King
- 10 years ago
- Views:
Transcription
1 BIOCHEM Database Application System Archival Account Database Dictionary Prepared for The Department of Fisheries and Oceans Canada Application Services Division Bedford Institute of Oceanography Informatics Branch, Maritimes Region Version 4.0 as of 20 Feb 2002 Edited January 2006 INTRODUCTION... 2 Database Table Security Permissions (BIOCHEM Account)...Error! Bookmark not defined. BIOCHEM DATABASE OBJECTS... 2 DESCRIPTION OF THE BIOCHEM ACCOUNT OBJECTS... 2 Entity Relationship Diagrams (ERD)... 3 Table Names and Table Comments (BIOCHEM Account)... 8 Table Column Descriptions (BIOCHEM Account) Sequences (BIOCHEM Account) Primary Key and Foreign Key Constraints (BIOCHEM Account) View Definitions (BIOCHEM Account) Synonyms (BIOCHEM Account) Stored Program Units (BIOCHEM account) LOOKUP TABLE DATA APPENDIX A (TABLE NAME TRANSLATION/CLARIFICATION) APPENDIX B (BIOCHEM DOCUMENT CATALOGUE)... 30
2 Introduction The BioChem System version 6 is made up of following the two subsystems: BioChem Archival/Edits system version 4.0 BioChem Query System version 3.0. The BioChem Archival System is comprised of one or more Oracle 8I data manager accounts and an Oracle Forms 6I application. The Application is used to validate and edit the data in the data manager account. Once the data is valid then it may be archived to another Oracle 8I account called the BioChem archive account. The BioChem Query System is comprised of an Oracle 8I query account and an Oracle Form 6I application. The application is used to create and execute query definitions that are based on data archived in another Oracle 8I account called the BioChem archive account. The common component of the two BioChem subsystems above is the BioChem archive account. The BioChem Archival/Edits System adds data to the BioChem archive via the data manager accounts, while the BioChem Query System creates and executes queries based on the data stored in the BioChem archive. This document will focus on the Oracle 8I database objects required by the two subsystems. For ease of use this document will make reference only to those objects implemented in this Version of the system.. BIOCHEM Database Objects Description of the BIOCHEM Account Objects The BIOCHEM database objects (tables, sequences, indexes, etc.) are separated into three separate accounts. The first Oracle database account is known as the Data Manager Account (or the Edit Account). This account contains all of the tables used to load the initial raw data, validate and correct the errors in the data and tables used to temporarily store the data until all data is processed for a given batch. For further information on the Oracle database objects within this account please see the document BCEDITS_data_dictionary_v4.0. The second database account is known as the query account (BCQRY). This account contains all the tables used to create and execute queries based on the data contained in the data. For further information on the Oracle database objects within this account please see the document BCQRY_data_dictionary_v3.0. The third Oracle database account is known as the BIOCHEM Archival Account. This account contains the following logical table grouping: Archival tables - store the validated discrete and plankton data that is queried upon by all users. Audit Trail table - tracks the changes to the archived data via the data manager EDIT tables. Lookup Tables (also known as code tables) - store the commonly referenced codes, which are used by the data tables in the Data Manager Account(s), query definition tables, the Archival tables, and the Deleted Database Tables. Deleted Database Tables -store the data that a Data Manager has deleted from the Archival database tables in the BIOCHEM account using the Archival/Edits application ver
3 Entity Relationship Diagrams (ERD) The Entity Relationship Diagram(s) displayed in this section depict the BIOCHEM database as distinctly separate areas of functionality. This is somewhat true since different types of data are being accommodated and saved in the tables. Here is a list of the separate ERD diagrams that have been included in this section: Archival DataTables (Common, Discrete and Plankton) Archival Deletes Tables (Common, Discrete and Plankton) Archival Audit Table Archival Lookup(Code) Tables The ERD diagrams separate the Archival Data Tables by "areas of functionality", which refers to a logical collection of tables in the diagram in order to focus on the relationships of the tables for one type of data. Diagrams are given for both the Plankton functional area and the Discrete functional area. These diagrams are rather small in size as well. Please increase the "Zoom" (if viewing this document using MS Word 97 or greater) to 200% or greater in order to make the details of the diagrams legible. 3
4 ARCHIVAL DATA TABLES These tables store the data records that were archived using the BioChem Archival/Edits Application. 4
5 ARCHIVAL DELETES TABLES These tables store the records that were deleted from the archive using the BioChem Archival/Edits Application. Note: There are no foreign key constraints on the DELETES tables. 5
6 ARCHIVAL AUDIT TABLE This table stores a record for each archival data item changed using the BioChem Archival/Edits Application. 6
7 ARCHIVAL LOOKUP TABLES BCCOLLECTIONMETHODS collection_method_seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL desc ription: VARCHAR2(1000) NULL BCDATAPOINTERS data_pointer_code: VARCHAR2(2) NOT NULL table_name: VARCHAR2(30) NOT NULL des cription: VARCHAR2(250) NULL functional_area: VARCHAR2(30) NOT NULL active: VARCHAR2(1) NOT NULL BCDATARETRIEVALS data_retrieval_seq: NUMBER(8) NOT NULL parameter_name: VARCHAR2(20) NOT NULL parameter_description: VARCHAR2(100) NOT NULL unit_seq: NUMBER(8) NOT NULL (FK) places _before: NUMBER(2) NOT NULL places _after: NUMBER(2) NOT NULL minimum_v alue: NUMBER(12,5) NULL max imum_value: NUMBER(12,5) NULL originally_entered_by: VARCHAR2(30) NOT NULL BCDATATYPES data_type_seq: NUMBER(8) NOT NULL data_retrieval_seq: NUMBER(8) NOT NULL (FK) analysis_seq: NUMBER(8) NOT NULL (FK) preservation_seq: NUMBER(8) NOT NULL (FK) sample_handling_seq: NUMBER(8) NOT NULL (FK) storage_seq: NUMBER(8) NOT NULL (FK) unit_seq: NUMBER(8) NOT NULL (FK) description: VARCHAR2(100) NOT NULL c onversion_equation: VARCHAR2(250) NULL originally_entered_by: VARCHAR2(30) NOT NULL method: VARCHAR2(20) NOT NULL priority: NUMBER(2) NOT NULL p_c ode: CHAR(4) NULL BCANALYSES analysis _seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL des cription: VARCHAR2(250) NULL BCPRESERVATIONS preservation_seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL desc ription: VARCHAR2(250) NULL type: VARCHAR2(30) NULL BCSAMPLEHANDLINGS sample_handling_seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL desc ription: VARCHAR2(250) NULL BCSTORAGES storage_seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL des cription: VARCHAR2(250) NULL BCUNITS unit_seq: NUMBER(8) NOT NULL name: VARCHAR2(20) NOT NULL desc ription: VARCHAR2(100) NULL BCDERIVATIONS derived_seq: NUMBER(8) NOT NULL parameter_name: VARCHAR2(20) NOT NULL desc ription: VARCHAR2(250) NULL BCDATACENTERS data_center_code: NUMBER(2) NOT NULL name: VARCHAR2(50) NOT NULL location: VARCHAR2(50) NOT NULL desc ription: VARCHAR2(100) NULL BCNATNLTAXONCODES national_taxonomic _seq: NUMBER(14) NOT NULL TSN: NUMBER(12) NOT NULL taxonomic _name: VARCHAR2(100) NOT NULL best_nodc7: NUMBER(12) NOT NULL authority : VARCHAR2(50) NULL c ollectors_comment: VARCHAR2(2000) NULL data_managers_comment: VARCHAR2(2000) NULL short_name: VARCHAR2(15) NULL BCGEARS gear_seq: NUMBER(8) NOT NULL type: VARCHAR2(40) NOT NULL model: VARCHAR2(50) NULL gear_siz e: VARCHAR2(20) NULL desc ription: VARCHAR2(2000) NULL BCERRORCODES error_code: NUMBER(4) NOT NULL description: VARCHAR2(80) NOT NULL long_desc : VARCHAR2(300) NULL last_update_by : VARCHAR2(30) NOT NULL last_update_date: DATE NOT NULL BCEDITPROCFLAGS process _flag: VARCHAR2(3) NOT NULL name: VARCHAR2(50) NOT NULL desc ription: VARCHAR2(250) NULL BCLIFEHISTORIES life_history_seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL description: VARCHAR2(1000) NULL molt_number: VARCHAR2(20) NULL BCPROCEDURES procedure_seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL description: VARCHAR2(1000) NULL BCSEXES sex_seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL desc ription: VARCHAR2(1000) NULL BCVOLUMEMETHODS volume_method_seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL description: VARCHAR2(1000) NULL BCQUALCODES qc_code: VARCHAR2(2) NOT NULL qc_definition: VARCHAR2(100) NOT NULL BCTROPHICDESCRIPTORS trophic _seq: NUMBER(8) NOT NULL name: VARCHAR2(30) NOT NULL description: VARCHAR2(1000) NULL 7
8 The following sections identify the various tables that are created in the BIOCHEM Archival Account. Table Names and Table Comments (BIOCHEM Account) Decide whether to write table stores or just stores below Plus stores information or stores description Table Stores is poor but not worth the effort to change Pierre need to check null vs not null and format for tables Foreign key references or reference??? Table Name Archival DataTables BCMISSIONS BCEVENTS BCCOMMENTS BCACTIVITIES BCDISCRETEHEDRS BCDISCRETEDTAILS BCDISCRETEREPLICATES BCPLANKTNHEDRS BCPLANKTNGENERALS BCPLANKTNFREQS BCPLANKTNDTAILS BCPLANKTNINDIVIDLS Archival Deletes Tables BCMISSIONSDEL BCEVENTSDEL BCCOMMENTSDEL BCACTIVITIESDEL BCDISCRETEHEDRSDEL BCDISCRETEDTAILSDEL BCDISCRETEREPLICTSDEL BCPLANKTNHEDRSDEL BCPLANKTNGENRLSDEL Table Comment Contains information on missions (cruises or Datasets). Contains information on events. Contains extra text information that is too long to fit in the comment fields of the Mission and Event tables. Table identifies data at the Header level as it related to either functional area (plankton, discrete etc). Contains metadata describing each individual DISCRETE sample. Contains DISCRETE sample analysis results and associated information including code table references (eg. Quality, detection limits, etc.) where applicable. Similar to BCDISCRETEDTAILS table, but there may be more than one entry in this table for a given sample and data type. All "same sample" data types are averaged and the averaged value is stored in the BCDISCRETEDTAILS Contains information on individual PLANKTON samples. Contains PLANKTON sample analysis results and associated information including sub-sampling conversion factors. Contains data types such as length, weight, width measurements associated with a PLANKTNGENERALS record. Contains additional plankton measurements not included in the other plankton tables associated with a PLANKTNGENERALS record. Contains individual specific measurements associated with a PLANKTNGENERALS record Contains the deleted records from the BCMISSIONS table in the Archival database tables. Contains the deleted records from the BCEVENTS table in the Archival database tables. Contains the deleted records from the BCCOMMENTS table in the Archival database tables. Contains the deleted records from the BCACTIVITIES table in the Archival database tables. Contains the deleted records from the BCDISCRETEHEDRS table in the Archival database tables. Contains the deleted records from the BCDISCRETEDTAILS table in the Archival database tables. Contains the deleted records from the BCDISCRETEREPLICATES table in the Archival database tables. Contains the deleted records from the BC_PLANKTON_HEADER table in the Archival database tables. Contains the deleted records from the BCPLANKTNGENRLS table in the Archival database tables. 8
9 BCPLANKTNFREQSDEL BCPLANKTNDTAILSDEL BCPLANKTNINDIVDLSDEL Archival Audit Table BCAUDITTRAILS Archival Lookup(Code) Tables BCANALYSES BCCOLLECTIONMETHODS BCDATACENTERS BCDATAPOINTERS BCDATARETRIEVALS BCDATATYPES BCDERIVATIONS BCEDITPROCFLAGS BCERRORCODES BCGEARS BCLIFEHISTORIES BCLOCKEDMISSIONS BCNATNLTAXONCODES BCPRESERVATIONS BCPROCEDURES Contains the deleted records from the BCPLANKTNFREQS table in the Archival database tables. Contains the deleted records from the BC_PLANKTON_DETAIL table in the Archival database tables. Contains the deleted records from the BCPLANKTNINDIVDLS table in the Archival database tables. Tracks all of the updates to any data from any of the Archival database tables. The table will store the table name, column name, old and new data values for the column as well as the user name of the individual who altered the data and the date of the change. Contains brief descriptions of the analytical methods used during sample analysis. Contains information pertaining to the method of plankton sample collection: oblique tow, horizontal tow, vertical tow, unknown. Contains a list the regional Data Centers defining ownership or origin of data and some codes. An application table used to reference functional area that data are part of (See BCLOCKEDMISSIONS) Contains a list of parameters or groupings of like Datas. Only one entry is allowed for each parameter. Associated data type data values are stored and reported in the units specified in this Contains description of each data type in the database. Data in detail tables reference BCDATATYPES to identify the nature of the measurement. Multiple entries for data types within the same parameter will exist in this table whenever the methods of analysis, preservation, sample_handling, storage differ significantly, or the original analytical units differ. N.B.: Units referenced by entries in this table identify the data s analysis units; actual results stored in the database are always in the units referenced by the corresponding entry in BCDATARETRIEVALS. Contains the derived parameter names of to be calculated parameters. An application table that stores the processing flags (and their descriptions) that are to be assigned to the records as the records in the Edit table system are being validated and duplicate checked. The processing flag codes are those that reflect the status of the validation process as the records are being validated and as the records are being duplicate checked. An application table that stores the possible error codes (and error messages) that are to be referenced during the validation processing. Contains information on the equipment used to collect samples or measure properties in situ. Contains information on the life history stage of the PLANKTON taxon associated with the PLANKTNGENERALS record An application table which references missions that have been downloaded but not re- archived or deleted. The table contains the downloaded date, mission, user, and data pointer code associated with the lock. Contains information on the taxa or group of organisms associated with the PLANKTNGENERALS record. Contains information on how a sample is preserved. Contains information on the status of the sample analysis. 9
10 BCQUALCODES BCSAMPLEHANDLINGS BCSEXES BCSTORAGES BCTROPHICDESCRIPTORS BCUNITS BCUSERS BCVOLUMEMETHODS Contains data Quality Codes and descriptions. Contains information on how a sample has been processed after collection (eg filtration, centrifuging etc) prior to analysis. Contains information on the sex of the taxa or group of organisms associated with the PLANKTNGENERALS record. Table contains information on how a sample was stored between collection and analysis. Contains the description of an organisms' position in the food chain. Contains description of units associated with data types and/or parameters. Contains the user name, data center to which they belong and the account type to which they have access (either the Data Manager role or a general read only user role). Contains the description of the method used for the calculation of PLANKTON sample volumes. Table Column Descriptions (BIOCHEM Account) N.B: Shaded fields denotes that these fields are filled in when a record is saved through the Edits/Archive application BCMISSIONS? Mission_seq NUMBER(14) N Primary key generated from the BCMISSIONS_SEQ sequence. data_center_code NUMBER(2) N Foreign Key reference to a data center in the BCDATACENTERS Name VARCHAR2(50) Y Originator s mission descriptor and/or common name(s) for the mission descriptor VARCHAR2(50) N BioChem s standardized mission descriptor (MEDS assigned mission id) leader VARCHAR2(50) Y The person responsible for the mission; a contact person for information concerning the mission details. On a cruise this would be the chief scientist. start_date DATE Y The start date for the mission. DD/MM/YYYY. end_date DATE Y The end date for the mission. DD/MM/YYYY. institute VARCHAR2(50) Y The institute responsible for the mission, cruise or data. platform VARCHAR2(50) Y The name of the platform(s) from which sampling was done, protocol VARCHAR2(50) Y A citation for standard protocols used during the mission. The use of non-standard protocols should be noted with further details provided in the BCCOLLECTOR_COMMENT field. geographic_region VARCHAR2(100) Y A text record of the general geographic region covered by the mission. collector_comment VARCHAR2(2000) Y Comments from the collector that are pertinent to the entire mission. Generally referring to data collection, analysis, publication, etc. data_manager_comment VARCHAR2(2000) Y Comments from the data manager that are pertinent to the entire mission. Generally referring to data management history (processing steps, edits, etc). more_comment CHAR(1) N A flag to indicate that more comments exist in the COMMENT table that relate to this record. (Yes(Y) or No(N)) created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database 10
11 BCEVENTS? event_seq NUMBER(14) N Primary key generated from the BCEVENTS_SEQ sequence. data_center_code NUMBER(2) N Foreign Key reference to a data center in the BCDATACENTERS mission_seq NUMBER(14) N Foreign Key reference to a mission in the BCMISSIONS start_date DATE N Start date for event (UTC). DD/MM/YYYY end_date DATE Y End date for event (UTC). DD/MM/YYYY. start_time NUMBER(4) Y Start time for event (UTC).4 digit integer-- HHMM end_time NUMBER(4) Y End time for event (UTC).4 digit integer-- HHMM utc_offset NUMBER(4,1) Y Time zone offset of event region (decimal hours). min_lat NUMBER(8,5) N Min latitude for event (decimal degrees +ve North). max_lat NUMBER(8,5) Y Max latitude for event (decimal degree +ve North). min_lon NUMBER(9,5) N Min longitude for event (decimal degrees +ve East) max_lon NUMBER(9,5) Y Max longitude for event (decimal degrees +ve East) collector_station_name VARCHAR2(50) Y Descriptive name of event, generally a location name (e.g. stn27, HL2) collector_event_id VARCHAR2(50) N Number or character string assigned to identify the event during data collection. collector_comment VARCHAR2(2000) Y Comments from the collector referring to the event. Example CTD001. data_manager_comment VARCHAR2(2000) Y Comments from the data manager/data centre. Generally referring to data management history (processing steps, edits, etc). more_comment CHAR(1) Y A flag to indicate that more comments exist in the COMMENT table that relate to this record. Y or N (Yes or No) prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. BCCOMMENTS? comment_seq NUMBER(14) N Primary key generated from the BCCOMMENTS_SEQ sequence. data_center_code NUMBER(2) N Foreign Key reference to a data center in the BCDATACENTERS mission_seq NUMBER(14) Y Foreign Key references to a mission in the BCMISSIONS event_seq NUMBER(14) Y Foreign Key references to an event in the BCEVENTS edit_comment VARCHAR2(2000) N Extra comment information that will not fit in either the BCMISSIONS or the BCEVENTS tables' comment columns. These comments further describe and clarify the Mission and/or the Event during a Mission. comment_num NUMBER(10) N The sequential comment number to link segments of multiple comments that refer to a single comment. prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. 11
12 BCACTIVITIES? activity_seq NUMBER(14) N Primary key generated from the BCACTIVITIES_SEQ sequence. event_seq NUMBER(14) N Foreign Key references to an event in the BCEVENTS data_center_code NUMBER(2) N Foreign Key references to a data center in the BCDATACENTERS data_pointer_code VARCHAR2(2) N Foreign Key references to a data pointer code in the BCDATAPOINTERS BCDISCRETEHEDRS? discrete_seq NUMBER(14) N Primary key generated from the BCDISCRETEHEDRS_SEQ sequence. data_center_code NUMBER(2) N Foreign Key references to a data center in the BCDATACENTERS event_seq NUMBER(14) N Foreign Key references to an event in the BCEVENTS activity_seq NUMBER(14) N Foreign Key references to an activity in the BCACTIVITIES gear_seq NUMBER(8) N Foreign Key references to a gear in the BCGEARS start_date DATE N Specific start date of collection (UTC). DD/MM/YYYY. end_date DATE Y Specific end date of collection (UTC). DD/MM/YYYY. start_time NUMBER(4) Y Specific start time of collection (UTC).4 digit integer-- HHMM end_time NUMBER(4) Y Specific end time of collection (UTC).4 digit integer-- HHMM. time_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES start_lat NUMBER(8,5) N Specific start latitude of collection. (decimal degrees +ve North) end_lat NUMBER(8,5) Y Specific end latitude of collection. (decimal degrees +ve North) start_lon NUMBER(9,5) N Specific start longitude of collection. (decimal degrees +ve East) end_lon NUMBER(9,5) Y Specific end longitude of collection. (decimal degrees +ve East) position_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES start_depth NUMBER(7,2) N The start depth(m) during sample collection. end_depth NUMBER(7,2) N The end depth(m) during sample collection. sounding NUMBER(5) Y Sounding or water depth(m) at location during sample collection. collector_deployment_id VARCHAR2(50) Y Collector s identifier for group of samples collected during common gear deployment. collector_sample_id VARCHAR2(50) N Collector s unique identifier for sample, if none provided use Negative numbers. collector VARCHAR2(50) Y The person responsible for the collection of the samle; a contact person for information concerning the sample details. Generally this would be the person who manages the logbooks. responsible_group VARCHAR2(50) Y The COLLECTOR S group or organization. (government department/division, university, etc) collector_comment VARCHAR2(2000) Y Comments from the collector/group referring to the sample collection. data_manager_comment VARCHAR2(2000) Y Comments from the data manager/data centre. Generally referring to data management history (processing steps, edits, etc). shared_data VARCHAR2(50) Y Flag to identify data exchange with MEDS. prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. BCDISCRETEDTAILS Column Name Column Data NULL? 12
13 discrete_detail_seq NUMBER(14) N Primary key generated from the BCDISCRETEDTAILS_SEQ sequence. data_center_code NUMBER(2) N Foreign Key references to a data center in the BCDATACENTERS data_type_seq NUMBER(8) N Foreign Key references a data method in the BCDATATYPES discrete_seq NUMBER(14) N Foreign Key references a discrete header in the BCDISCRETEHEDRS data_value NUMBER(10,5) N Data value. averaged_data CHAR(1) N Denotes if the data value is a calculated value. (I.e. average value of the replicate detail data values for a specified data type from the same sample.) data_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES detection_limit NUMBER(11,5) Y Detection limit of the observed data value during this run of analysis detail_collector VARCHAR2(50) Y The person responsible for the collection of the data value ; a contact person for information concerning the analysis details. collector_sample_id VARCHAR2(50) N Collector s unique identifier for sample. See BCDISCRETEHEDRS prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. BCDISCRETEREPLICATES? discrete_replicate_seq NUMBER(14) N Primary key generated from the BCDISCRETEREPLICATES_SEQ sequence. data_center_code NUMBER(2) N Foreign Key references to a data center in the BCDATACENTERS data_type_seq NUMBER(8) N Foreign Key references a data center in the BCDATATYPES discrete_detail_seq NUMBER(14) N Foreign Key references a discrete detail in the BCDISCRETEDTAILS data_value NUMBER(10,5) N Data value. data_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES detection_limit NUMBER(11,5) Y Detection limit of the observed data value during this run of analysis detail_collector VARCHAR2(50) Y The person responsible for the collection of the data type ; a contact person for information concerning the analysis details. collector_sample_id VARCHAR2(50) N Collector s unique identifier for sample. See BCDISCRETEHEDRS prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. BCPLANKTNHEDRS plankton_seq NUMBER(14) N Primary key generated from the BCPLANKTNHEDRS_SEQ sequence. event_seq NUMBER(14) N Foreign Key references an event in the BCEVENTS activity_seq NUMBER(14) N Foreign Key references an activity in the BCACTIVITIES gear_seq NUMBER(8) N Foreign Key references a gear in the BCGEARS Start_date DATE N Specific start date of collection (UTC). DD/MM/YYYY. End_date DATE Y Specific end date of collection (UTC). DD/MM/YYYY. Start_time NUMBER(4) Y Specific start time of collection (UTC).4 digit integer-- HHMM. 13
14 End_time NUMBER(4) Y Specific end time of collection (UTC).4 digit integer-- HHMM. time_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES Lookup phase_of_daylight VARCHAR2(15) Y Used to identify the state or phase of the day (i.e. day, night, twilight, etc.) Start_lat NUMBER(8,5) N Specific start latitude of collection. End_lat NUMBER(8,5) Y Specific end latitude of collection. Start_lon NUMBER(9,5) N Specific start longitude of collection. End_lon NUMBER(9,5) Y Specific end longitude of collection. position_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES Lookup start_depth NUMBER(7,2) N The start depth(m) during sample collection. end_depth NUMBER(7,2) N The end depth(m) during sample collection. sounding NUMBER(5) Y Sounding or water depth(m) at location during sample collection volume NUMBER(7,3) Y Volume of water filtered through net (cubic meters). volume_method_seq NUMBER(8) N Foreign Key references a volume method in the BCVOLUMEMETHODS Lookup large_plankton_removed CHAR(1) Y Procedure included removal of large organisms ie. Jellyfish prior to plankton sample analysis mesh_size NUMBER(6) Y Mesh size (microns) of plankton sampling gear. collection_method_seq NUMBER(8) N Foreign Key reference to a collection method from the BCCOLLECTIONMETODS collector_deployment_id VARCHAR2(50) Y Collector s identifier for group of samples collected during common gear deployment. collector_sample_id VARCHAR2(50) Y Collector s unique identifier for sample. procedure_seq NUMBER(8) N Foreign Key references a procedure from the BCPROCEDURES preservation_seq NUMBER(8) N Foreign Key references a preservation from the BCPRESERVATIONS storage_seq NUMBER(8) N Foreign Key references a storage from the BCSTORAGES lookup collector VARCHAR2(50) Y The person responsible for the collection of the samle; a contact person for information concerning the sample details. Generally this would be the person who manages the logbooks. collector_comment VARCHAR2(2000) Y Comments from the collector referring to the sample collection. meters_sqd_flag CHAR(1) Y Meters squared flag [Y or N] indicates that this sample should be included in water column integration calculations. data_manager_comment VARCHAR2(2000) Y Comments from the data manager/data centre. Generally referring to data management history (processing steps, edits, etc). responsible_group VARCHAR2(50) Y The COLLECTOR S group or organization. (government department/division, university, etc) shared_data VARCHAR2(50) Y The name of the source for which data may be sent to (i.e. Data may be sent to MEDS). prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. 14
15 BCPLANKTNGENERALS plankton_general_seq NUMBER(14) N Primary key generated from the BCPLANKTNGENERLS_SEQ sequence. plankton_seq NUMBER(14) N Foreign Key to a plankton header in the BCPLANKTNHEDREDITS national_taxonomic_seq NUMBER(14) N Foreign Key to a taxon in the BCNATNTAXONCODES collector_taxonomic_id VARCHAR2(20) Y Reference to originator's taxonomic code. life_history_seq NUMBER(8) N Foreign Key references a life history stage from the BCLIFEHISTORIES trophic_seq NUMBER(8) N Foreign Key references a trophic descriptor from the BCTROPHICDESCRIPTORS min_sieve NUMBER(8,4) Y Retention filter/sieve size (microns). max_sieve NUMBER(8,4) Y Largest filter/sieve used (microns). modifier text Y Non standard taxonomic descriptions such as sp. Or spp or ca.500u, etc split_fraction NUMBER(5,4) Y Fraction of sample analysed (range of ) Sex_seq NUMBER(8) N Foreign Key references a sex from the BCSEXES counts NUMBER(9,3) Y Number of organisms counted. count_pct NUMBER(6,3) Y Percentage of entire sample represented by organisms. wet_weight NUMBER(9,4) Y Wet weight of organisms (grams). dry_weight NUMBER(9,4) Y Dry weight of organisms (grams). bio_volume NUMBER(8,3) Y Volume of organisms (ml). presense CHAR(1) Y Indicates presence or absence of organism(s) (Yes(Y) or No(N)). Generally used to replace legacy non-numeric values such as few, many, etc collector_comment VARCHAR2(2000) Y Comments from the collector referring to the sample analysis. source VARCHAR2(30) N Tracks the name of the individual or source of the analysed data. Critical field when sample has been reanalyzed and both results are to be archived data_manager_comment VARCHAR2(2000) Y Comments from the data manager/data centre. Generally referring to data management history (processing steps, edits, etc). prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. BCPLANKTNFREQS plankton_frequency_seq NUMBER(14) N Primary key generated from the BCPLANKTNFREQS_SEQ sequence. plankton_general_seq NUMBER(14) N Foreign Key references a plankton general in the BCPLANKTNGENERALS bug_seq NUMBER(6) N identifier to track frequency bin. data_type_seq NUMBER(8) N Foreign Key references a data type the BCDATATYPES upper_bin_size NUMBER(6,3) Y Upper size fractional bin size. lower_bin_size NUMBER(6,3) Y Lower size fractional bin size. data_value NUMBER(10,5) N Data value (within upper and lower bin size limits). bug_count NUMBER(6) N Number of individuals in bin. data_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES Lookup detail_collector VARCHAR2(50) Y Name of the collector (individual) for the frequency data. 15
16 prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. BCPLANKTNDTAILS plankton_detail_seq NUMBER(14) N Primary key generated from the BCPLANKTNDTAILS_SEQ sequence. plankton_general_seq NUMBER(14) N Foreign Key references a plankton general in the BCPLANKTNGENERALS data_type_seq NUMBER(8) N Foreign Key references a data type the BCDATATYPES lookup data_value NUMBER(10,5) N Data value. data_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES Lookup detail_collector VARCHAR2(50) Y Name of the collector (individual) for the detail data. prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. BCPLANKTNINDIVIDLS plankton_individual_seq NUMBER(14) N Primary key generated from the BCPLANKTNINDIVDLS_SEQ sequence. plankton_general_seq NUMBER(14) N Foreign Key references a plankton general in the BCPLANKTNGENERALS data_type_seq NUMBER(8) N Foreign Key references a data type the BCDATATYPES lookup bug_seq NUMBER(6) N Identifier to track individual taxon. data_value NUMBER(10,5) N Data value. data_qc_code VARCHAR2(2) N Foreign Key references a quality code in the BCQUALCODES Lookup data_collector VARCHAR2(50) Y Name of the collector (individual) for the individual data. prod_created_date DATE N The date the record was last archived into the production database prod_created_by VARCHAR2(10) Y The data manager account name that was last used to archive the record into the production database created_date DATE Y The date the record was originally created. created_by VARCHAR2(30) Y The name of the person or data manager account that originally created the data record. 16
17 DEL Tables The following DEL or delete tables are exact replicates of the route table with the addition of 2 fields described below. All field entries in these tables are automatically filled in when a dataset is deleted through the Edits/Archive application. BCMISSIONSDEL BCEVENTSDEL BCCOMMENTSDEL BCACTIVITIESDEL BCDISCRETEHEDRSDEL BCDISCRETEDTAILSDEL BCDISCRETEREPLICTSDEL BCPLANKTNHEDRSDEL BCPLANKTNGENRLSDEL BCPLANKTNFREQSDEL BCPLANKTNDTAILSDEL BCPLANKTNINDIVIDLSDEL deleted_date DATE N The date the record was deleted from the archival data deleted_by VARCHAR2(10) N The data manager account name that was used to delete the record from the production database BCAUDITTRAILS audit_seq NUMBER(14) N Primary key generated from the BCAUDITTRAILS_SEQ sequence. audit_date DATE N Date and time of data modification using the Edits/Archival application. table_name VARCHAR2(30) N Table name in which data has been modified using the Edits/Archival application. column_name VARCHAR2(30) N Column name in which data has been modified. sequence_name VARCHAR2(30) N Name of the Primary Key column in a table where data has been modified. sequence_number NUMBER(14) N Record number in which data has been modified. (Typically the value of the primary key column of modified data record). user_name VARCHAR2(30) N The data manager account name that was used to modify the record. old_value VARCHAR2(100) N Old data value. new_value VARCHAR2(100) N New data value. BCANALYSES analysis_seq NUMBER(8) N Primary key generated from the BCANALYSES_SEQ sequence. Name VARCHAR2(30) N Name of the analysis method. Description VARCHAR2(250) Y Description of the analysis method. BCCOLLECTIONMETHODS collection_method_seq NUMBER(8) N Primary key generated from the BCCOLLECTIONMETHODS_SEQ sequence. 17
18 Name VARCHAR2(30) N Name of the collection method or type of PLANKTON tow (i.e. oblique, horizontal, vertical, etc). description VARCHAR2(1000) Y Description of the collection method. BCDATACENTERS data_center_code NUMBER(2) N Code value to represent the organization that is responsible for record archival Name VARCHAR2(50) N Name of the data center. Location VARCHAR2(50) N Geographic location of the data center. Description VARCHAR2(100) Y Description of the data center (if necessary). BCDATAPOINTERS data_pointer_code VARCHAR2(2) N Identifies the general data type: i.e. plankton, discrete, continuous, etc. via the following notation: 'BL' BCBLOBS 'CH' BCCONTINUOUSHEDRS 'DH' BCDISCRETEHEDRS 'EH' BCENVIRONMNTLHEDRS 'PH' BCPROFILEHEDRS 'PL' BCPLANKTNHEDRS. table_name VARCHAR2(30) N Table name that references the activity functional area. Description VARCHAR2(250) Y Description of the data pointer (if necessary). functional_area VARCHAR2(30) N Thirty-character meaningful name that references the functional area that stores data (used to populate a list of values). Active CHAR(1) N Designates if the functional area currently contains data and may be queried (used by the application). BCDATARETRIEVALS data_retrieval_seq NUMBER(8) N Primary key generated from the BCDATARETRIEVALS_SEQ sequence. parameter_name VARCHAR2(20) N Short name for parameter. parameter_description VARCHAR2(100) N Parameter description. unit_seq NUMBER(8) N Foreign Key references a Unit code in the BCUNITS All data for data types associated with this parameter will be archived in these units. Plus, units for data output. places_before NUMBER(2) N Maximum digits before the decimal point for data output. places_after NUMBER(2) N Digits after the decimal point for data output. minimum_value NUMBER(12,5) Y Minimum expected value for the parameter (FPMINM). Validation check during data loading procedure. maximum_value NUMBER(12,5) Y Maximum expected value for the parameter (FPMAXM). ). Validation check during data loading procedure. originally_entered_by VARCHAR2(30) N The name of the person or data manager account that originally entered the parameter. 18
19 BCDATATYPES data_type_seq NUMBER(8) N Primary key generated from the BCDATATYPES_SEQ sequence. data_retrieval_seq NUMBER(8) N Foreign Key references a data retrieval in the BCDATARETRIEVALS analysis_seq NUMBER(8) N Foreign Key references an analysis method in the BCANALYSIS preservation_seq NUMBER(8) N Foreign Key references a preservation method in the BCPRESERVATIONS sample_handling_seq NUMBER(8) N Foreign Key references a sample handling method in the BCSAMPLEHANDLINGS storage_seq NUMBER(8) N Foreign Key references a storage method in the BCSTORAGES unit_seq NUMBER(8) N Foreign Key references a Unit code in the BCUNITS NOTE: these units refer to the units of the original analysis. Description VARCHAR2(100) N Description of data type. conversion_equation VARCHAR2(250) Y A specified formula for the conversion of analysed units to archival/retrieval units for this data type. originally_entered_by VARCHAR2(30) N The name of the person or data manager account that originally entered the data type. Method VARCHAR2(20) N Short name for Data (typically will reference a method of obtaining a data value for a given parameter). Priority NUMBER(2) N BioChem Table Manager assigned value to identify the priority of the Data s based on the same Data Retrieval value (i.e. parameter). p_code CHAR(4) Y MEDS and/or other national/ international standardized exchange code BCDERIVATIONS Restricted to DBA derived_seq NUMBER(8) N Primary key generated from the BCDERIVATIONS_SEQ sequence. parameter_name VARCHAR2(20) N Name of the derived parameter. Description VARCHAR2(250) Y Description of the derived parameter. BCEDITPROCFLAGS Restricted to DBA process_flag VARCHAR2(3) N Value (code) of the processing flag. Name VARCHAR2(50) N Name of the processing flag. Description VARCHAR2(250) Y Description of the processing flag to describe how the records are to be processed based on the assignment of a specified flag. BCERRORCODES Restricted to DBA error_code NUMBER(4) N Code that specifies the validation error in the Edit table system. Description VARCHAR2(80) N Description of the validation error. long_desc VARCHAR2(300) Y Detailed description of the validation error. last_update_by VARCHAR2(30) N The name of the person or data manager account that last updated the record. last_update_date DATE N The date the record was last updated. 19
20 BCGEARS gear_seq NUMBER(8) N Primary key generated from the BCGEARS_SEQ sequence. VARCHAR2(40) N of gear (i.e. Net, Bottle, Pump, etc). Model VARCHAR2(50) Y Model of the specified gear type (i.e. for.type of Bottle - the model may be Nisken, Knudsen, Go-Flo, etc.) used to collect the sample. NOTE: this is not the gear used to analyse the sample. gear_size VARCHAR2(20) Y Size of the specified gear. Description VARCHAR2(2000) Y Description of the specified gear including the manufacturer or any other necessary information. Mission/data centre specific information such as calibration, etc does not belong in this BCLIFEHISTORIES life_history_seq NUMBER(8) N Primary key generated from the BCLIFEHISTORIES_SEQ sequence. Name VARCHAR2(30) N Name of the development stage. Description VARCHAR2(1000) Y Description of the development stage. molt_number VARCHAR2(20) Y Accepted numeric standard to represent the molt stage. BCLOCKEDMISSIONS mission_seq NUMBER(14) Y A mission seq from the BCMISSIONS mission_name VARCHAR2(50) Y BCMISSIONS.name. Descriptor VARCHAR2(50) Y BCMISSIONS.descriptor (Note you are not locking the entire mission just the one associated with this mission_seq) data_pointer_code VARCHAR2(2) Y The functional area of the switchboard that was used to download the mission. downloaded_by VARCHAR2(10) Y Account name of the data manager account that has downloaded the mission. downloaded_date DATE Y The date the mission was downloaded BCNATNLTAXONCODES national_taxonomic_seq NUMBER(14) N Primary key generated from the BCNATNLTAXONCODES_SEQ sequence. Tsn NUMBER(12) N If +ve this value represent an ITIS TSN value. If this value is ve then it represents a BioChem assigned TSN value taxonomic_name VARCHAR2(100) N Name of taxon or group of taxa. best_nodc7 NUMBER(12) N 10 digit taxonomic reference number. Authority VARCHAR2(50) Y Author s name plus year reference to the accepted description of the taxon. Collectors_comment VARCHAR2(2000) Y Comments from the collector referring to the taxon. Generally a reference to the material used to identify the taxon data_managers_comment VARCHAR2(2000) Y Comments from the data manager/data centre. Generally referring to the data collection identifier which first contained this taxon. short_name VARCHAR2(15) Y Short name representing taxonomic name. BCPRESERVATIONS 20
21 preservation_seq NUMBER(8) N Primary key generated from the BCPRESERVATIONS_SEQ sequence. Name VARCHAR2(30) N Name of the preservation method used immediatedly after sample collection Description VARCHAR2(250) Y Description of the preservation method. VARCHAR2(30) Y of preservation. (i.e. frozen, refrigerated, formaldehyde, lugols). BCPROCEDURES procedure_seq NUMBER(8) N Primary key generated from the BCPROCEDURES_SEQ sequence. Name VARCHAR2(30) N Name of procedure or state of analysis for PLANKTON samples. Description VARCHAR2(1000) Y Description of procedure. BCQUALCODES Restricted to DBA Column Name Column Data NULL qc_code VARCHAR2(2) N Quality control code. qc_definition VARCHAR2(100) N Quality control code definition. BCSAMPLEHANDLINGS sample_handling_seq NUMBER(8) N Primary key generated from the BCSAMPLEHANDLINGS_SEQ sequence. Name VARCHAR2(30) N Name of the sample handling method used prior to sample analysis. Description VARCHAR2(250) Y Description of the sample handling method. BCSEXES sex_seq NUMBER(8) N Primary key generated from BCSEXES_SEQ sequence. Name VARCHAR2(30) N Name of sex. Description VARCHAR2(250) Y Description of the sex. BCSTORAGES storage_seq NUMBER(8) N Primary key generated from BCSTORAGES_SEQ sequence. Name VARCHAR2(30) N Name of the storage method used after sample preservation and prior to sample analysis. Description VARCHAR2(250) Y Description of the storage method. 21
22 BCTROPHICDESCRIPTORS trophic_seq NUMBER(8) N Primary key generated from BCTROPHICDESCRIPTORS_SEQ sequence. Name VARCHAR2(30) N Name of the trophic level. Description VARCHAR2(1000) Y Description of the trophic level. BCUNITS unit_seq NUMBER(8) N Primary key generated from BCUNITS_SEQ sequence. Name VARCHAR2(20) N Name for the unit of measure. Description VARCHAR2(100) Y Description of the unit of measurement. BCUSERS Restricted to DBA Username VARCHAR2(30) N User account name assigend by DBA, table Primary Key. account_type VARCHAR2(20) N The type of account that is assigned to a user. The account types are Data Manager (a user who has Select, Insert, Update, and Delete access privileges on the Bio-Chem database) and Query User (a user who has Select access privilege on the Bio-Chem database). responsible_group VARCHAR2(50) N The User s group or organization. (government department/division, university, etc) BCVOLUMEMETHODS volume_method_seq NUMBER(8) N Primary key generated from BCVOLUMEMETHODS_SEQ sequence. name VARCHAR2(30) N Name of the volume method. This method will indicate how the volume of water filtered to collect the PLANKTON sample was calculated description VARCHAR2(1000) Y Description of the method. 22
23 Sequences (BIOCHEM Account) These sequences reside in the BIOCHEM Oracle account. The Data Manager accounts have access to these sequences via grants and reference them via synonyms created in the individual Data Manager accounts. For further information please see the BCEDITS_data_dictionary_v3.2 document. Sequence Name BCMISSIONS_SEQ BCEVENTS_SEQ BCCOMMENTS_SEQ BCACTIVITIES_SEQ BCDISCRETEHEDRS_SEQ BCDISCRETEDTAILS_SEQ BCDISCRETEREPLICATES_SEQ BCPLANKTNHEDRS_SEQ BCPLANKTNGENERLS_SEQ BCPLANKTNFREQS_SEQ BCPLANKTNDTAILS_SEQ BCPLANKTNINDIVDLS_SEQ BCAUDITTRAILS_SEQ BCANALYSES_SEQ BCCOLLECTIONMETHODS_SEQ BCDATARETRIEVALS_SEQ BCDATATYPES_SEQ BCDERIVATIONS_SEQ BCGEARS_SEQ BCLIFEHISTORIES_SEQ BCNATNLTAXONCODES_SEQ BCPRESERVATIONS_SEQ BCPROCEDURES_SEQ BCSAMPLEHANDLINGS_SEQ BCSEXES_SEQ BCSTORAGES_SEQ BCTROPHICDESCRIPTORS_SEQ BCUNITS_SEQ BCVOLUMEMETHODS_SEQ Primary Key and Foreign Key Constraints (BIOCHEM Account) Table Name Constraint Name Constr. Constrained Column(s) BCMISSIONS BCMISSIONS_PK Primary MISSION_SEQ Primary Key That Foreign Key References DATACNTR_MISSION_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCEVENTS BCEVENTS_PK Primary EVENT_SEQ DATACNTR_EVENT_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK MISSION_EVENT_FK Reference MISSION_SEQ BCMISSIONS_PK BCCOMMENTS BCCOMMENTS_PK Primary COMMENT_SEQ DATACNTR_COMMNTS_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK 23
24 EVENTS_COMMNTS_FK Reference EVENT_SEQ BCEVENTS_PK MISSION_CMMNTS_FK Reference MISSION_SEQ BCMISSIONS_PK BCACTIVITIES BCACTIVITIES_PK Primary ACTIVITY_SEQ DATACNTR_ACTVTY_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK DATAPNTR_ACTVTY_FK Reference DATA_POINTER_CODE BCDATAPOINTERS_PK EVENTS_ACTVTY_FK Reference EVENT_SEQ BCEVENTS_PK BCDISCRETEHEDRS BCDISCRETEHEDRS_PK Primary DISCRETE_SEQ DATACNTR_DISHDR_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK ACTIVTY_DISHDR_FK Reference ACTIVITY_SEQ, EVENT_SEQ BCACTIVITIES_PK, BCEVENTS_PK GEARS_DISHDR_FK Reference GEAR_SEQ BCGEARS_PK QUALCOD_DISHDR1_FK Reference TIME_QC_CODE BCQUALCODES_PK QUALCOD_DISHDR_FK Reference POSITION_QC_CODE BCQUALCODES_PK BCDISCRETEDTAILS BCDISCRETEDTAILS_PK Primary DISCRETE_DETAIL_SEQ DATACNTR_DISDTLS_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK DATATYP_DISDTLS_FK Reference DATA_TYPE_SEQ BCDATATYPES_PK DISHDR_DISDTL_FK Reference DISCRETE_SEQ BCDISCRETEHEDRS_PK QUALCOD_DISDTLS_FK Reference DATA_QC_CODE BCQUALCODES_PK BCDISCRETEREPLICATES BCDISCRETEREPLICATES_PK Primary DISCRETE_REPLICATE_SEQ DATACNTR_DISREPL_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK DATATYP_DISREPL_FK Reference DATA_TYPE_SEQ BCDATATYPES_PK DISDTL_DISREPL_FK Reference DISCRETE_DETAIL_SEQ BCDISCRETEDTAILS_PK QUALCOD_DISREPL_FK Reference DATA_QC_CODE BCQUALCODES_PK BCPLANKTNHEDRS BCPLANKTNHEDRS_PK Primary PLANKTON_SEQ ACTIVTY_PLNTNHDR_FK Reference ACTIVITY_SEQ, EVENT_SEQ BCACTIVITIES_PK, BCEVENTS_PK COLMETH_PLNKHEDR_FK Reference COLLECTION_METHOD_SEQ BCCOLLECTIONMETHODS_PK DATACNTR_PLNKHDR_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK GEARS_PLNKHDR_FK Reference GEAR_SEQ BCGEARS_PK PRESERV_PLNKHDR_FK Reference PRESERVATION_SEQ BCPRESERVATIONS_PK PROCDRS_PLNKHDR_FK Reference PROCEDURE_SEQ BCPROCEDURES_PK QUALCOD_PLNKHDR1_FK Reference POSITION_QC_CODE BCQUALCODES_PK QUALCOD_PLNKHDR_FK Reference TIME_QC_CODE BCQUALCODES_PK STORAGE_PLNKHDR_FK Reference STORAGE_SEQ BCSTORAGES_PK BCPLANKTNGENERALS BCPLANKTNGENERALS_PK Primary PLANKTON_GENERAL_SEQ DATACNTR_PLNKGEN_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK LFHIST_PLNKGEN_FK Reference LIFE_HISTORY_SEQ BCLIFEHISTORIES_PK NTTXCOD_PLNKGEN_FK Reference NATIONAL_TAXONOMIC_SEQ BCNATNLTAXONCODES_PK PLNKHDR_PLNKGEN_FK Reference PLANKTON_SEQ BCPLANKTNHEDRS_PK SEXES_PLNKGEN_FK Reference SEX_SEQ BCSEXES_PK BCPLANKTNFREQS BCPLANKTNFREQS_PK Primary PLANKTON_FREQUENCY_SEQ DATACNTR_PLNKFREQ_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK DATATYP_PLNKFRQ_FK Reference DATA_TYPE_SEQ BCDATATYPES_PK PLNKGEN_PLNKFRQ_FK Reference PLANKTON_GENERAL_SEQ BCPLANKTNGENERALS_PK QUALCOD_PLNKFRQ_FK Reference DATA_QC_CODE BCQUALCODES_PK BCPLANKTNDTAILS BCPLANKTNDTAILS_PK Primary PLANKTON_DETAIL_SEQ DATACNTR_PLNKDTLS_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK DATATYP_PLNKDTL_FK Reference DATA_TYPE_SEQ BCDATATYPES_PK PLNKGEN_PLNKDTL_FK Reference PLANKTON_GENERAL_SEQ BCPLANKTNGENERALS_PK QUALCOD_PLNKDTL_FK Reference DATA_QC_CODE BCQUALCODES_PK 24
25 BCPLANKTNINDIVIDLS BCPLANKTNINDIVIDLS_PK Primary PLANKTON_INDIVIDUAL_SEQ DATACNTR_PLNKIND_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK DATATYP_PLNKIND_FK Reference DATA_TYPE_SEQ BCDATATYPES_PK PLNKGEN_PLNKIND_FK Reference PLANKTON_GENERAL_SEQ BCPLANKTNGENERALS_PK QUALCOD_PLNKIND_FK Reference DATA_QC_CODE BCQUALCODES_PK BCAUDITTRAILS BCAUDITTRAILS_PK Primary AUDIT_SEQ DATACNTR_AUDTRL_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCMISSIONSDEL BCMISSIONSDEL_PK Primary MISSION_SEQ BCEVENTSDEL BCEVENTSDEL_PK Primary EVENT_SEQ BCCOMMENTSDEL BCCOMMENTSDEL_PK Primary COMMENT_SEQ BCACTIVITIESDEL BCACTIVITIESDEL_PK Primary ACTIVITY_SEQ BCDISCRETEHEDRSDEL BCDISCRETEHEDRSDEL_PK Primary DISCRETE_SEQ BCDISCRETEDTAILSDEL BCDISCRETEDTAILSDEL_PK Primary DISCRETE_DETAIL_SEQ BCDISCRETEREPLICTSDEL BCDISCRETEREPLICTSDEL_PK Primary DISCRETE_REPLICATE_SEQ BCPLANKTNHEDRSDEL BCPLANKTNHEDRSDEL_PK Primary PLANKTON_SEQ BCPLANKTNGENRLSDEL BCPLANKTNGENRLSDEL_PK Primary PLANKTON_GENERAL_SEQ BCPLANKTNFREQSDEL BCPLANKTNFREQSDEL_PK Primary PLANKTON_FREQUENCY_SEQ BCPLANKTNDTAILSDEL BCPLANKTNDTAILSDEL_PK Primary PLANKTON_DETAIL_SEQ BCPLANKTNINDIVDLSDEL BCPLANKTNINDIVDLSDEL_PK Primary PLANKTON_INDIVIDUAL BCANALYSES BCANALYSES_PK Primary ANALTSIS_SEQ DATACNTR_ANLYS_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCCOLLECTIONMETHODS BCCOLLECTIONMETHODS_PK Primary COLLECTION_METHOD_SEQ DATACNTR_COLMETH_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCDATACENTERS BCDATACENTERS_PK Primary DATA_CENTER_CODE BCDATAPOINTERS BCDATAPOINTERS_PK Primary DATACNTR_DATAPNTR_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCDATARETRIEVALS BCDATARETRIEVALS_PK Primary DATACNTR_DATARTRVLS_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK UNITS_DATARTVL_FK Reference BCUNITS_PK BCDATATYPES BCDATATYPES_PK Primary ANL_DATATYPS_FK Reference ANALYSIS_SEQ BCANALYSES_PK DATACNTR_DATATYP_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK DATARTVL_DATATYP_FK Reference DATA_RETRIEVAL_SEQ BCDATARETRIEVALS_PK PRESERV_DATATYP_FK Reference PRESERVATION_SEQ BCPRESERVATIONS_PK SMPLHND_DATATYP_FK Reference SAMPLE_HANDLING_SEQ BCSAMPLEHANDLINGS_PK STORAGE_DATATYP_FK Reference STORAGE_SEQ BCSTORAGES_PK UNITS_DATATYP_FK Reference UNIT_SEQ BCUNITS_PK BCDERIVATIONS BCDERIVATIONS_PK Primary DERIVATION_SEQ DATACNTR_DERIVTN_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCEDITPROCFLAGS BCEDITPROCFLAGS_PK Primary PROCESS_FLAG BCERRORCODES BCERRORCODES_PK Primary ERROR_CODE BCGEARS BCGEARS_PK Primary GEAR_SEQ DATACNTR_GEARS_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCLIFEHISTORIES BCLIFEHISTORIES_PK Primary LIFE_HISTORY_SEQ DATACNTR_LFEHIST_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCNATNLTAXONCODES BCNATNLTAXONCODES_PK Primary NATIONAL_TAXONOMIC_SEQ DATACNTR_NTNLTXCD_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCPRESERVATIONS BCPRESERVATIONS_PK Primary DATACNTR_PRESERV_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK 25
26 BCPROCEDURES BCPROCEDURES_PK Primary DATACNTR_PROCDR_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCQUALCODES BCQUALCODES_PK Primary DATACNTR_QUALCOD_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCSAMPLEHANDLINGS BCSAMPLEHANDLINGS_PK Primary DATACNTR_SMPLHAND_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCSEXES BCSEXES_PK Primary SEX_SEQ DATACNTR_SMPLHAND_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCSTORAGES BCSTORAGES_PK Primary STORAGE_SEQ DATACNTR_STORGE_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCTROPHICDESCRIPTORS BCTROPHICDESCRIPTORS_PK Primary TROPHIC_SEQ DATACNTR_TRPHDES_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCUNITS BCUNITS_PK Primary UNIT_SEQ DATACNTR_UNITS_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCUSERS BCUSERS_PK Primary USERNAME DATACNTR_USERS_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK BCVOLUMEMETHODS BCVOLUMEMETHODS_PK Primary VOLUME_METHOD_SEQ DATACNTR_VOLMETH_FK Reference DATA_CENTER_CODE BCDATACENTERS_PK View Definitions (BIOCHEM Account) No views currently exist in the BIOCHEM Oracle Account. Synonyms (BIOCHEM Account) No synonyms currently exist in the BIOCHEM Oracle Account. Stored Program Units (BIOCHEM account) The table below lists the database stored packages, procedures, and functions that reside in the BIOCHEM archival account. The table lists the name of the program unit, the type, and a description of what it does. Program Unit Name Program Arguments Description Unit ITEM_VALIDATION Package This package contains functions used to validate all the fields in the data manager EDIT tables that are not a code (Lookup) table field or that represent a foreign key field. Lookup Table Data The following table outlines the SQL*Loader file, and corresponding data file (CSV file) used to populate the various Code tables required to assist in maintaining the data integrity of the system. For further information on populating these Oracle tables please see the document, BCARCHIVE_installation_guide_v4.0. Table Name SQL*Loader Control File Name CSV File Name BCANALYSES load_bcanalyses.ctl bcanalyses.csv BCCOLLECTIONMETHODS load_bccollectionmethods.ctl bccollectionmethods.csv BCDATACENTERS load_bcdatacenters.ctl bcdatacenters.csv BCDATAPOINTERS load_bcdatapointers.ctl bcdatapointers.csv BCDATARETRIEVALS load_bcdataretrievals.ctl bcdataretrievals.csv BCDATATYPES load_bcdatatypes.ctl bcdatatypes.csv BCDERIVATIONS load_bcderivations.ctl bcderivations.csv 26
27 BCEDITPROCFLAGS load_bceditprocflags.ctl bceditprocflags.csv BCERRORCODES load_bcerrorcodes.ctl bcerrorcodes.csv BCGEARS load_bcgears.ctl bcgears.csv BCPRESERVATIONS load_bcpreservations.ctl bcpreservations.csv BCPROCEDURES load_bcprocedures.ctl bcprocedures.csv BCQUALCODES load_bcqualcodes.ctl bcqualcodes.csv BCSAMPLEHANDLINGS load_bcsamplehandlings.ctl bcsamplehandlings.csv BCSTORAGES load_bcstorages.ctl bcstorages.csv BCUNITS load_bcunits.ctl bcunits.csv BCUSERS load_bcusers.ctl bcusers.csv 27
28 APPENDIX A (Table Name Translation/Clarification) BIOCHEM Account and Data Manager Account Table Name Translation/Clarification Current Table Name BCACTIVITIES BCACTIVITIESDEL BCACTIVITYEDITS BCANALYSES BCAUDITTRAILS BCCOLLECTIONMETHODS BCCOMMENTS BCCOMMENTSDEL BCCOMMENTEDITS BCDATACENTERS BCDATAPOINTERS BCDATARETRIEVALS BCDATATYPES BCDISCRETEDTAILEDITS BCDISCRETEDTAILAUDITS BCDISREPLICATEDITS BCDISCRETEDATAEDITS BCDISCRETEDTAILS BCDISCRETEDTAILSDEL BCDISCRETEHEDRS BCDISCRETEHEDRSDEL BCDISCRETEHEDREDITS BCDISCRETEREPLICTSDEL BCDISCRETEREPLICATES BCDISCRETESTATNEDITS BCEDITPROCFLAGS BCERRORS BCERRORCODES BCEVENTS BCEVENTSDEL BCEVENTEDITS BCGEARS BCMEDSEDITS BCMISSIONS BCMISSIONSDEL BCMISSIONEDITS BCPRESERVATIONS BCPROCEDURES BCQUALCODES BCSAMPLEHANDLINGS Current Table Name Translation/Clarification BC_ACTIVITY BC_ACTIVITY_DELETED BC_ACTIVITY_EDIT BC_ANALYSIS BC_AUDIT_TRAIL BC_COLLECTION_METHOD BC_COMMENT BC_COMMENT_DELETED BC_COMMENT_EDIT BC_DATA_CENTER BC_DATA_POINTER BC_DATA_RETRIEVAL BC_DATA_TYPE BC_DIS_DETAIL_EDIT BC_DIS_DETAIL_RECORD_DELETED BC_DIS_REPLICATE_DETAIL_EDIT BC_DISCRETE_DATA_EDIT BC_DISCRETE_DETAIL BC_DISCRETE_DETAIL_DELETED BC_DISCRETE_HEADER BC_DISCRETE_HEADER_DELETED BC_DISCRETE_HEADER_EDIT BC_DISCRETE_REPLICATE_DELETED BC_DISCRETE_REPLICATE_DETAIL BC_DISCRETE_STATION_EDIT BC_EDIT_PROCESS_FLAG BC_ERROR BC_ERROR_CODE BC_EVENT BC_EVENT_DELETED BC_EVENT_EDIT BC_GEAR BC_MEDS_EDIT BC_MISSION BC_MISSION_DELETED BC_MISSION_EDIT BC_PRESERVATION BC_PROCEDURE BC_QC BC_SAMPLE_HANDLING 28
29 BCSTATNDATAERRORS BCSTORAGES BCUNITS BCUSERS BCBATCHES BCDERIVATIONS BC_STATION_DATA_ERRORS BC_STORAGE BC_UNIT BC_USERS BCBATCH BCDERIVATIONS 29
30 Appendix B (BIOCHEM Document Catalogue) The following outlines reference documentation created regarding the BIOCHEM database and BIOCHEM Database Edit Application System: DOCUMENT NAME INTENDED DESCRIPTION AUDIENCE BCARCHIVE_data_dictionary_v4.0 Informatics Analysts Information on all Oracle objects developed to date for the system. Including objects not yet implemented and information on Stored Procedures. BCEDITS_data_dictionary_v4.0 Users Information on all Data Manager Oracle database objects implemented in Version 4.0. Recommended for all Data Managers. BCEDITS_installation_guide_v4.0 Users Instructions to create the BIOCHEM Data Manager schema. BCARCHIVE_installation_guide_v4.0 Users Super user document containing instructions to create the BIOCHEM Archival schema and granting access to the Data Manager account(s). BCQUERY_data_dictionary_v3.0 Informatics Analysts Technical information on all database objects related to the BCQRY query database. BCQUERY_installation_guide_v3.0 Informatics Analysts Instructions to create the BCQRY schema. BIOCHEM_User_guide_v4.0 Users Descriptions of all functional aspects of Version 4.0. BCQUERY_User_guide_v3.0 Users Descriptions of all functional aspects of the web version of the application. 30
DBMS Questions. 3.) For which two constraints are indexes created when the constraint is added?
DBMS Questions 1.) Which type of file is part of the Oracle database? A.) B.) C.) D.) Control file Password file Parameter files Archived log files 2.) Which statements are use to UNLOCK the user? A.)
Physical Design. Meeting the needs of the users is the gold standard against which we measure our success in creating a database.
Physical Design Physical Database Design (Defined): Process of producing a description of the implementation of the database on secondary storage; it describes the base relations, file organizations, and
Conventional Files versus the Database. Files versus Database. Pros and Cons of Conventional Files. Pros and Cons of Databases. Fields (continued)
Conventional Files versus the Database Files versus Database File a collection of similar records. Files are unrelated to each other except in the code of an application program. Data storage is built
3.GETTING STARTED WITH ORACLE8i
Oracle For Beginners Page : 1 3.GETTING STARTED WITH ORACLE8i Creating a table Datatypes Displaying table definition using DESCRIBE Inserting rows into a table Selecting rows from a table Editing SQL buffer
Once the schema has been designed, it can be implemented in the RDBMS.
2. Creating a database Designing the database schema... 1 Representing Classes, Attributes and Objects... 2 Data types... 5 Additional constraints... 6 Choosing the right fields... 7 Implementing a table
www.gr8ambitionz.com
Data Base Management Systems (DBMS) Study Material (Objective Type questions with Answers) Shared by Akhil Arora Powered by www. your A to Z competitive exam guide Database Objective type questions Q.1
Table Backup and Recovery using SQL*Plus
VIII Konferencja PLOUG Koœcielisko PaŸdziernik 2002 Table Backup and Recovery using SQL*Plus Peter G Robson British Geological Survey Abstract A technique has been developed whereby a complete auditing
SQL Server An Overview
SQL Server An Overview SQL Server Microsoft SQL Server is designed to work effectively in a number of environments: As a two-tier or multi-tier client/server database system As a desktop database system
Oracle Database 10g Express
Oracle Database 10g Express This tutorial prepares the Oracle Database 10g Express Edition Developer to perform common development and administrative tasks of Oracle Database 10g Express Edition. Objectives
Field Audit Trail Implementation Guide
Field Audit Trail Implementation Guide Salesforce, Spring 16 @salesforcedocs Last updated: January 19, 2016 Copyright 2000 2016 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark
Programming with SQL
Unit 43: Programming with SQL Learning Outcomes A candidate following a programme of learning leading to this unit will be able to: Create queries to retrieve information from relational databases using
Using SQL Server Management Studio
Using SQL Server Management Studio Microsoft SQL Server Management Studio 2005 is a graphical tool for database designer or programmer. With SQL Server Management Studio 2005 you can: Create databases
How To Create A Table In Sql 2.5.2.2 (Ahem)
Database Systems Unit 5 Database Implementation: SQL Data Definition Language Learning Goals In this unit you will learn how to transfer a logical data model into a physical database, how to extend or
Database Design Standards. U.S. Small Business Administration Office of the Chief Information Officer Office of Information Systems Support
Database Design Standards U.S. Small Business Administration Office of the Chief Information Officer Office of Information Systems Support TABLE OF CONTENTS CHAPTER PAGE NO 1. Standards and Conventions
Oracle Database Development Standards For DNR Staff and Contractors. Table of Contents
Oracle Database Development Standards For DNR Staff and Contractors Table of Contents INTRODUCTION...2 DATABASE ORGANIZATION...2 DATABASE PROCEDURES...3 Development...3 Testing...3 Production Release...4
Chapter 6: Physical Database Design and Performance. Database Development Process. Physical Design Process. Physical Database Design
Chapter 6: Physical Database Design and Performance Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Robert C. Nickerson ISYS 464 Spring 2003 Topic 23 Database
IT2305 Database Systems I (Compulsory)
Database Systems I (Compulsory) INTRODUCTION This is one of the 4 modules designed for Semester 2 of Bachelor of Information Technology Degree program. CREDITS: 04 LEARNING OUTCOMES On completion of this
2874CD1EssentialSQL.qxd 6/25/01 3:06 PM Page 1 Essential SQL Copyright 2001 SYBEX, Inc., Alameda, CA www.sybex.com
Essential SQL 2 Essential SQL This bonus chapter is provided with Mastering Delphi 6. It is a basic introduction to SQL to accompany Chapter 14, Client/Server Programming. RDBMS packages are generally
In This Lecture. SQL Data Definition SQL SQL. Notes. Non-Procedural Programming. Database Systems Lecture 5 Natasha Alechina
This Lecture Database Systems Lecture 5 Natasha Alechina The language, the relational model, and E/R diagrams CREATE TABLE Columns Primary Keys Foreign Keys For more information Connolly and Begg chapter
Guide to the Superbase. ODBC Driver. By Superbase Developers plc
Guide to the Superbase ODBC Driver By Superbase Developers plc This manual was produced using Doc-To-Help, by WexTech Systems, Inc. WexTech Systems, Inc. 310 Madison Avenue, Suite 905 New York, NY 10017
Best Practices for Data Dictionary Definitions and Usage Version 1.1 2006-11-14
Best Practices for Dictionary Definitions and Usage Version 1.1 2006-11-14 1 1.0 Introduction This document introduces readers to the importance of a data dictionary as a critical part of a metadata record
FIELD NAME NULL? DATA TYPE CRUISE PK NOT NULL VARCHAR2(6) STRATUM NOT NULL VARCHAR2(5) TOW NOT NULL VARCHAR2(3) STATION PK NOT NULL VARCHAR2(4)
FSCS_SVSTA Survey Station Data This table holds a single record for each station conducted on an Ecosystems Surveys Branch cruise. The data in this table represents the position of the tow, meteorological
A basic create statement for a simple student table would look like the following.
Creating Tables A basic create statement for a simple student table would look like the following. create table Student (SID varchar(10), FirstName varchar(30), LastName varchar(30), EmailAddress varchar(30));
Extracting META information from Interbase/Firebird SQL (INFORMATION_SCHEMA)
13 November 2007 22:30 Extracting META information from Interbase/Firebird SQL (INFORMATION_SCHEMA) By: http://www.alberton.info/firebird_sql_meta_info.html The SQL 2003 Standard introduced a new schema
Introduction This document s purpose is to define Microsoft SQL server database design standards.
Introduction This document s purpose is to define Microsoft SQL server database design standards. The database being developed or changed should be depicted in an ERD (Entity Relationship Diagram). The
Downloading & Using Data from the STORET Warehouse: An Exercise
Downloading & Using Data from the STORET Warehouse: An Exercise August 2012 This exercise addresses querying or searching for specific water resource data, and the respective methods used in collecting
Real Time Monitor. A Real-Time Windows Operator Interface. DDE Compliant. (for remote data display)
Real Time Monitor A Real-Time Windows Operator Interface DDE Compliant (for remote data display) TABLE OF CONTENTS 1. INTRODUCTION...1 1.1 INSTALLATION...2 1.2 FIRST START UP - DDE CONFIGURE...2 1.3 AUTO-STARTUP...2
Retrieving Data Using the SQL SELECT Statement. Copyright 2006, Oracle. All rights reserved.
Retrieving Data Using the SQL SELECT Statement Objectives After completing this lesson, you should be able to do the following: List the capabilities of SQL SELECT statements Execute a basic SELECT statement
Carl R. Haske, Ph.D., STATPROBE, Inc., Ann Arbor, MI
Using SAS/AF for Managing Clinical Data Carl R. Haske, Ph.D., STATPROBE, Inc., Ann Arbor, MI ABSTRACT Using SAS/AF as a software development platform permits rapid applications development. SAS supplies
Oracle Database 12c: Introduction to SQL Ed 1.1
Oracle University Contact Us: 1.800.529.0165 Oracle Database 12c: Introduction to SQL Ed 1.1 Duration: 5 Days What you will learn This Oracle Database: Introduction to SQL training helps you write subqueries,
Wave Analytics Data Integration
Wave Analytics Data Integration Salesforce, Spring 16 @salesforcedocs Last updated: April 28, 2016 Copyright 2000 2016 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of
Oracle Supply Chain Hub Technical Reference Manual
Oracle Supply Chain Hub Technical Reference Manual RELEASE 6.2 April 2001 A88857 01 Oracle Supply Chain Hub Technical Reference Manual Release 6.2 A88857 01. Copyright 2001. Oracle Corporation. All rights
IT2304: Database Systems 1 (DBS 1)
: Database Systems 1 (DBS 1) (Compulsory) 1. OUTLINE OF SYLLABUS Topic Minimum number of hours Introduction to DBMS 07 Relational Data Model 03 Data manipulation using Relational Algebra 06 Data manipulation
Choosing a Data Model for Your Database
In This Chapter This chapter describes several issues that a database administrator (DBA) must understand to effectively plan for a database. It discusses the following topics: Choosing a data model for
HP Quality Center. Upgrade Preparation Guide
HP Quality Center Upgrade Preparation Guide Document Release Date: November 2008 Software Release Date: November 2008 Legal Notices Warranty The only warranties for HP products and services are set forth
Governance, Risk, and Compliance Controls Suite. Preventive Controls Governor Audit Rules User s Guide. Software Version 7.2.2.3
Governance, Risk, and Compliance Controls Suite Preventive Controls Governor Audit Rules User s Guide Software Version 7.2.2.3 Preventive Conrols Governor: Audit Rules User s Guide Part No. AR002-7223A
Structured Query Language (SQL)
Objectives of SQL Structured Query Language (SQL) o Ideally, database language should allow user to: create the database and relation structures; perform insertion, modification, deletion of data from
Performance Tuning for the Teradata Database
Performance Tuning for the Teradata Database Matthew W Froemsdorf Teradata Partner Engineering and Technical Consulting - i - Document Changes Rev. Date Section Comment 1.0 2010-10-26 All Initial document
news from Tom Bacon about Monday's lecture
ECRIC news from Tom Bacon about Monday's lecture I won't be at the lecture on Monday due to the work swamp. The plan is still to try and get into the data centre in two weeks time and do the next migration,
EECS 647: Introduction to Database Systems
EECS 647: Introduction to Database Systems Instructor: Luke Huan Spring 2013 Administrative Take home background survey is due this coming Friday The grader of this course is Ms. Xiaoli Li and her email
Database Query 1: SQL Basics
Database Query 1: SQL Basics CIS 3730 Designing and Managing Data J.G. Zheng Fall 2010 1 Overview Using Structured Query Language (SQL) to get the data you want from relational databases Learning basic
ETL PROCESS IN DATA WAREHOUSE
ETL PROCESS IN DATA WAREHOUSE OUTLINE ETL : Extraction, Transformation, Loading Capture/Extract Scrub or data cleansing Transform Load and Index ETL OVERVIEW Extraction Transformation Loading ETL ETL is
The Relational Model. Why Study the Relational Model?
The Relational Model Chapter 3 Instructor: Vladimir Zadorozhny [email protected] Information Science Program School of Information Sciences, University of Pittsburgh 1 Why Study the Relational Model?
4. The Third Stage In Designing A Database Is When We Analyze Our Tables More Closely And Create A Between Tables
1. What Are The Different Views To Display A Table A) Datasheet View B) Design View C) Pivote Table & Pivot Chart View D) All Of Above 2. Which Of The Following Creates A Drop Down List Of Values To Choose
How To Read The Ooracle Call Center Technology Technical Reference Manual
Oracle Call Center Technology Technical Reference Manual RELEASE 11i April 2000 Oracle Call Center Technology Technical Reference Manual Release 11i To order this book, ask for Part No. A83703 01 Copyright
MHRA GMP Data Integrity Definitions and Guidance for Industry January 2015
MHRA GMP Data Integrity Definitions and Guidance for Industry Introduction: Data integrity is fundamental in a pharmaceutical quality system which ensures that medicines are of the required quality. This
Specific API Usage Limitations... 6 Daily Limitation... 6 Concurrency Limitation... 6. API Description... 7 Site Data API... 7
Last update: July 2015 SolarEdge API SolarEdge API Contents Last update: July 2015... 1 SolarEdge API... 2 Contents... 2 General... 3 Purpose and scope... 3 Acronyms and abbreviations... 3 Introduction...
Introduction to SQL (3.1-3.4)
CSL 451 Introduction to Database Systems Introduction to SQL (3.1-3.4) Department of Computer Science and Engineering Indian Institute of Technology Ropar Narayanan (CK) Chatapuram Krishnan! Summary Parts
Access Queries (Office 2003)
Access Queries (Office 2003) Technical Support Services Office of Information Technology, West Virginia University OIT Help Desk 293-4444 x 1 oit.wvu.edu/support/training/classmat/db/ Instructor: Kathy
Database Administration with MySQL
Database Administration with MySQL Suitable For: Database administrators and system administrators who need to manage MySQL based services. Prerequisites: Practical knowledge of SQL Some knowledge of relational
Data Dictionary and Normalization
Data Dictionary and Normalization Priya Janakiraman About Technowave, Inc. Technowave is a strategic and technical consulting group focused on bringing processes and technology into line with organizational
SQL. Short introduction
SQL Short introduction 1 Overview SQL, which stands for Structured Query Language, is used to communicate with a database. Through SQL one can create, manipulate, query and delete tables and contents.
SQL - QUICK GUIDE. Allows users to access data in relational database management systems.
http://www.tutorialspoint.com/sql/sql-quick-guide.htm SQL - QUICK GUIDE Copyright tutorialspoint.com What is SQL? SQL is Structured Query Language, which is a computer language for storing, manipulating
Select the Crow s Foot entity relationship diagram (ERD) option. Create the entities and define their components.
Α DESIGNING DATABASES WITH VISIO PROFESSIONAL: A TUTORIAL Microsoft Visio Professional is a powerful database design and modeling tool. The Visio software has so many features that we can t possibly demonstrate
Oracle Database Links Part 2 - Distributed Transactions Written and presented by Joel Goodman October 15th 2009
Oracle Database Links Part 2 - Distributed Transactions Written and presented by Joel Goodman October 15th 2009 About Me Email: [email protected] Blog: dbatrain.wordpress.com Application Development
New Mexico State University. AiM 8.X Basic AiM
New Mexico State University AiM 8.X Basic AiM January 22, 2015 Confidential Business Information This documentation is proprietary information of New Mexico State University (NMSU) and is not to be copied,
Question 1. Relational Data Model [17 marks] Question 2. SQL and Relational Algebra [31 marks]
EXAMINATIONS 2005 MID-YEAR COMP 302 Database Systems Time allowed: Instructions: 3 Hours Answer all questions. Make sure that your answers are clear and to the point. Write your answers in the spaces provided.
Technical. Overview. ~ a ~ irods version 4.x
Technical Overview ~ a ~ irods version 4.x The integrated Ru e-oriented DATA System irods is open-source, data management software that lets users: access, manage, and share data across any type or number
Objectives. Oracle SQL and SQL*PLus. Database Objects. What is a Sequence?
Oracle SQL and SQL*PLus Lesson 12: Other Database Objects Objectives After completing this lesson, you should be able to do the following: Describe some database objects and their uses Create, maintain,
Oracle Database: SQL and PL/SQL Fundamentals NEW
Oracle University Contact Us: 001-855-844-3881 & 001-800-514-06-97 Oracle Database: SQL and PL/SQL Fundamentals NEW Duration: 5 Days What you will learn This Oracle Database: SQL and PL/SQL Fundamentals
PERFORMANCE EVALUATION AUDIT CHECKLIST EXAMPLE. EIIP Volume VI
Final 7/96 APPENDIX E - PERFORMANCE EVALUATION AUDIT APPENDIX E PERFORMANCE EVALUATION AUDIT CHECKLIST EXAMPLE APPENDIX E - PERFORMANCE EVALUATION AUDIT Final 7/96 This page is intentionally left blank.
Financial Data Access with SQL, Excel & VBA
Computational Finance and Risk Management Financial Data Access with SQL, Excel & VBA Guy Yollin Instructor, Applied Mathematics University of Washington Guy Yollin (Copyright 2012) Data Access with SQL,
5. CHANGING STRUCTURE AND DATA
Oracle For Beginners Page : 1 5. CHANGING STRUCTURE AND DATA Altering the structure of a table Dropping a table Manipulating data Transaction Locking Read Consistency Summary Exercises Altering the structure
- Suresh Khanal. http://mcqsets.com. http://www.psexam.com Microsoft Excel Short Questions and Answers 1
- Suresh Khanal http://mcqsets.com http://www.psexam.com Microsoft Excel Short Questions and Answers 1 Microsoft Access Short Questions and Answers with Illustrations Part I Suresh Khanal Kalanki, Kathmandu
1.0 INTRODUCTION 1.1 Overview
Guidance document for the writing of standard operating procedures (Taken from United States Environmental Protection Agency Guidance for Preparing Standard Operating Procedures (SOPs) EPA QA/G- 6 [EPA/600/B-
BCA. Database Management System
BCA IV Sem Database Management System Multiple choice questions 1. A Database Management System (DBMS) is A. Collection of interrelated data B. Collection of programs to access data C. Collection of data
Driver for JDBC Implementation Guide
www.novell.com/documentation Driver for JDBC Implementation Guide Identity Manager 4.0.2 January 2014 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use
Postgres Plus xdb Replication Server with Multi-Master User s Guide
Postgres Plus xdb Replication Server with Multi-Master User s Guide Postgres Plus xdb Replication Server with Multi-Master build 57 August 22, 2012 , Version 5.0 by EnterpriseDB Corporation Copyright 2012
Oracle SQL. Course Summary. Duration. Objectives
Oracle SQL Course Summary Identify the major structural components of the Oracle Database 11g Create reports of aggregated data Write SELECT statements that include queries Retrieve row and column data
MHRA GMP Data Integrity Definitions and Guidance for Industry March 2015
MHRA GMP Data Integrity Definitions and Guidance for Industry Introduction: Data integrity is fundamental in a pharmaceutical quality system which ensures that medicines are of the required quality. This
What is a database? COSC 304 Introduction to Database Systems. Database Introduction. Example Problem. Databases in the Real-World
COSC 304 Introduction to Systems Introduction Dr. Ramon Lawrence University of British Columbia Okanagan [email protected] What is a database? A database is a collection of logically related data for
Enterprise Data Dictionary Standards
Department of Education, Federal Student Aid Enterprise Data Dictionary Standards Version: 1.0 Draft April 2007 List of Figures Table of Contents Purpose... 1 Background... 2 1.0 Overview... 3 1.1 Introduction...
DICOM Conformance Statement Print Management Service Class FUJI NETWORK PRINT SERVER FN-PS551
DICOM Conformance Statement Print Management Service Class FUJI NETWORK PRINT SERVER FN-PS55 October 006 5th Edition Copyright FUJIFILM Corporation, Japan 897N00094A (006-03-40) 006.0 Revision History
Managing Objects with Data Dictionary Views. Copyright 2006, Oracle. All rights reserved.
Managing Objects with Data Dictionary Views Objectives After completing this lesson, you should be able to do the following: Use the data dictionary views to research data on your objects Query various
Microsoft Access 2010 Overview of Basics
Opening Screen Access 2010 launches with a window allowing you to: create a new database from a template; create a new template from scratch; or open an existing database. Open existing Templates Create
Xcalibur. Foundation. Administrator Guide. Software Version 3.0
Xcalibur Foundation Administrator Guide Software Version 3.0 XCALI-97520 Revision A May 2013 2013 Thermo Fisher Scientific Inc. All rights reserved. LCquan, Watson LIMS, and Web Access are trademarks,
MS ACCESS DATABASE DATA TYPES
MS ACCESS DATABASE DATA TYPES Data Type Use For Size Text Memo Number Text or combinations of text and numbers, such as addresses. Also numbers that do not require calculations, such as phone numbers,
[MS-SPACSOM]: Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SPACSOM]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
Infusion Business Software Update 8.200
Infusion Business Software Update 8.200 Administration The re-index process now has an option to complete all the Integrity checks for Customers, Suppliers, Products and Financials along with a History
Oracle Database 10g: Introduction to SQL
Oracle University Contact Us: 1.800.529.0165 Oracle Database 10g: Introduction to SQL Duration: 5 Days What you will learn This course offers students an introduction to Oracle Database 10g database technology.
214 Transportation Carrier Shipment Status Message
214 Transportation Carrier Shipment Status Message Introduction: Functional Group ID=QM This Draft Standard for Tria l Use contains the format and establishes the data contents of the Transportation Carrier
Kaseya 2. Quick Start Guide. for VSA 6.3
Kaseya 2 Custom Reports Quick Start Guide for VSA 6.3 December 9, 2013 Agreement The purchase and use of all Software and Services is subject to the Agreement as defined in Kaseya s Click-Accept EULA as
Clinical Data Management (Process and practical guide) Dr Nguyen Thi My Huong WHO/RHR/RCP/SIS
Clinical Data Management (Process and practical guide) Dr Nguyen Thi My Huong WHO/RHR/RCP/SIS Training Course in Sexual and Reproductive Health Research Geneva 2012 OUTLINE Clinical Data Management CDM
Chapter 23. Database Security. Security Issues. Database Security
Chapter 23 Database Security Security Issues Legal and ethical issues Policy issues System-related issues The need to identify multiple security levels 2 Database Security A DBMS typically includes a database
Oracle 10g PL/SQL Training
Oracle 10g PL/SQL Training Course Number: ORCL PS01 Length: 3 Day(s) Certification Exam This course will help you prepare for the following exams: 1Z0 042 1Z0 043 Course Overview PL/SQL is Oracle's Procedural
not at all a manual simply a quick how-to-do guide
not at all a manual simply a quick how-to-do guide As a general rule, the GUI implemented by spatialite-gis is closely related to the one implemented by the companion app spatialite-gui So, if you are
Core Components Data Type Catalogue Version 3.1 17 October 2011
Core Components Data Type Catalogue Version 3.1 17 October 2011 Core Components Data Type Catalogue Version 3.1 Page 1 of 121 Abstract CCTS 3.0 defines the rules for developing Core Data Types and Business
Parameter Fields and Prompts. chapter
Parameter Fields and Prompts chapter 23 Parameter Fields and Prompts Parameter and prompt overview Parameter and prompt overview Parameters are Crystal Reports fields that you can use in a Crystal Reports
Software Architecture Document
Software Architecture Document Project Management Cell 1.0 1 of 16 Abstract: This is a software architecture document for Project Management(PM ) cell. It identifies and explains important architectural
ACDM GUIDELINES TO FACILITATE PRODUCTION OF A DATA HANDLING PROTOCOL
ACDM GUIDELINES TO FACILITATE PRODUCTION OF A DATA HANDLING PROTOCOL BACKGROUND The need was identified by the Electronic Data Transfer Special Interest Group (SIG) for each company or organisation to
MRA Data Transfer Catalogue (DTC) Change Proposal Form
MRA Data Transfer Catalogue (DTC) Change Proposal Form YOUR REFERENCE ORIGINATOR (MRA Change Administrator) DTC CP NUMBER (assigned by Gemserv Change Co-ordination) SPONSOR APPROVAL (MRA Contract Manager)
Data Management Implementation Plan
Appendix 8.H Data Management Implementation Plan Prepared by Vikram Vyas CRESP-Amchitka Data Management Component 1. INTRODUCTION... 2 1.1. OBJECTIVES AND SCOPE... 2 2. DATA REPORTING CONVENTIONS... 2
Wave Analytics Data Integration Guide
Wave Analytics Data Integration Guide Salesforce, Winter 16 @salesforcedocs Last updated: November 6, 2015 Copyright 2000 2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark
MS Access: Advanced Tables and Queries. Lesson Notes Author: Pamela Schmidt
Lesson Notes Author: Pamela Schmidt Tables Text Fields (Default) Text or combinations of text and numbers, as well as numbers that don't require calculations, such as phone numbers. or the length set by
Managing Users and Identity Stores
CHAPTER 8 Overview ACS manages your network devices and other ACS clients by using the ACS network resource repositories and identity stores. When a host connects to the network through ACS requesting
SIF Validation Tool. Wages Protection System Qatar Central Bank& Ministry of Labour And Social Affairs. End User Guide
SIF Validation Tool Wages Protection System Qatar Central Bank& Ministry of Labour And Social Affairs End User Guide [1] SIF Validation Tool at a Glance Content 1 SIF VALIDATION TOOL AT A GLANCE 3 2 GETTING
