Rebuild Microsoft Office 2008 Database Mac

Microsoft office 2008 download full version free download - Microsoft Office 2008 update, Microsoft Office 2010, Microsoft Office 2011, and many more programs. Enter to Search. My Profile Logout. Report and share information using database solutions. Free to try Publisher: Microsoft Downloads: 964,461.

  1. Microsoft Office 2008 Updates Download
  2. Iwork 09
-->
  • Aug 12, 2011 /Documents/Microsoft User Data/Office 2011 Identities/Main Identity/ Inside should be the database file simply named 'Database'. If you fix the permissions(Get Info- Sharing and Permissions) and it still isn't working, there is a repair tool called Microsoft Database Utility located in /Applications/Microsoft Office 2011/Office/.
  • Rebuild the Office database. On the Outlook menu, click Turn Off Office Reminders. Quit Messenger for Mac and all Microsoft Office applications, including Outlook. Open the Microsoft Database Utility. The default location is in /Applications/Microsoft Office 2011/Office/. Tip: You can also open the.
  • How do I Rebuild Outlook for Mac for Office 365 Database. I am continuously getting a pop-up window that says 'Something's wrong with Outlook Database. Please repair to fix the problem', and then when.
  • How to run Microsoft Database Utility in Mac In a case, your Microsoft Outlook in Mac has an issue, you may need to rebuild the Microsoft Database. Here is the how. Quit all applications. Hold down the Option key on the keyboard, and then start Outlook 2011.

Summary

This article describes some useful tools for Microsoft Outlook for Mac.

More information

Outlook Search Repair

The Outlook Search Repair tool repairs search results within Outlook.

Important

Due to some changes in macOS Mojave, this tool no longer works in 10.14 and higher. If you are on macOS Mojave (10.14), you can follow the steps below to reindex Spotlight for Outlook for Mac.

  1. Choose Apple menu, then System Preferences, and then Spotlight.

  2. Select the Privacy tab.

  3. In Finder:

    1. On the Go menu, select Go to Folder..

    2. Copy and paste the following location into the 'Go to the folder:' dialog box and select Go:

      ~/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/

  4. Drag the 'Main Profile' folder to the Privacy tab. Once added, remove the folder, and Spotlight will re-index the folder.

    You must perform this step for any additional profile folders you have.

See the following article from Apple to learn more: How to rebuild the Spotlight index on your Mac.

When to use the tool

Use this tool if search results within Outlook show nothing or return older items only. For example, if you search for an email message that you already have open and that message isn't displayed in the search results.

How to use the tool

  1. Download and open the Outlook Search Repair tool.

  2. Follow the instructions.

    Note The tool searches for duplicate installations of Outlook. If no duplicates are detected, go to step 3. If duplicates are detected, remove the duplicate Outlook installations, and then restart the system. After your system is restarted, the Outlook Search Repair tool may reopen. If it does reopen, exit and restart the tool.

  3. Select Reindex.

    Note The Outlook Search Repair tool displays a 'Reindexing, please wait' message while it works. Wait for this process to finish. This may require an hour or more, depending on the size of your Outlook profile. Outlook doesn't have to be open when the repair occurs. A spotlight search will be slower and may not finish while the index is being repaired.

  4. Exit the Outlook Search Repair tool when you receive the following message after the repair is completed:

    Done! Reindexing has completed!

OutlookResetPreferences

The Outlook Reset Preferences tool resets all Outlook preferences to their default settings.

When to use the tool

Use this tool to reset any customizations that you've made to Outlook by using the Preferences option on the Outlook menu. This tool also stores the settings for the Outlook window size and position. This tool shouldn't be needed most of the time. But it can be useful.

Note The Outlook Preferences file doesn't contain all the preferences for the application. Also, resetting Outlook preferences doesn't remove email messages or account settings.

How to use the tool

  1. Download and open the Outlook Reset Preferences tool.
  2. Click the Reset Now! button. This closes Outlook if it's open, and then resets the preferences to their default settings.
  3. Exit the Outlook Reset Preferences tool.

SetDefaultMailApp

The Default Mail Application tool lets you easily make Outlook the default mail application.

When to use the tool

