“I have recently upgraded to SQL Server 2014, but there have been some issues with the application since the upgrade. Now I want to downgrade my SQL database to its previous version. I believe this downgrade will solve the current issues. Sadly, I do not know the process of restoring database from 2014 to 2008. Kindly suggest me an easy method to downgrade 2014 SQL Server.”

Prerequisites to Prevent Disaster During the Process

• This isn’t just a restore or recovery process in a database. Hence, it is beneficial to consider this as a migration process for data in SQL Server 2014 to SQL Server version 2008 and further carry out the process with complete precision. 
• Before initiating the process, it is important to lock the schema and put the source database, i.e., SQL Server 2014 database to read-only mode so that no data is changed or hampered during the migration process. 
• Never run the process directly on the production environment, as any issue or challenge can lead to bigger issues including permanent data loss in the database. It is better to run the commands on a clone database first. 
• To avoid any issues in the future regarding the process and why it took place, it is crucial to document the entire process.

These are some of the best practices database administrators can follow to avoid any disasters during the migration process. 

Method 1: Restore Database from SQL Server 2014 to 2008 Through Generate Script Wizard

In this method, Generate Scripts wizard is used to script the SQL database schema in a higher SQL database version. Then we get connected to a lower SQL Server version and run the script we have generated earlier. Thus, we are able to copy data and successfully restore database from 2014 to 2008.

#Stage 1: First, we have to script AdventureWorks database schema in SQL 2014 Server. To do that, we will use Generate Scripts wizard.

• To begin with, connect to SQL Server instance of 2014 version, In “Object Explorer.” Then right-click on Adventureworks database and expand Tasks. Select the option “Generate Scripts…”.
• Generate and Publish Scripts wizard will open. Skip Introduction screen and go to Choose Objects page by clicking Next.
• On the next page named “Choose Objects”, select Script entire database and all database objects. Click Next.
• On Set Scripting Options page, choose the file name and location where you want the script to be saved. Then click on Advanced button.
• A dialog box called Advanced Scripting Options will appear. You have to change certain options on this box. Set the value True for “Triggers,” “Indexes,” and “Primary Key.” Also set SQL Server 2008 R2 as “Script for Server Version” and Schema and Data as “Types of data to script.”
• Click OK to close this dialog box and get back to Set Scripting Options page. Click Next on that page to proceed with the restore database from SQL Server 2014 to 2008 process.
• On Summary page, review all the selections you have made and then click on Next button to start generating scripts.
• Once the script generation is completed, click Finish to close the wizard.

#Stage 2: Now, we have to run the SQL Script generated in stage 1 and copy data.

• Get connected to SQL Server 2008 in Object Explorer. Open previously saved SQL Server script in SQL Server Management Studio.
• You have to edit the script by specifying correct Adventureworks database data location and log files location. After that, run the script. This will create Adventureworks database on SQL Server 2008 instance.
• Once it gets executed successfully, refresh Object Explorer Database folder. You will see that the Adventureworks database has been downgraded.

Method 2: Restore Database From SQL Server 2014 to 2008 Automatically

It is understandable that most users do not want to go through such complex method. For them, there is an alternate method available in the market. Users can choose SQL Server Database Migrator to seamlessly downgrade SQL Server database 2014 to 2008. This tool has a simple interface that anyone can use without any problem. It does not take much time to restore SQL database using this application. Users need to fill the destination server name to restore the database. Then this software will smoothly downgrade the database to desired SQL Server version.

Free Download Purchase Now

Step-1. Launch the Software in the system.

Step-2. Now, Choose from Offline or Online to connect with the source server.

Step-3. After connecting to the server, preview the scanned data and click on Export button to restore database from SQL Server 2014 to 2008 method.

Step-4. Select the Destination SQL Server and add authentication details to restore files.

Step-5. Choose database objects to be restored and Click the Export button to complete it.

Final Thoughts

If you are looking for solution to restore database from SQL Server 2014 to 2008, this post will be of great help. It discussed two different methods of restoring SQL database 2014 to 2008. The method using Generate Script Wizard is a complex one and takes a lot of time for execution. So, we suggest users go for the alternate method of using the third-party tool. This program allows you to revert to the older version of SQL Server easily.

The post How to Restore Database from SQL Server 2014 to 2008 Version appeared first on SysTools Software.

Let’s first learn a little more about the issue and figure out the common causes for the issue. 

What is the ‘Dedicated SQL Server Instance Failed’ Error?

If we talk about the major challenge with this error, it’s that the users and database administrators cannot access their databases or SQL Server Instance. This might look like a smaller concern, but when we take a closer look, it’s way more complicated. We will now take a look at the common concerns raised due to this error:

• The first common challenge with the occurrence of this error is that the SQL Server services stop frequently. 
• The SQL Server is not able to connect with the SQL Server instance, further resulting in application connection failures.
• When the user tries to connect the SQL Server database to SSMS or other tools, it gets difficult as the instance doesn’t show in the list. This might create misunderstandings with users that SQL Server might not be installed on the device. 
• Not just with the database accessibility and connection, with this issue, database administrators can also encounter permission-related issues in the database. 
• If the SQL Server instance fails during start, users might face issues like partial updates or SQL Server patches implementation in the database. 

These are some of the common challenges and issues encountered by the users and database administrators. Let’s now take a look at the reasons why the error occurs and find the best ways to resolve the error in a hassle-free way. 

Common Causes for SQL Server Instance Failure in Database

Here, we will discuss some of the most common reasons that might have led to the error in the database and affected user workflow.

