| At times, when you are updating your existing | | | | downtime but also gives you enough testing time |
| SharePoint installation to a faster and more | | | | to successfully complete your update and test all |
| secure SharePoint 2010, you may face different | | | | possible scenarios. |
| upgrade scenarios that can affect the overall | | | | Forms-Based Authentication Environment |
| update process. Blow is a list of the major special | | | | After migration your SharePoint 2007 to |
| case scenarios that you must look into before | | | | SharePoint 2010; your authentication method is |
| performing an in-place or database-attach upgrade. | | | | automatically converted to legacy or Windows |
| These include but are not limited to: | | | | Login-based authentication. If your SharePoint is |
| SQL Server 32 Bit - 64 Bit | | | | already using Windows-Based authentication, the |
| As a prerequisite of SharePoint 2010 server, you | | | | no further changes are required and your web |
| must have your databases transferred to a | | | | applications will work fine. However, if your web |
| 64-bit version of SQL Server. It is recommended | | | | applications are using Web SSO based or |
| that you perform your SQL server migration | | | | form-based authentication, you may need to |
| before you begin the SharePoint update process. | | | | make additional configuration changes to make |
| This approach has certain benefits including | | | | this work. |
| performance and fault-tolerance. You have two | | | | In order to use your SharePoint 2007 based web |
| options available to migrate your database server. | | | | applications in SharePoint 2010, you must first |
| You can perform a full backup on your existing | | | | convert to claims-based authentication. Once you |
| database which will copy your entire database | | | | have converted to claims-based authentication, |
| that you can restore later. Apart from being a | | | | web application zones should be configured to |
| recommended and fail-safe method, you do not | | | | web SSEO or form-based authentication. You can |
| have to perform any manual operations on the | | | | finalize the process by migrating users and |
| Share Point 2010 server except run the restore | | | | permissions from the Share Point 2007 server. |
| procedure. | | | | Large Databases |
| You can also move your new database to a new | | | | As a general rule of thumb, larger database with |
| SQL Server 64-bit installation. In this option, you | | | | tens of gigabytes of data take longer to migrate. |
| must first add a new 64-bit version of SQL | | | | However, complexity of the to-be-migrated data |
| Server and then manually point every new | | | | plays an important role in defining the overall time |
| SharePoint 2010 server to the location of new | | | | of migration. Connection problems also cause |
| SQL server. | | | | time-outs during data migration. However, these |
| 32 Bit - 64 Bit Operating System | | | | types of issues that commonly occurred in Share |
| In order to update your existing server farms | | | | Point 2007 have been fixed in SharePoint 2010. |
| running on a 32-bit version of operating system | | | | Upgrading from WSS 3.0 |
| to a 64-bit version, you must adopt a phased | | | | If you are upgrading from Windows SharePoint |
| approach. The phased approach includes adding | | | | Services 3.0, you must use a database-attach |
| the new 64-bit servers to the server farm and | | | | upgrade option to successfully migrate the |
| then removing the 32-bit servers from the farm. | | | | content databases to Share Point 2010 |
| This technique not only mitigates the service | | | | successfully. |