Use this tool if you want Outlook to open a new email message when you click a mailto: link in an email message or on a website. Selecting a mailto: link opens the default email application. Outlook isn't the default email application until you change that setting.

How to use the tool

  1. Download and open the Default Mail Application tool.
  2. In the Default Mail Application dialog box, select com.microsoft.outlook, and then click Make Default.
  3. Exit the Default Mail Application tool.

ResetRecentAddresses

The Reset Recent Addresses tool lets you reset recent addresses that Outlook stores. This tool deletes all recent addresses instead of you having to manually delete addresses one at a time.

When to use the tool

When you compose an email message and add people on the To, Cc, or Bcc line, Outlook suggests names as you type characters. The list of names that Outlook uses is a combination of stored contacts, the company directory, and recent contacts. Recent contacts have an 'X' character next to each name. Without this tool, you have to click the 'X' on each contact to remove that contact from the Recent Address List. The Reset Recent Addresses tool cleans out all recent addresses at the same time.

How to use the tool

  1. Download and open the ResetRecentAddresses tool.
  2. Click the Reset Now! button.
  3. Exit the Reset Outlook Recent Addresses tool.
-->

APPLIES TO: SQL Server Azure SQL Database Azure Synapse Analytics (SQL DW) Parallel Data Warehouse

System databases must be rebuilt to fix corruption problems in the master, model, msdb, or resource system databases or to modify the default server-level collation. This topic provides step-by-step instructions to rebuild system databases in SQL Server 2019 (15.x).

In This Topic

  • Before you begin:

  • Procedures:

  • Follow Up:

Before You Begin

Limitations and Restrictions

When the master, model, msdb, and tempdb system databases are rebuilt, the databases are dropped and re-created in their original location. If a new collation is specified in the rebuild statement, the system databases are created using that collation setting. Any user modifications to these databases are lost. For example, you may have user-defined objects in the master database, scheduled jobs in msdb, or changes to the default database settings in the model database.

Prerequisites

Perform the following tasks before you rebuild the system databases to ensure that you can restore the system databases to their current settings.

  1. Record all server-wide configuration values.

  2. Record all hotfixes applied to the instance of SQL Server and the current collation. You must reapply these hotfixes after rebuilding the system databases.

  3. Record the current location of all data and log files for the system databases. Rebuilding the system databases installs all system databases to their original location. If you have moved system database data or log files to a different location, you must move the files again.

  4. Locate the current backup of the master, model, and msdb databases.

  5. If the instance of SQL Server is configured as a replication Distributor, locate the current backup of the distribution database.

  6. Ensure you have appropriate permissions to rebuild the system databases. To perform this operation, you must be a member of the sysadmin fixed server role. For more information, see Server-Level Roles.

  7. Verify that copies of the master, model, msdb data and log template files exist on the local server. The default location for the template files is C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLBinnTemplates. These files are used during the rebuild process and must be present for Setup to succeed. If they are missing, run the Repair feature of Setup, or manually copy the files from your installation media. To locate the files on the installation media, navigate to the appropriate platform directory (x86 or x64) and then navigate to setupsql_engine_core_inst_msiPfilesSqlServrMSSQL.XMSSQLBinnTemplates.

    Microsoft Office 2016 - Unmistakably Office, designed for Mac. The new versions of Word, Excel, PowerPoint, Outlook and OneNote provide the best of both worlds for Mac users - the familiar Office experience paired with the best of Mac. If you already use Office on a PC or iPad, you will find yourself right at home in Office 2016 for Mac. Office 365 customers get the new Office for Mac first. You’ll have Office applications on your Mac or PC, apps on tablets and smartphones for when you're on the go, and Office Online on the web for everywhere in between. Jun 16, 2019  apps.apple.com. Music download for mac.

Rebuild System Databases

The following procedure rebuilds the master, model, msdb, and tempdb system databases. You cannot specify the system databases to be rebuilt. For clustered instances, this procedure must be performed on the active node and the SQL Server resource in the corresponding cluster application group must be taken offline before performing the procedure.

This procedure does not rebuild the resource database. See the section, 'Rebuild the resource Database Procedure' later in this topic.