• If the SQL Server service fails to start due to some reasons, it can lead to an error. This can also happen due to SQL Server service crashes or other similar issues. This can also lead to various errors like Error 1067 in SQL Server.
• Another cause for the error is the corruption in the SQL Server database. If the master or msdb database in the SQL Server is corrupted or damaged, users may encounter inaccessibility issues in the databases. 
• To access any database or data in the SQL Server database, users and database administrators require certain permissions. If they do not have the required permissions to the service account, they might not be able to access the system database files and the data folders. 

After learning the causes for the dedicated SQL Server instance failed SCCM error, let’s now take a look at what methods can help the database administrators fix the issue. 

How to Resolve the Dedicated SQL Server Instance Failed Issue? Understanding the Methods

We will now take a look at the best ways to fix the issue effectively. Most of these solutions are troubleshooting ways. These methods don’t assure the repair completely, so for more precise results, we will also learn a smart way for this error. 

Method 1: Restart the SQL Server Service to Repair the Error

The first method of resolving the error requires checking if there are any issues with the SQL Server instance. The steps to fix dedicated SQL Server instance failed SCCM are given below: 

1. The first step is to open SQL Server Configuration Manager. 
2. Next, it is time to find and locate the damaged or corrupted SQL Server instance. 
3. Once done, restart the SQL Server service instance to check whether the issue has been resolved. 
4. If any error messages show up, note them and find the appropriate solutions or fixes for the displayed error. 

Moving on to the next method, let’s see how it helps fix the error. 

Method 2: Manage Permissions to Fix SQL Server Instance Failure Easily

The error also signifies that the database cannot be accessed due to permission issues in the database. To fix that, we will now take a look at the steps to repair the issue.

1. Check and identify the SQL Service account with the error. 
2. Next, go to the SQL Server directory.
3. From the directory, check and grant required permissions to the SQL Server service account. This includes permissions to access the data folders and system database files. 
4. Also, check the permissions of the error log directories and grant if needed.
5. After this, restart the SQL Server instance and check if it starts successfully. 

This is how the method helps users with repairing the issue and further accessing their data in a hassle-free way. Let’s now move to the next method to fix the error. 

Method 3: Fix Database Corruption to Resolve SQL Server Instance Failed Issue

As we read earlier, one of the common causes for the error is corruption in the database. This can affect the workflow for the database administrators and further lead to a risk of permanent data loss in the database. So, to resolve a dedicated SQL Server instance failed SCCM due to this cause, it becomes important to repair SQL database corruption using a dedicated SQL Recovery Tool. This utility is designed with smart features to completely fix the damaged databases and allow users to access their databases with complete efficiency.

Download Tool Purchase Now

We will now take a look at the steps to use this advanced utility:

1. Install and launch the tool on the device. Click on Open Button to add the affected database file.
2. Choose a scan mode depending on the severity of the corruption in the database.
3. After the scan, preview the recovered files and click on the Export button.
4. In the export window, choose the destination to save the recovered data. Then add the authentication details.
5.  Next, choose the database objects to be exported. Click on Export button to fix SQL Server instance failure completely. 

These steps will help you recover data after a database corruption in the database. It is always better to go for a trusted solution in such cases to minimize the risk of data loss in the SQL Server database. Let’s now take a look at some of the best practices to help avoid this error from occurring and affecting the workflow.

Prevention Tips for dedicated SQL Server Instance Failed SCCM Error

Here are some of the prevention tips that will help users avoid the issue in the future. 

• It is important to secure the databases from any damages or corruption to avoid the error from occurring in the first place. 
• Take backup of the databases and store them in a different disk to easily recover the databases when needed. 
• To keep the databases healthy, regularly monitor the disk health and free the space is the drives to avoid any issues due to oversized log files. 
• Patches in SQL Server also play an important role when it comes to securing the database from errors during database maintenance. 

Conclusion

With the help of this write-up, we have learned about the dedicated SQL Server instance failed SCCM issue in the database. We have discussed some of the challenges database administrators might encounter, along with the common reasons that might lead to the error. To repair the issue in a secure way, it becomes important to go with a trusted solution. Lastly, we have listed some of the best ways to help users resolve the issue in quickly. 

The post Dedicated SQL Server Instance Failed SCCM – Explained & Fixed appeared first on SysTools Software.

Here you will look at the differences between HTML and plain text emails and also help you choose the right format for every communication scenario. It does so by explaining when each format works best and how to manage them in Microsoft Outlook, Gmail and marketing platforms. 

Understanding the Basics: HTML vs Plain Text Email Formatting

HTML and plain text emails represent two different philosophies in digital communication.

HTML (HyperText Markup Language): This language allows its users to use colours, images and buttons. It prioritises the use of representation, so when you see a beautiful newsletter from your favourite brand, it’s because of HTML.

Plain Text: It is raw text which contains no bolding, no images and no buttons only URLs. It is prefered it as it feels personal and loads quickly.

Difference Between HTML and Plain Text Email Formatting

1. Visual Impact and Branding: HTML allows you to give life to the visual with logos and colours, while plain text emails are very limited to specific character set.
2. Delivery and Security: Many users prefer plain text for high-security environments as it does not contain anything dangerous, while HTML can hide dangerous elements from the spam filters.
3. Engagement and Tracking: HTML is your only real choice if you want to track opens and clicks. HTML uses tracking pixels to report data and you cannot do this with basic plain text.
4. Device Compatibility: Plain text emails are compatible with all devices but the compatibility in HTML may break if images are broken.
5. Loading Speed: In HTML the loading speed is slow due to images and styling but the speed in plain text emails is instant.
6.  Best Use Case: HTML is best suited for marketing, promotions and newsletters, while plain text emails are better for personal emails, alerts and compliance.

