<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/archiving/creatinganarchivecompany" xml:lang="en">
   <Header>
      <Title>Creating an Archive Company</Title>
      <Keyword type="header" order="d1e4173">
         <Level1>Creating an archive company</Level1>
         <Level2>archiving</Level2>
      </Keyword>
      <Keyword type="header" order="d1e4178">
         <Level1>Archiving</Level1>
         <Level2>creating an archive company</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <SectionTitle>Number of archive companies</SectionTitle>
      <Paragraph>When you set up an archive company, various concepts and
		strategies are involved. You can have one archive company, which will be fed
		with data yearly, that is, the operational company will archive its data each
		year to the same archive company. Therefore, all data will be centrally stored.
		However, this concept has one major drawback: performance degradation. Due to
		the transfer of large amounts of data from the operational company to the
		archive company, over time, the archive company grows larger than the
		operational company. Therefore, you must make enough disk space available,
		which, in turn, significantly decreases the performance of the archive company
		as more data is archived.</Paragraph>
      <Paragraph>The second concept of setting up an archive company implies the
		data of the operational company will be archived each year to a new archive
		company. Having one archive company for each archiving period limits the size
		of the archive company, which, in turn, stabilizes the performance to access
		this data. You can easily store this archive company onto an external device
		for a longer period of time. At the end of the archiving cycle the data will be
		cleared. With one archive company for each year, you can easily drop the entire
		company at once, whereas filtering the old data that can be removed from one
		large archive involves more investigation and takes more time.</Paragraph>
      <Paragraph>Another point worth considering setting up the archive company
		is the strategy towards migration. If the operational company will be migrated
		in the future, the archive company must also be migrated. With this strategy,
		it is easier to migrate multiple smaller companies than one large archive
		company.</Paragraph>
      <Paragraph>When you archive in ERP Enterprise, you must keep close watch on the company numbers
		(operational – archive).</Paragraph>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>The subsequent procedure for creating an archive company is
			 valid for a standard, non-localized and non-customized ERP
			 environment.</ListItem>
            <ListItem>In the examples used throughout this document, companies 001
			 and 002 are operational companies; companies 901 and 902 are archive
			 companies.</ListItem>
            <ListItem>To perform the steps to create an archive company, you must
			 be super user.</ListItem>
         </List>
      </Note>
      <GeneralSection>
         <SectionTitle>Creating an archive company – overview</SectionTitle>
         <Figure space-and-orientation="indented-estimated">
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="666" width="427"
                      SRC="images/tr_flow_create_archive_company.gif"
                      alt="[...]"/>
         </Figure>
      </GeneralSection>
   </GeneralSection>
</ManualTopic>