To rebuild system databases for an instance of SQL Server:

  1. Insert the SQL Server 2019 (15.x) installation media into the disk drive, or, from a command prompt, change directories to the location of the setup.exe file on the local server. The default location on the server is C:Program FilesMicrosoft SQL Server130Setup BootstrapSQLServer2016.

  2. From a command prompt window, enter the following command. Square brackets are used to indicate optional parameters. Do not enter the brackets. When using a Windows operating system that has User Account Control (UAC) enabled, running Setup requires elevated privileges. The command prompt must be run as Administrator.

    Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts [ /SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName]

    Parameter nameDescription
    /QUIET or /QSpecifies that Setup run without any user interface.
    /ACTION=REBUILDDATABASESpecifies that Setup re-create the system databases.
    /INSTANCENAME=InstanceNameIs the name of the instance of SQL Server. For the default instance, enter MSSQLSERVER.
    /SQLSYSADMINACCOUNTS=accountsSpecifies the Windows groups or individual accounts to add to the sysadmin fixed server role. When specifying more than one account, separate the accounts with a blank space. For example, enter BUILTINAdministrators MyDomainMyUser. When you are specifying an account that contains a blank space within the account name, enclose the account in double quotation marks. For example, enter NT AUTHORITYSYSTEM.
    [ /SAPWD=StrongPassword ]Specifies the password for the SQL Server sa account. This parameter is required if the instance uses Mixed Authentication (SQL Server and Windows Authentication) mode.
    ** Security Note ** The sa account is a well-known SQL Server account and it is often targeted by malicious users. It is very important that you use a strong password for the sa login.
    Do not specify this parameter for Windows Authentication mode.
    [ /SQLCOLLATION=CollationName ]Specifies a new server-level collation. This parameter is optional. When not specified, the current collation of the server is used.
    ** Important ** Changing the server-level collation does not change the collation of existing user databases. All newly created user databases will use the new collation by default.
    For more information, see Set or Change the Server Collation.
    [ /SQLTEMPDBFILECOUNT=NumberOfFiles ]Specifies the number of tempdb data files. This value can be increased up to 8 or the number of cores, whichever is higher.
    Default value: 8 or the number of cores, whichever is lower.
    [ /SQLTEMPDBFILESIZE=FileSizeInMB ]Specifies the initial size of each tempdb data file in MB. Setup allows the size up to 1024 MB.
    Default value: 8
    [ /SQLTEMPDBFILEGROWTH=FileSizeInMB ]Specifies the file growth increment of each tempdb data file in MB. A value of 0 indicates that automatic growth is off and no additional space is allowed. Setup allows the size up to 1024 MB.
    Default value: 64
    [ /SQLTEMPDBLOGFILESIZE=FileSizeInMB ]Specifies the initial size of the tempdb log file in MB. Setup allows the size up to 1024 MB.
    Default value: 8.
    Allowed range: Min = 8, max = 1024.
    [ /SQLTEMPDBLOGFILEGROWTH=FileSizeInMB ]Specifies the file growth increment of the tempdb log file in MB. A value of 0 indicates that automatic growth is off and no additional space is allowed. Setup allows the size up to 1024 MB.
    Default value: 64
    Allowed range: Min = 8, max = 1024.
    [ /SQLTEMPDBDIR=Directories ]Specifies the directories for tempdb data files. When specifying more than one directory, separate the directories with a blank space. If multiple directories are specified the tempdb data files will be spread across the directories in a round-robin fashion.
    Default value: System Data Directory
    [ /SQLTEMPDBLOGDIR=Directory ]Specifies the directory for the tempdb log file.
    Default value: System Data Directory

  3. When Setup has completed rebuilding the system databases, it returns to the command prompt with no messages. Examine the Summary.txt log file to verify that the process completed successfully. This file is located at C:Program FilesMicrosoft SQL Server130Setup BootstrapLogs.

  4. RebuildDatabase scenario deletes system databases and installs them again in clean state. Because the setting of tempdb file count does not persist, the value of number of tempdb files is not known during setup. Therefore, RebuildDatabase scenario does not know the count of tempdb files to be re-added. You can provide the value of the number of tempdb files again with the SQLTEMPDBFILECOUNT parameter. If the parameter is not provided, RebuildDatabase will add a default number of tempdb files, which is as many tempdb files as the CPU count or 8, whichever is lower.