Now that we have seen the difference between HTML and plain text emails, let’s have a look at how to set up these two in popular email clients.

Choose HTML or Plain Text Email in Microsoft Outlook

Managing the HTML or plain text emails in Microsoft Outlook settings is a daily task for many users.

1. Open Microsoft Outlook, go to File and then to Options.
2. Select the Mail option from the left sidebar.
3. Under Compose Messages choose your preferred HTML or plain text email format from the dropdown menu.
4. In order to change the HTML or plain text email formatting for a single message you can go to the Format Text tab while composing and select your desired style.

Managing the HTML or plain text email Microsoft Outlook preferences ensures that your receivers see what you intended.

Note: For Microsoft Outlook users SysTools provides an Outlook recovery tool to help them get back deleted PST files.

Choose HTML or Plain Text Email Formatting in Gmail

In Gmail you can switch between HTML and plain text email formats because it handles these formats with ease. Look at the steps below to understand how it does so:

1. Click on the Compose button.
2. In the bottom right corner of the window click the three dots for more options.
3. Check or uncheck the plain text mode as this allows you to switch between HTML and plain text email instantly.

Note: For Gmail users SysTools provides Gmail backup software to securely back up data and prevent loss. 

Choose HTML or Plain Text Emails for Marketing Platforms

Many marketing platforms such as Mailchimp and HubSpot allow you to send a multi-part messages, meaning that the system can send both HTML and plain text emails, but the receiver’s device defaults to plain text if it cannot process the HTML.

Which One Should You Choose?

HTML is best suited for sales newsletters, product announcements and brand awareness campaigns where the HTML stands out visually.

Plain Text Email Formatting is best for a 1-on-1 outreach, technical support and critical security alerts where the plain text should be readable. 

Conclusion

The choice between HTML vs plain text emails is not easy because the right choice depends on your audience and communication goals. HTML is great for marketing campaigns where visual representation and tracking matter. On the other hand plain text email formatting is better for personal communication and technical support.

If you know the strengths and weaknesses of HTML vs plain text emails, you can ensure that your emails remain easy to read and safe. Choosing the right email format helps in improving the user experience and building trust. If you want to know how to export emails of Outlook PST to HTML, you can try this.

The post HTML vs Plain Text Email Formatting Which is Better appeared first on SysTools Software.

So, without any further delay, let’s begin by understanding why the end of life of SQL Server 2016 was announced. 

Understanding SQL Server 2016 End Of Life Announcement

To understand the concept more concisely, let’s first understand what end-of-life means. When a product reaches the end of its official lifecycle, the software and IT officials call it the end-of-life for that specific product. Similarly, when SQL Server 2016 reached the end of its official lifecycle, Microsoft announced the SQL 2016 eol.  

Microsoft offers two types of support in the complete lifecycle for all its products. These supports are as follows:

The Mainstream Support:
This support mainly has a life of 5 years, and the following services are offered within that period:

• Fixes for Bugs
• Security Patch
• No-Cost Support
• Improved Features
• Compatibility and Design Upgrades

The Extended Support:
After the mainstream support ends, the extended support is offered for the next 5 years before the SQL Server 2016 end of life. The extended support includes the following services:

• The Security Updates
• Paid Support Contracts
• No Upgraded Features

After this support ends its tenure, the product officially reaches its end-of-life. This means that after this time, Microsoft will no longer offer any support or upgrades to that specific version or product, in this case, that is SQL Server 2016. When both these time period ends, there are various services and support that end by Microsoft. Here are some of these services that are stopped completely after the SQL Server 2016 end of support:

• Security Updates have been completely stopped by Microsoft.
• The product officially turns out of support. This means no more services or guidance is provided to the SQL 2016 version.
•  If the database is still running in production, there are risks of compliance and security.

Now, we will take a look at what the important takeaways are from this announcement, and what the necessary measures are to take after the complete stoppage of the product. 

What To Do After the SQL 2016: End Of Life? 

After the SQL Server 2016 end of life, there will be certain changes that might hugely impact the users’ performance and further create issues for the database administrators, if they do not take the necessary steps. Let’s first take a look at the services that will be completely stopped after the SQL Server 2016 end of support:

• Once the extended support offered by Microsoft ends for this version, the security patches will not be provided for any new issues or vulnerabilities in the SQL Server database. 
• Next, the performance improvements and any kind of bug fixes will not be offered for the version. 
• Microsoft will completely cease any support offered to SQL Server Version 2016. 
• Any updates that help the SQL Server to be compatible with any new Windows version or hardware will also be stopped after SQL Server 2016 End of Life. 

For all these reasons, the database can result in degraded performance and become vulnerable to new errors and bugs. This can lead to bigger issues in the databases, risking data security and integrity. Let’s now learn the ways and the methods that will help the users and the database administrators to deal with the SQL 2016 EOL. 

Important Dates Concerning SQL 2016 End of Life 

• Release Date of SQL Server 2016: 1 June 2016
• Mainstream Support End for SQL 2016: 13 July 2021
• SQL Server 2016 End of Life Extended Support: 14 July 2026 

Best Practices To Avoid Disasters After SQL Server 2016: EOL

As we all know that after the SQL Server 2016 End of Life, the services for the SQL Server version will be entirely stopped. We will now take a look at the preventive measures and the necessary steps to keep the data safe after the version goes outdated. 

Document the Entire Workload of SQL Server 2016

• The first precautionary measure is to document everything about the server. Note all the servers running SQL Server 2016 version. 
• Also, list all the databases and the applications relying on the SQL 2016 version servers. 
• Check the complete resource usage and do a thorough compatibility check, and dependency check. 
• SQL Server Management Studio and Data Migration Assistant are the tools that can help you with assessing and documenting the required data. 

