Either will work (or anything that is MySQL compatible. We use AWS Aurora). The main point to me of that statement is to be sure not to run production level ArchivesSpace using the local, base level database which is for testing purposes only.
So use either one. For the ArchivesSpace database, there should be no difference in functionality. Tom On Wed, Aug 18, 2021 at 9:21 AM Kat Spears <[email protected]> wrote: > Our IT Manager had a question as we are preparing to implement > ArchivesSpace. Perhaps someone could answer her question (below)? Any > feedback is appreciated. > > > > Thanks, > > kat > > > > Her message to me was: > > Under the “implementing ArchivesSpace” page it says > > > > *“The embedded database is for testing purposes only. You should use MySQL > or MariaDB for any data intended for production, including data in a test > instance that you intend to move over to a production instance.”* > > > > Question is – how did they address that need? > > > > Are people using MySQL or MariaDB, which is better to tie into > ArchivesSpace? > > > > > > *__* > > > > > *Katarina Spears **Library and Archives Manager* > > *O *804.262.9887 ext. 342 > > [email protected] <[email protected]> > > > > 1800 Lakeside Avenue > Richmond, VA 23228 > > > > [image: /Volumes/Clients A-L/Lewis-Ginter/16 Projects/16LGB1710 Lewis > Ginter Brand Refresh/06_Final/Wordmark/PRIMARY_FullMark/COLOR/RGB > (digital)/PNG/LGBG_LogoPrimary_RGB_forEmailSignature.png] > <http://www.lewisginter.org/> > > > _______________________________________________ > Archivesspace_Users_Group mailing list > [email protected] > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* [email protected]
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
