ERP data archiving - a critical analysis
ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases...
Ausführliche Beschreibung
Autor*in: |
---|
Format: |
E-Artikel |
---|---|
Sprache: |
Englisch |
Erschienen: |
2004 |
---|
Schlagwörter: |
---|
Umfang: |
11 |
---|
Reproduktion: |
Emerald Fulltext Archive Database 1994-2005 |
---|---|
Übergeordnetes Werk: |
In: Journal of enterprise information management - Bradford : Emerald, 2004, 17(2004), 2, Seite 131-141 |
Übergeordnetes Werk: |
volume:17 ; year:2004 ; number:2 ; pages:131-141 ; extent:11 |
Links: |
---|
DOI / URN: |
10.1108/17410390410518772 |
---|
Katalog-ID: |
NLEJ219594511 |
---|
LEADER | 01000caa a22002652 4500 | ||
---|---|---|---|
001 | NLEJ219594511 | ||
003 | DE-627 | ||
005 | 20210707090305.0 | ||
007 | cr uuu---uuuuu | ||
008 | 090811s2004 xxk|||||o 00| ||eng c | ||
024 | 7 | |a 10.1108/17410390410518772 |2 doi | |
035 | |a (DE-627)NLEJ219594511 | ||
040 | |a DE-627 |b ger |c DE-627 |e rakwb | ||
041 | |a eng | ||
044 | |c XA-GB | ||
245 | 1 | 0 | |a ERP data archiving - a critical analysis |
264 | 1 | |c 2004 | |
300 | |a 11 | ||
336 | |a nicht spezifiziert |b zzz |2 rdacontent | ||
337 | |a nicht spezifiziert |b z |2 rdamedia | ||
338 | |a nicht spezifiziert |b zu |2 rdacarrier | ||
520 | |a ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. | ||
533 | |f Emerald Fulltext Archive Database 1994-2005 | ||
650 | 4 | |a Data storage | |
650 | 4 | |a Databases | |
700 | 1 | |a Mensching, James |4 oth | |
700 | 1 | |a Corbitt, Gail |4 oth | |
773 | 0 | 8 | |i In |t Journal of enterprise information management |d Bradford : Emerald, 2004 |g 17(2004), 2, Seite 131-141 |h Online-Ressource |w (DE-627)NLEJ219577919 |w (DE-600)2144850-4 |7 nnns |
773 | 1 | 8 | |g volume:17 |g year:2004 |g number:2 |g pages:131-141 |g extent:11 |
856 | 4 | 0 | |u http://dx.doi.org/10.1108/17410390410518772 |
912 | |a GBV_USEFLAG_U | ||
912 | |a ZDB-1-EFD | ||
912 | |a GBV_NL_ARTICLE | ||
951 | |a AR | ||
952 | |d 17 |j 2004 |e 2 |h 131-141 |g 11 |
matchkey_str |
menschingjamescorbittgail:2004----:rdtaciigciia |
---|---|
hierarchy_sort_str |
2004 |
publishDate |
2004 |
allfields |
10.1108/17410390410518772 doi (DE-627)NLEJ219594511 DE-627 ger DE-627 rakwb eng XA-GB ERP data archiving - a critical analysis 2004 11 nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. Emerald Fulltext Archive Database 1994-2005 Data storage Databases Mensching, James oth Corbitt, Gail oth In Journal of enterprise information management Bradford : Emerald, 2004 17(2004), 2, Seite 131-141 Online-Ressource (DE-627)NLEJ219577919 (DE-600)2144850-4 nnns volume:17 year:2004 number:2 pages:131-141 extent:11 http://dx.doi.org/10.1108/17410390410518772 GBV_USEFLAG_U ZDB-1-EFD GBV_NL_ARTICLE AR 17 2004 2 131-141 11 |
spelling |
10.1108/17410390410518772 doi (DE-627)NLEJ219594511 DE-627 ger DE-627 rakwb eng XA-GB ERP data archiving - a critical analysis 2004 11 nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. Emerald Fulltext Archive Database 1994-2005 Data storage Databases Mensching, James oth Corbitt, Gail oth In Journal of enterprise information management Bradford : Emerald, 2004 17(2004), 2, Seite 131-141 Online-Ressource (DE-627)NLEJ219577919 (DE-600)2144850-4 nnns volume:17 year:2004 number:2 pages:131-141 extent:11 http://dx.doi.org/10.1108/17410390410518772 GBV_USEFLAG_U ZDB-1-EFD GBV_NL_ARTICLE AR 17 2004 2 131-141 11 |
allfields_unstemmed |
10.1108/17410390410518772 doi (DE-627)NLEJ219594511 DE-627 ger DE-627 rakwb eng XA-GB ERP data archiving - a critical analysis 2004 11 nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. Emerald Fulltext Archive Database 1994-2005 Data storage Databases Mensching, James oth Corbitt, Gail oth In Journal of enterprise information management Bradford : Emerald, 2004 17(2004), 2, Seite 131-141 Online-Ressource (DE-627)NLEJ219577919 (DE-600)2144850-4 nnns volume:17 year:2004 number:2 pages:131-141 extent:11 http://dx.doi.org/10.1108/17410390410518772 GBV_USEFLAG_U ZDB-1-EFD GBV_NL_ARTICLE AR 17 2004 2 131-141 11 |
allfieldsGer |
10.1108/17410390410518772 doi (DE-627)NLEJ219594511 DE-627 ger DE-627 rakwb eng XA-GB ERP data archiving - a critical analysis 2004 11 nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. Emerald Fulltext Archive Database 1994-2005 Data storage Databases Mensching, James oth Corbitt, Gail oth In Journal of enterprise information management Bradford : Emerald, 2004 17(2004), 2, Seite 131-141 Online-Ressource (DE-627)NLEJ219577919 (DE-600)2144850-4 nnns volume:17 year:2004 number:2 pages:131-141 extent:11 http://dx.doi.org/10.1108/17410390410518772 GBV_USEFLAG_U ZDB-1-EFD GBV_NL_ARTICLE AR 17 2004 2 131-141 11 |
allfieldsSound |
10.1108/17410390410518772 doi (DE-627)NLEJ219594511 DE-627 ger DE-627 rakwb eng XA-GB ERP data archiving - a critical analysis 2004 11 nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. Emerald Fulltext Archive Database 1994-2005 Data storage Databases Mensching, James oth Corbitt, Gail oth In Journal of enterprise information management Bradford : Emerald, 2004 17(2004), 2, Seite 131-141 Online-Ressource (DE-627)NLEJ219577919 (DE-600)2144850-4 nnns volume:17 year:2004 number:2 pages:131-141 extent:11 http://dx.doi.org/10.1108/17410390410518772 GBV_USEFLAG_U ZDB-1-EFD GBV_NL_ARTICLE AR 17 2004 2 131-141 11 |
language |
English |
source |
In Journal of enterprise information management 17(2004), 2, Seite 131-141 volume:17 year:2004 number:2 pages:131-141 extent:11 |
sourceStr |
In Journal of enterprise information management 17(2004), 2, Seite 131-141 volume:17 year:2004 number:2 pages:131-141 extent:11 |
format_phy_str_mv |
Article |
institution |
findex.gbv.de |
topic_facet |
Data storage Databases |
isfreeaccess_bool |
false |
container_title |
Journal of enterprise information management |
authorswithroles_txt_mv |
Mensching, James @@oth@@ Corbitt, Gail @@oth@@ |
publishDateDaySort_date |
2004-01-01T00:00:00Z |
hierarchy_top_id |
NLEJ219577919 |
id |
NLEJ219594511 |
language_de |
englisch |
fullrecord |
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">NLEJ219594511</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20210707090305.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">090811s2004 xxk|||||o 00| ||eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1108/17410390410518772</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)NLEJ219594511</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="044" ind1=" " ind2=" "><subfield code="c">XA-GB</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">ERP data archiving - a critical analysis</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2004</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">11</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">zzz</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">z</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">zu</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper.</subfield></datafield><datafield tag="533" ind1=" " ind2=" "><subfield code="f">Emerald Fulltext Archive Database 1994-2005</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Data storage</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Databases</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Mensching, James</subfield><subfield code="4">oth</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Corbitt, Gail</subfield><subfield code="4">oth</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">In</subfield><subfield code="t">Journal of enterprise information management</subfield><subfield code="d">Bradford : Emerald, 2004</subfield><subfield code="g">17(2004), 2, Seite 131-141</subfield><subfield code="h">Online-Ressource</subfield><subfield code="w">(DE-627)NLEJ219577919</subfield><subfield code="w">(DE-600)2144850-4</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:17</subfield><subfield code="g">year:2004</subfield><subfield code="g">number:2</subfield><subfield code="g">pages:131-141</subfield><subfield code="g">extent:11</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">http://dx.doi.org/10.1108/17410390410518772</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_USEFLAG_U</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-1-EFD</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_NL_ARTICLE</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">17</subfield><subfield code="j">2004</subfield><subfield code="e">2</subfield><subfield code="h">131-141</subfield><subfield code="g">11</subfield></datafield></record></collection>
|
series2 |
Emerald Fulltext Archive Database 1994-2005 |
ppnlink_with_tag_str_mv |
@@773@@(DE-627)NLEJ219577919 |
format |
electronic Article |
delete_txt_mv |
keep |
collection |
NL |
remote_str |
true |
illustrated |
Not Illustrated |
topic_title |
ERP data archiving - a critical analysis Data storage Databases |
topic |
misc Data storage misc Databases |
spellingShingle |
misc Data storage misc Databases ERP data archiving - a critical analysis |
topic_unstemmed |
misc Data storage misc Databases |
topic_browse |
misc Data storage misc Databases |
format_facet |
Elektronische Aufsätze Aufsätze Elektronische Ressource |
format_main_str_mv |
Text Zeitschrift/Artikel |
carriertype_str_mv |
zu |
author2_variant |
j m jm g c gc |
hierarchy_parent_title |
Journal of enterprise information management |
hierarchy_parent_id |
NLEJ219577919 |
hierarchy_top_title |
Journal of enterprise information management |
isfreeaccess_txt |
false |
familylinks_str_mv |
(DE-627)NLEJ219577919 (DE-600)2144850-4 |
title |
ERP data archiving - a critical analysis |
ctrlnum |
(DE-627)NLEJ219594511 |
title_full |
ERP data archiving - a critical analysis |
journal |
Journal of enterprise information management |
journalStr |
Journal of enterprise information management |
lang_code |
eng |
isOA_bool |
false |
recordtype |
marc |
publishDateSort |
2004 |
contenttype_str_mv |
zzz |
container_start_page |
131 |
container_volume |
17 |
physical |
11 |
format_se |
Elektronische Aufsätze |
countryofpublication_str_mv |
XA-GB |
doi_str_mv |
10.1108/17410390410518772 |
title_sort |
erp data archiving - a critical analysis |
title_auth |
ERP data archiving - a critical analysis |
abstract |
ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. |
abstractGer |
ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. |
abstract_unstemmed |
ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper. |
collection_details |
GBV_USEFLAG_U ZDB-1-EFD GBV_NL_ARTICLE |
container_issue |
2 |
title_short |
ERP data archiving - a critical analysis |
url |
http://dx.doi.org/10.1108/17410390410518772 |
remote_bool |
true |
author2 |
Mensching, James Corbitt, Gail |
author2Str |
Mensching, James Corbitt, Gail |
ppnlink |
NLEJ219577919 |
mediatype_str_mv |
z |
isOA_txt |
false |
hochschulschrift_bool |
false |
author2_role |
oth oth |
doi_str |
10.1108/17410390410518772 |
up_date |
2024-07-06T05:35:55.508Z |
_version_ |
1803806735607005184 |
fullrecord_marcxml |
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">NLEJ219594511</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20210707090305.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">090811s2004 xxk|||||o 00| ||eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1108/17410390410518772</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)NLEJ219594511</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="044" ind1=" " ind2=" "><subfield code="c">XA-GB</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">ERP data archiving - a critical analysis</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2004</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">11</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">zzz</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">z</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">zu</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">ERP (enterprise resource planning) systems run on top of database systems, like Oracle, SQL Server and DB2. The longer these systems are in place within organizations the larger the databases are. Some sources estimate that corporate databases double or triple in size every year. As these databases grow, performance, the time it takes to complete transactions, is adversely affected. This implies that limiting the amount of data stored on an ERP system is an essential element of proper storage and data management. However, removing data from an ERP system can be a complex and risky task. Archiving ERP data is an area of academic and professional research that has had minimal attention. This paper examines the issues and provides insight into solutions associated with archiving ERP data. The issues are explored by summarizing the limited background and research in the archiving area, followed by an overview of the methodology used to arrive at the case study approach used to gather the data. Case data are presented from three different large corporate environments and the results of the data are used to recommend an archiving strategy that other companies can follow. A discussion of the implications of the proposed archiving strategy for future use and research concludes the paper.</subfield></datafield><datafield tag="533" ind1=" " ind2=" "><subfield code="f">Emerald Fulltext Archive Database 1994-2005</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Data storage</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Databases</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Mensching, James</subfield><subfield code="4">oth</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Corbitt, Gail</subfield><subfield code="4">oth</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">In</subfield><subfield code="t">Journal of enterprise information management</subfield><subfield code="d">Bradford : Emerald, 2004</subfield><subfield code="g">17(2004), 2, Seite 131-141</subfield><subfield code="h">Online-Ressource</subfield><subfield code="w">(DE-627)NLEJ219577919</subfield><subfield code="w">(DE-600)2144850-4</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:17</subfield><subfield code="g">year:2004</subfield><subfield code="g">number:2</subfield><subfield code="g">pages:131-141</subfield><subfield code="g">extent:11</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">http://dx.doi.org/10.1108/17410390410518772</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_USEFLAG_U</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-1-EFD</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_NL_ARTICLE</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">17</subfield><subfield code="j">2004</subfield><subfield code="e">2</subfield><subfield code="h">131-141</subfield><subfield code="g">11</subfield></datafield></record></collection>
|
score |
7.4025593 |