Next, it is required to upgrade the database from the outdated version to a newer version to minimize the risk of data loss and data security after the extended support ends. For this, we will now consider the following measures for a safer and secure server migration. 

Upgrade the Server After SQL Server 2016 End Of Life

To reduce the risk of data loss or other security risks after the SQL 2016 EOL, it is advised to upgrade the server to a newer version like SQL Server 2019, SQL Server 2022, or SQL Server 2025. 

There are certain benefits of upgrading to SQL Server 2019 or 2022, and SQL Server 2025 after SQL 2016 end of life, and one of them is that Microsoft supports these versions and will continue to do so till 2030(SQL Server 2022) and 2033(SQL Server 2022), respectively. Similarly, when we take a look at the end of the lifecycle of SQL 2025, it goes on till January 6, 2031 for mainstream support and January 6, 2036 for extended support. Additionally, both these versions support better security features and improved performance. 

It is recommended by the experts to copy SQL Server from one server to another. This will help the database administrators to benefit from the advanced features provided by Microsoft in newer versions to deal with SQL Server 2016 end of life. 

Migrate from SQL Server 2016 to Azure SQL(Cloud Database)

As we all know that moving from on-premise server to cloud server is beneficial for SQL 2016 EOL as it offers numerous features. Here are some of these features that have been proven to be advantageous for the users. 

• No requirement for managing hardware as the complete server is available on the cloud. 
• The Cloud SQL offers automated backups, patching, and updates, making it hassle-free for the users. 
• The cloud-based servers also offer enhanced security features, ensuring that the data is secure from any unauthorized access and malicious activities. 
• The Azure SQL also offers improved performance tuning features that help with better performance optimization and better resource consumption. 

These are the benefits offered by the Azure SQL Database. In case the users wonder whether they should switch after SQL Server 2016 End of Life, they can consider these aspects as well. Now, migration or upgradation to a new server is a helpful solution in this situation. However, when it comes to execution, it is certainly necessary for the users to first test the SQL Server Environment to avoid any kind of issues. 

Also Read: How to migrate from SQL Server to MySQL database for easy accessibility?

Testing & Monitoring of the New SQL Server Environment

Before beginning with the migration or upgradation, it is necessary to follow certain steps to ensure that the data remains intact during the process. These steps will help the users ensure data safety and smooth execution of the complete process. Additionally, the users must take the following measures for efficient migration for the SQL Server 2016 End of Life:

• The first step is to choose a non-production environment so that the workflow on the original database remains smooth. 
• Next, it is also important to check the following things before starting the migration process:
  • Application Compatibility
  • Query Performance
  • Security Configurations
  • Backup and Restore Functions

Checking these aspects is necessary before migrating to another server to ensure there are no compatibility issues or database performance degradation during or after the process. 

Following these steps, it helps the database administrators to understand the requirements and challenges after the SQL 2016 EOL. Also, it allows them to take appropriate actions regarding the same. This is how the users can safeguard their data from any harm or damage once the server version completes its lifecycle. 

Conclusion

In this write-up, we have learned the concept of SQL Server 2016 End of Life support. We also discussed what end-of-life meant and how it could impact the users’ day-to-day tasks. Afterwards, we learned the ways that would help the users to safeguard their data before SQL Server 2016 eol or after SQL 2016 goes completely outdated.

The post A Complete Guide to SQL Server 2016 End Of Life Support appeared first on SysTools Software.

Duplicate contacts in Outlook can cause chaos and clutter your address book, which can be confusing while emailing, resulting in a waste of both time & effort. These duplicates may occur due to a sync error, import, or simply adding the contact a second time. Regardless of the cause, you need to know how to merge contacts on Outlook into one single contact via a reliable & effective tool.

Let’s discuss them quickly:

Method 1: Use Outlook’s Built-in Merge Feature

This method allows users to merge duplicate Outlook contacts manually by combining their information.
Steps to use:

1. Open Contacts tab in Outlook.
2. Select all Duplicate contacts.
3. Open one of the contacts and drag the duplicate onto it.
4. Outlook will ask if you want to merge the contact details.

Pro Tip: You can also take an action like if you want to delete the merged duplicate contacts, you should use SysTools Outlook Duplicate Remover which can help to identify and remove duplicate contacts in outlook‘s list.

Method 2: Export, Clean, and Re-import Contacts

This is a more technical way to manually merge contacts in Outlook using Excel.
Steps to use:

1. Navigate to File > Open & Export > Import/Export.
2. Export your contacts to a CSV file.
3. Open the .csv file in Excel and either manually merge duplicate rows.
4. Save the file, and re-import it to your Outlook contacts.

Pro Tip: If you want to export your contacts to gather email addresses for list building, migration, or backup, this article will help you to extract email addresses from Outlook easily.

Method 3: Merge Contacts Using the People Pane

The People Pane is another way to merge Outlook contacts.
Steps to use:

1. Open an email from the contact.
2. In the People Pane, click on Contact’s name.
3. If there are duplicates, Outlook may display linked contacts that can be merged.

Note: As these manual methods have their limitations, to prevent these consequences to merge Outlook contacts. You should opt for the automatic method to save time and avoid the risk of loss of data.

How to Merge Contacts in Outlook: Step-by-Step

1. Download and launch the software on your device.



2. Click on Add File & Folder option to add a PST file.



3. Press Next, then select Merge tab.



4. Choose Merge in New PST, an Existing File or an Outlook Profile option.



5. In Select Item Types, select Contacts for Outlook combine contacts.



