Outlook 2011 had a proprietary database format and we (as users) had very few options to work with it.
Outlook 2016 now uses a sqlite3 databases for its identity (just like Mail).
While there is very little we can run from the app itself in terms of maintenance or troubleshooting, in theory we should be able to tap straight into the database through sqlite3 itself.<\/p>\n
*********\u00a0NONE OF THIS<\/span> IS PUBLISHED<\/span>\/APPROVED\/SUPPORTED BY MICROSOFT FOR OUTLOOK FOR MAC<\/span>\u00a0*********<\/p>\n As none of this is officially supported, I would recommend That are in the ~\/Library\/Group Containers\/UBF8T346G9.Office\/Outlook\/Outlook 15 Profiles\/Main Profile\/Data<\/em> folder.<\/p>\n 2) QUIT<\/span><\/strong> Outlook. You can’t run anything safely on the identity if it\u2019s still in use in Outlook itself.<\/p>\n \u2022\u00a0You can check the integrity of the database with the command: If everything is fine, the Terminal will return \u201cOK\u201d \u2022\u00a0A number of websites have illustrated how “vacuuming” the envelope index could help speed things up and trim the database in Mail. I figured that the same should apply to Outlook too. You can vacuum the database using: <\/p>\n On Answers<\/a>, Michal Palat provides additional options that can allow you to rebuild the sqlite3 database by exporting the data to an ASCII \u201cdump\u201d and recreating a new one based on the output: Outlook 2011 had a proprietary database format and we (as users) had very few options to work with it. Outlook 2016 now uses a sqlite3 databases for its identity (just like Mail). While there is very little we can run from the app itself in terms of maintenance or troubleshooting, in theory we should be able to tap straight into the database through sqlite3 itself. *********\u00a0NONE OF THIS IS PUBLISHED\/APPROVED\/SUPPORTED BY MICROSOFT FOR OUTLOOK FOR MAC\u00a0********* As none of this is officially supported, I would…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-295","post","type-post","status-publish","format-standard","hentry","category-outlook"],"_links":{"self":[{"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/posts\/295","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/comments?post=295"}],"version-history":[{"count":8,"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/posts\/295\/revisions"}],"predecessor-version":[{"id":321,"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/posts\/295\/revisions\/321"}],"wp:attachment":[{"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/media?parent=295"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/categories?post=295"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cortig.net\/wordpress\/wp-json\/wp\/v2\/tags?post=295"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
1) BACKUP<\/span><\/strong> the database before anything.
You need to backup the three files:<\/p>\n\n
(triple-click the command to select all, then copy)
\/usr\/bin\/sqlite3 ~\/Library\/Group\\ Containers\/UBF8T346G9.Office\/Outlook\/Outlook\\ 15\\ Profiles\/Main\\ Profile\/Data\/Outlook.sqlite \"PRAGMA integrity_check\"<\/code><\/p>\n
If you get a warning there, then obviously something in wrong in the database. In theory, Outlook should detect issues and automatically attempt to fix them, but there are been reports in the forums of identity failures and users no longer able to open up their identities. It might be worth attempting other “rescue” operations in these cases using additional commands like “.dump\u201d etc. (which is beyond the point of this post: search for your favorite sqlite How To or Forum page for additional information on how to repair a corrupted sqlite3 database<\/a>).<\/p>\n
I ran the command in Outlook and the database shrunk a bit. No problem within Outlook whatsoever on my Mac, but who knows\u2026 (hence the very very strong suggestion to make a backup).
\u201cVacuuming<\/a>\u201d\u00a0will rebuild the database file, reclaiming free space and defragmenting tables and index. I’m not sure whether Outlook is currently using auto_vacuum or not, but I have read reports of abnormally large Outlook database files which makes me suspect it’s not always taking place as it should if it is even enabled.<\/p>\n
(triple-click the command to select all, then copy)
\/usr\/bin\/sqlite3 ~\/Library\/Group\\ Containers\/UBF8T346G9.Office\/Outlook\/Outlook\\ 15\\ Profiles\/Main\\ Profile\/Data\/Outlook.sqlite vacuum<\/code><\/p>\n
\nhttps:\/\/answers.microsoft.com\/en-us\/msoffice\/forum\/msoffice_outlook-mso_mac\/outlook-2016-for-mac-outlook-couldnt-repair-the\/e486e7b1-6c6e-46e8-9387-36f2442508b9<\/a><\/p>","protected":false},"excerpt":{"rendered":"