Post-Rebuild Tasks

After rebuilding the database you may need to perform the following additional tasks:

  • Restore your most recent full backups of the master, model, and msdb databases. For more information, see Back Up and Restore of System Databases (SQL Server).

    Important

    If you have changed the server collation, do not restore the system databases. Doing so will replace the new collation with the previous collation setting.

    If a backup is not available or if the restored backup is not current, re-create any missing entries. For example, re-create all missing entries for your user databases, backup devices, SQL Server logins, end points, and so on. The best way to re-create entries is to run the original scripts that created them.

Important

We recommend that you secure your scripts to prevent their being altered by unauthorized by individuals.

  • If the instance of SQL Server is configured as a replication Distributor, you must restore the distribution database. For more information, see Back Up and Restore Replicated Databases.

  • Move the system databases to the locations you recorded previously. For more information, see Move System Databases.

  • Verify the server-wide configuration values match the values you recorded previously.

Rebuild the resource Database

The following procedure rebuilds the resource system database. When you rebuild the resource database, all hot fixes are lost, and therefore must be reapplied.

To rebuild the resource system database:

  1. Launch the SQL Server 2019 (15.x) Setup program (setup.exe) from the distribution media.

  2. In the left navigation area, click Maintenance, and then click Repair.

  3. Setup support rule and file routines run to ensure that your system has prerequisites installed and that the computer passes Setup validation rules. Click OK or Install to continue.

  4. On the Select Instance page, select the instance to repair, and then click Next.

  5. The repair rules will run to validate the operation. To continue, click Next.

  6. From the Ready to Repair page, click Repair. The Complete page indicates that the operation is finished.

Create a New msdb Database

If the msdb database is damaged and you do not have a backup of the msdb database, you can create a new msdb by using the instmsdb script.

Warning

Rebuilding the msdb database using the instmsdb script will eliminate all the information stored in msdb such as jobs, alert, operators, maintenance plans, backup history, Policy-Based Management settings, Database Mail, Performance Data Warehouse, etc.

  1. Stop all services connecting to the Database Engine, including SQL Server Agent, SSRS, SSIS, and all applications using SQL Server as data store.

  2. Start SQL Server from the command line using the command: NET START MSSQLSERVER /T3608

    For more information, see Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service.

  3. In another command line window, detach the msdb database by executing the following command, replacing <servername> with the instance of SQL Server: SQLCMD -E -S<servername> -dmaster -Q'EXEC sp_detach_db msdb'

  4. Using the Windows Explorer, rename the msdb database files. By default these are in the DATA sub-folder for the SQL Server instance.

  5. Using SQL Server Configuration Manager, stop and restart the Database Engine service normally.

  6. In a command line window, connect to SQL Server and execute the command: SQLCMD -E -S<servername> -i'C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLInstallinstmsdb.sql' -o'C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLInstallinstmsdb.out'

    Replace <servername> with the instance of the Database Engine. Use the file system path of the instance of SQL Server.

  7. Using the Windows Notepad, open the instmsdb.out file and check the output for any errors.

  8. Re-apply any hotfix installed on the instance.

  9. Recreate the user content stored in the msdb database, such as jobs, alert, etc.

  10. Backup the msdb database.

Troubleshoot Rebuild Errors

Syntax and other run-time errors are displayed in the command prompt window. Examine the Setup statement for the following syntax errors:

Microsoft Office 2008 Updates Download

  • Missing slash mark (/) in front of each parameter name.

  • Missing equal sign (=) between the parameter name and the parameter value.

  • Presence of blank spaces between the parameter name and the equal sign.

  • Presence of commas (,) or other characters that are not specified in the syntax.

Iwork 09

After the rebuild operation is complete, examine the SQL Server logs for any errors. The default log location is C:Program FilesMicrosoft SQL Server130Setup BootstrapLogs. To locate the log file that contains the results of the rebuild process, change directories to the Logs folder from a command prompt, and then run findstr /s RebuildDatabase summary*.*. This search will point you to any log files that contain the results of rebuilding system databases. Open the log files and examine them for relevant error messages.

See Also

Comments are closed.