6. Tick the Skip Duplicate Items checkbox and save Specific Criteria.



7. Click OK to combine contacts in Outlook PST file successfully.

Read Also: How to Merge Calendars in Outlook?

Conclusion

In this article, we’ve discussed how Outlook merge duplicate contacts with both manual and automatic methods effectively. For large-sized data, which is experiencing ongoing synchronization issues, we would suggest that you go for the aforementioned tool rather than manual methods, as it can do its work very easily, quickly, and safely. Keep your Outlook address book clean for effective performance and communication as well.

The post How to Merge Duplicate Contacts in Outlook Quickly? appeared first on SysTools Software.

Along with that, you’ll learn the default size limits for each Outlook version and how to safely modify the registry entries (MaxFileSize, WarnFileSize, etc.) to expand the capacity of your Outlook data files without any data loss, other manual techniques, or drawbacks.

There are various cases when you need to increase Outlook data file size limit beyond the default size available. If you receive lots of emails a day with larger attachments, it can result in size limit issues. Here in this blog, you can see the complete process one by one.

Let’s understand the file size of Outlook data files according to versions for better understanding:

• Outlook 2002 & earlier – 2 GB (ANSI – Cannot be increased)
• Outlook 2003–2007 – 20 GB (UNICODE – Maximum 50 GB)
• Outlook 2010–2021 – 50 GB (UNICODE – Maximum 50 GB)
• Microsoft 365 – 50 GB (UNICODE – Maximum 50 GB)

Can You Really Increase Outlook Data File Size?

Yes, you can increase outlook pst size limit within Microsoft’s allowed range. Microsoft allow users to increase the maximum size of PST and OST files by modifying Windows Registry values and other methods. But these techniques don’t improve Outlook performance and contains high risk of corruption. You can use automatic tools according to your reequipments. These are the techniques to increase Outlook PST size limit:

• Windows Registry Editor
• Archive Old Emails
• Divide Data Files
• Compact Outlook Data File
• Change “Mail to Keep Offline” Setting
• Delete & Rebuild OST File

Method 1: Windows Registry Editor to Increase Mailbox Size

This is the perfect method to increase Outlook data file size just by changing the registry. Follow the mentioned steps one by one:

Important Note: Microsoft doesn’t support to increase Outlook PST size limit using the Registry, because it contains a high risk of corruption.

These are the four registry entries that allow you to limit the size of Outlook .PST and .OST files:

• MaxFileSize registry entry – It determines an absolute maximum size for .PST and .OST files, up to which they can grow. The Outlook does not permit the size of the data file to grow beyond this maximum size.
• WarnFileSize Registry Entry: It determines the maximum data an Outlook data file can have. When this maximum data is reached, the Outlook .PST or.OST files are not permitted to add any more data. But there can be an increase in the physical file size because of internal processes.
• MaxLargeFileSize Registry Entry: To set the maximum size up to which an Outlook data file can be expanded (only for UNICODE files).
• WarnLargeFileSize Registry Entry: To set the maximum allowable data for Outlook data (PST / OST) file (only for UNICODE files).

Important: Incorrect registry changes may cause system instability. Make sure you have a backup copy of your data file before proceeding to increase Outlook data file size.

1. Choose “Windows + R” and type “regedit” and hit the “Enter” button.
2. Now, find the Outlook version key:
   HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\PST
   (Replace 16.0 with your Outlook version)
3. Right-click on the >> New >> DWORD (32-bit) Value.

   

4. Next, create these entries:

   Outlook Version	Policy location for registry entries in Registry Editor
   MaxLargeFileSize	Maximum PST/OST size
   WarnLargeFileSize	Warning threshold

5. Now, set the values in Decimal (MB):
6. And finally, restart your Outlook account.

Method 2: Divide Large Data Files

If your Outlook mailbox is full and contains your crucial data. In simple words, you don’t want to lose any data, so use the SysTools PST Splitter Tool. This software allows users to split PST file into smaller parts of MB, GB, and TB. It’s the best option to increase Outlook PST size limit without removing or deleting any data. Also, there is no risk of corruption and data loss, because it keeps your data separate and managed. Download the free edition now:

Download Now Purchase Now

How to Increase PST File Size?

1. Download and run the solution.

   

2. Add your files/folders using the given options.

   

3. Select the location to save the file using the Browse icon.

   

4. Choose Options as per choice.

   

5. Protect your data file and choose the Split icon.

   

Method 3: Increase Outlook Data File Size by Archiving

If your goal is to manage and organize your data, then archiving would be the best option for you. You can archive and keep your crucial emails and data safe for future access:

1. Head to the “File” tab in Outlook.
2. Choose “Tools” >> “Clean Up Old Items” options.
3. Select a folder that you want to archive.
4. Select any date according to your requirement.
5. After that, choose location and save the archive PST file.
6. Finally, select the OK button to increase Outlook data file size.

Method 4: Compact PST/OST Data Files

Compacting Outlook data files means it removes the extra space from the PST/OST data files.

1. Open your Outlook account.
2. Choose the “File” >> “Account Settings” > “Data Files” options.
3. After that, select the “PST/OST” file.
4. Choose the “Settings” >> “Compact Now” options.

Method 5: Increase OST File Size by Changing “Mail to Keep Offline”

This technique helps to reduce OST file size, especially for Microsoft 365 and Exchange users.

Important Note: This method only downloads recent emails instead of the full mailbox.

1. Choose the “File” tab in Outlook.
2. Choose the “Account Settings” option.
3. Select the “Exchange/Microsoft 365” account.
4. Hit the “Change” icon.
5. Adjust the “Mail to Keep Offline slider” (e.g., 6 months).
6. Now restart your Outlook to increase Outlook data file size.

