<subfieldcode="a">Persistent storage of non-event data in the CMS databases</subfield>
</datafield>
<datafieldtag="260"ind1=" "ind2=" ">
<subfieldcode="c">2010</subfield>
</datafield>
<datafieldtag="269"ind1=" "ind2=" ">
<subfieldcode="c">12 Jan 2010</subfield>
</datafield>
<datafieldtag="300"ind1=" "ind2=" ">
<subfieldcode="a">20 p</subfield>
</datafield>
<datafieldtag="500"ind1=" "ind2=" ">
<subfieldcode="a">Comments: 20 pages, submitted to IOP</subfield>
</datafield>
<datafieldtag="520"ind1=" "ind2=" ">
<subfieldcode="a">In the CMS experiment, the non event data needed to set up the detector, or being produced by it, and needed to calibrate the physical responses of the detector itself are stored in ORACLE databases. The large amount of data to be stored, the number of clients involved and the performance requirements make the database system an essential service for the experiment to run. This note describes the CMS condition database architecture, the data-flow and PopCon, the tool built in order to populate the offline databases. Finally, the first results obtained during the 2008 and 2009 cosmic data taking are presented.</subfield>
</datafield>
<datafieldtag="595"ind1=" "ind2=" ">
<subfieldcode="a">LANL EDS</subfield>
</datafield>
<datafieldtag="650"ind1="1"ind2="7">
<subfieldcode="2">arXiv</subfield>
<subfieldcode="a">Detectors and Experimental Techniques</subfield>
</datafield>
<datafieldtag="650"ind1="1"ind2="7">
<subfieldcode="2">arXiv</subfield>
<subfieldcode="a">Computing and Computers</subfield>