Upgrading SharePoint



What happens to Web Analytics after upgrade?GP0|#b20346d4-3cda-4fd2-9603-5571a7e5e2db;L0|#0b20346d4-3cda-4fd2-9603-5571a7e5e2db|Upgrade;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#1b064965-36f6-40b1-a474-78053852e564;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213The Web Analytics Service is not upgraded to the Analytics Processing Component in SharePoint 2013. When you upgrade to SharePoint 2013, the databases that contain the data from Web Analytics in SharePoint Server 2010 are not removed. These databases are not used by or maintained by the Analytics Processing Component in SharePoint 2013. This means that documents on sites in SharePoint Server 2010 that are upgraded will show a hit count of 0. When you upgrade to SharePoint 2013, do not attach and upgrade the databases that contain the data from Web Analytics in SharePoint Server 2010. We recommend that you turn off Web Analytics in the SharePoint Server 2010 environment before you copy the content databases that you want to upgrade to SharePoint 2013. Reports from Web Analytics for the top items in a site are carried forward. Reports that show browser traffic, top users of a site, and referring URL are not carried forward and are not used by the Analytics Processing Component in SharePoint 2013. Administrative reports for the quota usage of site collections in the farm are not available in SharePoint 2013. SharePoint 2013 does not support the Web Analytics Web Part. After a farm is upgraded to SharePoint 2013, all instances of a Web Analytics Web Part will not function. The page that includes the Analytics Web Part will render and a message appears that informs the user that the Web Part is no longer supported. Note. Data collection for Analytics Processing in SharePoint 2013 starts immediately for sites, including SharePoint Server 2010 sites.
Can't edit workbooks in the browser that have external data connectionsGP0|#b20346d4-3cda-4fd2-9603-5571a7e5e2db;L0|#0b20346d4-3cda-4fd2-9603-5571a7e5e2db|Upgrade;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#1b064965-36f6-40b1-a474-78053852e564;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213;GP0|#b8094c52-e86a-452d-ab36-1a0091ea9c22;L0|#0b8094c52-e86a-452d-ab36-1a0091ea9c22|Excel Services;GPP|#aa2447c2-0307-4407-bd59-fedab9e12903;GP0|#55fb27c6-9a9a-4c40-be08-4801ff88eeec;L0|#055fb27c6-9a9a-4c40-be08-4801ff88eeec|Excel Web Access;GPP|#7c66663a-64ea-4c65-9772-9b3a76b4aa65;GPP|#1bc09cbd-f411-45d5-ad40-bb6b715fb72f;GPP|#a5205c2f-ad79-446f-8d9e-afd0eeecf427 ​Workbooks with external data connections that use Windows authentication cannot be refreshed in the browser. Instead, you are prompted to open the workbook in the Excel client program. Workbooks that have database or Windows credentials stored either in the Secure Store Service or in the connection string can still be edited in the browser. This change applies only when Excel Web App in Office Web Apps Server is used to view workbooks, not when Excel Services in SharePoint Server 2013 is used. Note You can still refresh these workbooks in the Excel client program. Additionally, a service application administrator can configure that workbooks are viewed in SharePoint 2013 instead of Office Web Apps Server.