Method 6: Delete and Rebuild OST File

1. First, close your Outlook completely.
2. Choose the OST file location.
3. Delete or rename the OST file.
4. Restart your Outlook account.
5. And finally, Outlook will create a new OST file automatically.

How to Increase Outlook PST Size Limit?

1. Download and start on your system.

   

2. Add your data files and folders.

   

3. Choose between “Within Folder(s)” and “Across Folder(s)” options.

   

4. Select the folders according to your needs.

   

5. Choose the “Filters” as per your choice.

   

6. Choose “Data Range” to export selective data.

   

7. After that, select the “Action” as needed.

   

8. Finally, select the “Next” and “OK” buttons.

   

Let’s Conclude

If you frequently deal with large mailboxes, increasing the Outlook PST file size limit through registry modification, archiving old emails, dividing data files, compact Outlook data file, change “Mail to Keep Offline” setting, and delete & rebuild OST file are the best techniques.

You can use an automated solution as well to divide your large data files and remove duplicate emails according to your needs. You can select any technique as per your requirements. For any query, you can contact us through chat support.

The post How to Increase Outlook Data File Size Limit (PST & OST)? appeared first on SysTools Software.

Zoho Mail is a popular webmail service that offers clean and ads-free services to its users. It can easily manage email messages, attachments, calendars, contacts, and more. Zoho is designed for businesses as well and it offers personal email accounts for free. It offers 5 GB of storage for a single Zoho mail account.

User Query: Zoho Cannot Print Mail

“I’ve been using Zoho Mail for a long time and I find it very helpful. I always used to print emails using Print Preview and Print, but now when I click Print Preview for a few days it pops up a blank new window and I can’t print emails. Please guide me on how can I fix it and print an email in Zoho.”

“I’m new to Zoho Mail and I’m having trouble printing pictures in email. I’ve tried printing from different computers and browsers and I’ve tried every possible setting I could find in Zoho Mail. And I still can’t print pictures in email. Has anyone seen this problem before? Does anyone have a solution for this problem? please help”

How to Fix Zoho Mail Not Printing Emails Issue?

Zoho provides an option to its users to easily print emails one by one by clicking on the Print option. But when Zoho cannot print mail and you want to print multiple Zoho emails at the same time, you can use the SysTools Zoho backup tool. This is an expert-recommended tool that helps you to export Zoho emails to PDF with attachments. Once you have saved the email in PDF file format, you can easily print and open it in any browser.

Download Now Purchase Now

The software enables you to print emails from single and Zoho small business accounts. With this tool, you can select emails from all folders or select a folder for saving in a PDF file. It supports saving multiple Zoho emails to PDF files in a single attempt. Now, let’s look at the steps for the same.

Steps to Export Zoho Mail to PDF 

Follow these simple steps to save emails in PDF and fix Zoho Mail not printing emails:

• Step 1. Download and run the Zoho Mail Backup Tool.
• Step 2. Enter Zoho Mail Account Credentials and log in.
  
• Step 3. Select PDF as saving file format.
  
• Step 4. Click Browse and select a location to store the output.
  
• Step 5. Select email folders and click the Start button.
  

Done! This is the best and most successful way to fix Zoho’s print mail issue and save emails in PDF files. Now, let’s look briefly at PDF file format and what are the benefits of Adobe PDF files.

Advantages of Adobe PDF File

• A PDF file is a portable format that is completely safe & secure
• It can be easily opened and viewed in any browser like Chrome, Internet Explorer, etc.
• Users can easily print PDF files with all images at any time using the printer
• A PDF file is easily shareable with someone without any size issue
• It is easy to open devices including computers, mobile phones, etc.

What’s More in Zoho Email Backup Tool?

The software comes with multiple features some of which are mentioned below:

• It offers a user-friendly interface that can be accessible by any beginner
• Able to resolve fix Zoho Mail not printing emails issue by exporting emails in PDF file
• Saves attachments associated with Zoho emails without any error
• Maintains metadata properties and folder structure of Zoho emails
• Option to delete exported emails from the Zoho server
• Works with all versions of Windows including Windows 10 version
• Supports exporting emails from Zoho to PST, MBOX, EML and MSG
• Users can easily do Zoho to Gmail migration using the PST file format

So There You Have It

Zoho cannot print mail is a common problem for users and they are looking for a solution to fix it. In the blog above, we have discussed the best solution to resolve Zoho Mail not printing emails. Here we suggested the Zoho email backup tool that allows you to save Zoho emails as PDF files so that you can print mail with ease.

The post Here’s What To Do If Zoho Mail Not Printing Emails appeared first on SysTools Software.

Mac Outlook is a personal information manager available as a part of the Microsoft Office suite for Mac. However, it is mainly used as an email client, which includes a calendar, task manager, contact manager, note, journal, and web browsing. At certain times, the user wants to migrate from Mac Outlook to Gmail. As everyone knows, Gmail is the most popular web-based email program used to access email from anywhere through the internet. Thus, a large number of desktop email client users keep a copy of messages in webmail.

Therefore, in this blog, we are going to discuss a step-by-step method to let users understand how to move mail from Mac Outlook to Gmail account in a clear way. Before that let us consider the following scenario which can help to perform data migration from Outlook for Mac to Gmail, which is taken from a forum site.

User Query

“I have been using Outlook for Mac from the past few weeks. Still, I have decided to import my emails from Mac Outlook to Gmail account. I have searched too many ways, but I was unable to find a relevant solution for the same. So, anyone can suggest me a suitable method to export Outlook For Mac to Gmail. Thanks in advance!!”

Manual Steps to Migrate Emails From Outlook For Mac to Gmail

Go through the following steps that will help to import emails from Outlook 2016 For Mac to your Gmail account. Some of them are listed below:

1.  First, you have to configure both the Gmail account and the account you wish to transfer mail from
2. After that, click the Inbox of an account you would like to copy email from.
3. Select all emails by either clicking on Select All from the Edit drop-down menu or by using the Ctrl+ A shortcut key.
4. Now, you can drag all items into Gmail Inbox.
5. The export process will take some time based on the amount of email that is being migrated.
6. Last, you can remove all items from an existing mail account by deleting the option

Drawbacks of the Manual Approach

While using the manual solution, make sure that users have migrated all emails to their Gmail accounts in a precise manner. If the above-stated method is not successful, then users can move their emails using a third-party tool. Some of the disadvantages of the manual method are:

1. Manual migration of Outlook For Mac to Gmail account is very complicated and users require a good knowledge about what they are trying to do.
2. When converting emails from Mac Outlook to a Gmail account, this manual approach does assure data integrity.
3. Users cannot perform the above method without an installation of Mac Outlook.

Expert Way to Export Emails Outlook For Mac to Gmail

As we can see there are several limitations that a user might face while configuring Mac Outlook to Gmail manually. If you are looking for some alternative solution, then it is suggested to go for a professional solution. Now, there are large numbers of applications, and choosing the best from the rest is always a tough decision for a new user. To make this task somewhat easy for the user, the OLM to Gmail Converter tool is suggested here.

Download Now Purchase Now

It is one of the simplest and most reliable applications to migrate from Mac Outlook to Gmail in a seamless manner. In addition, a user is allowed to export multiple OLM files to a Gmail account at once via the Add Folder option. It keeps the integrity of data intact as the original even after the migration process. The software is designed in a manner that supports Outlook 2011 and 2016 both without any hassle.

Prerequisites for Exporting Mac Outlook Emails to Gmail

If you already have an OLM file, then it is great. Directly, move to the tool and begin the migration process.

If not, then you need to extract the OLM file first from Mac Outlook. Now, to do the same, follow the steps mentioned below:

1 Go to the File option from the top menu bar of Mac Outlook and choose the Export option

2. Now, time to choose your Export options:

For Mac Outlook 2016

• If you want to export selective data from Mac Outlook, check the items from the Category option and take the help of the drop-down menu to choose the category
• To export everything from Outlook, select the Items of these types: option and check the types of items that you want to migrate

• After that, Click Continue when ready and move to Step 3 below.

For Mac Outlook 2011

• First of all, choose Outlook for Mac (olm) data file option
• Now, again to export selective data items in an OLM file, you can check the desired items in the Category option and take the help of the drop-down menu for the same
• To migrate everything from Mac Outlook, select the Items of the following types: option and check the types of items you want to export

• After that, click on the right arrow from the bottom right corner of the window to proceed further
• Then, you can check or uncheck the Delete After Exporting. window and again click on the right arrow from the bottom

3. Then, you need to choose the destination location to save the exported OLM file on the local machine and give a name to the file in the “Save as:” section

4. After that, Mac Outlook will begin the export process

5. When the Export Complete message appears on the screen, click on the Finish or Done to complete the process.

After this, you have a Mac Outlook OLM file on the local machine. Now, you can easily take the help of the suggested automated converter to migrate from Mac Outlook to Gmail seamlessly.

So There You Have It

After considering the ongoing necessity to migrate from Outlook for Mac to Gmail, we have described a manual procedure to let the users understand how to export from Mac Outlook to a Google Mail account. Otherwise, users can choose a reliable OLM to Gmail Converter that makes it easy to move data. Furthermore, we have discussed some extraordinary features of the tool in an absolute way.

The post Here’s How to Migrate from Mac Outlook to Gmail Account appeared first on SysTools Software.

If you have ever tried copying files on your Windows PC and felt frustrated watching the progress bar crawl along or even worse, freeze completely well you are not alone. This is the problem many of you are facing even on modern systems with SSDs and fast processors.

Here slow file transfer speed remains one of the major complaints. From Windows 7 to Windows 10 and Windows 11 if you are moving your files to a USB drive, transferring data between disks, or backing up your important files or folders you will feel unpredictable, slow, and inconsistent while transferring your Windows files.

How Windows Copies Files

Before we start fixing the problem it is important to understand how Windows file copy works.

When you start to copy your file Windows doesn’t directly move data from one place to another. However It performs several steps you can check below:

1. It reads data from the source drive,
2. stores it in system memory (cache) for a short time,
3. writes it to the destination drive,
4. verifies the data integrity,
5. and updates the file metadata and permissions.

Here you may still think why is my file transfer speed so slow even though I have a powerful PC? Here you need to understand that the process happens repeatedly and file by file. The more complex the transfer including (multiple files, slow drives, USB devices) the higher chances of delays.

Why Does Copying Files Take So Long on Windows?

As a data recovery expert I haven’t seen a single cause but there are multiple factors combined to slow things down on Windows.

1. Storage Device Speed Limits

Let me tell you, not all storage devices are equal.

If you are trying to copy files from an SSD to a USB flash drive, the USB device becomes the bottleneck. This is one of the major reasons why file transfers are slow in Windows especially when you are copying to external drives.

2. Why File Transfer Speed Goes Up and Down

If you ever notice that file transfer speed starts fast and then suddenly it slows down or start fluctuation well there are the multiple reasons behind this:

• initially used RAM cache by Windows (fast burst)
• The cache fills up
• The system waits for the destination drive to catch up
• Thermal throttling reduces speed
• Background processes interrupt I/O

Because of these reasons your file transfer speed goes up and down instead of staying consistent.

3. Why Do Small Files Take Longer to Copy?

This is one of the most confusing behaviors that small files often take longer to copy than large files. If you have ever experienced sometimes:

• Copying a single 10 GB video file might be completed quickly.
• Copying 10,000 photos (each 2 MB) might take longer.

Have you ever wondered why this happens?

This must be making you quite curious about why and how this often happens? Well this all happens because each file requires:

• File system checks
• Metadata creation
• Antivirus scanning
• Permission validation

You must have now understood why small files take longer to copy, and what is going on in the background of your system when you copy a file from one drive to another.

Windows Version – Specific File Transfer Issues

Windows 11 File Transfer Speed is Slow

Windows 11: Why does copying files take so long? You will find these features are introduced in desktop operating system windows 11:

• Improved security layers
• Virtualization-based security
• Updated Explorer UI

While these features enhance security, they can slow down disk operations. This is why many of you are asking why copying files takes so long in Windows 11, especially on older hardware.

Windows 10 File Transfer Speed Slow

The common reasons you encounter in Windows 10 are something like this:

• USB power management throttling
• Background Windows Update services
• Explorer bugs affecting large transfers

As a result, users often report slow file transfer speeds in Windows 10, especially when copying files to USB drives.

Slow File Transfer on Windows 7

Compared to other current desktop operating systems, Windows 7 severely lacks modern optimizations, especially for SSDs and USB 3.0 devices.

• Large file handling
• High-speed external drives
• Modern file systems

This highlights and explains ongoing complaints about the slow file transfer in Windows 7.

When File Transfer Speed Drops to 0 Bytes

Few things are more serious than seeing file transfer speed 0 bytes while your copy operation. This usually indicates:

• Bad sectors on the source drive
• File system corruption
• USB connection instability
• Drive firmware issues

At this time, forcing the transfer could lead to further problems. If the transfer repeatedly stalls at 0 bytes, it often indicates a larger storage issue, not just a slow Windows system.

Windows 10 Slow Copying Files to USB

Have you ever wondered why this happens? USB transfers are quite problematic, and the main reasons for this are:

• Many flash drives have low-quality controllers.
• USB power saving settings reduce performance.
• FAT32 or exFAT file systems behave differently.
• Cheap USB cables reduce speed.

This is why slow file copying to USB drives in Windows 10 is one of the most frequently searched issues.

Why Windows Slows Down When Copying Large Files

Windows Explorer focuses more on security over speed so when you copy large and heavy files, it depends completely on system caching and write verification. First the data is stored in RAM and then it is written to the disk in batches.

Windows pauses the transfer to flush the data once cache fills up which slows down the speed and it drops to 0 bytes per second for a short period.

Another major drawback is single-threaded processing. Windows Explorer copies large files one by one instead of utilizing parallel operations. I have noticed that the modern SSDs and USB 3.x devices support multiple simultaneous writes, but the thing is explorer doesn’t fully utilize this capability so the output will be slower transfer speeds.

As Windows has continuous integrity checks during this process of file copying which helps prevent data corruption adding extra overhead especially for those files larger than 10 to 20 Gigabyte.

Combination of this sequential processing caching limitations, and the verification overhead explains why Windows file copying struggles with some large files, even if you have high performing systems.
Performance comparison

Quick Fixes to Improve File Transfer Speed

What should be our immediate course of action that is safe for everyone to improve file transfer speed, and make the transfer stable?
Immediate Actions

• Stop and restart the transfer.
• Close background apps.
• Temporarily disable your antivirus.
• Use different USB ports or cables.

System Level Tweaks

• Enable write caching for the external drive.
• Disable USB selective suspend.
• Use NTFS instead of FAT32 for large files.

These steps equally reduce slow file transfer speeds in many cases.

What Works Better Than Windows’ Built-In File Copy

Windows Explorer is not always the best option. For critical or challenging transfers you can try with some better alternatives that includes:

• Command-line copy tools with improved buffering
• Dedicated transfer utilities with error handling
• Copying in smaller batches instead of one large operation

As these methods often provide more stable performance and fewer interruptions compared to the standard Explorer copy operation.

Practical Situations Where File Transfers Slow Down

Moving your Data from Old HDD to New SSD

The important thing to understand here is slow transfer. It is common because the hard drive limits the read speed. Suppose if the drive has bad sectors or missing files, users often resort to HDD recovery solutions before attempting another transfer.

Copying Backups to External Drives

Differences in USB versions and file system errors can cause a sudden decrease in speed or even stop the copying process.

Transferring Media Libraries

Thousands of small files create metadata overhead which significantly slows down the file copying process.

When Slow File Transfer Signals a Bigger Problem

If your file transfers are always slow, then this points to the deeper issues like:

• Failing hard drive
• Corrupt file system
• Bad sectors
• USB controller degradation

If you find your file transfer is always unreliable it is not a Windows issue alone it’s simply a storage health warning situation.

Final Thoughts

Why does copying files take so long and what should you do in this critical case? If the copy files are very slow or unreliable it is basically a combination of hardware limitation, structure of the files, and most importantly your system behavior. File transfers depend on:

• Speed of the Storage device
• Structure of the File
• Windows version behavior
• Background processes
• Health of Hardware

First Identifying the bottlenecks and after choosing the right yet reliable solutions. By understanding these common reasons, you can minimize errors and make more informed decisions when transferring your important data.

The post Why Does Copying Files Take So Long on Windows? appeared first on SysTools Software.