You have a fully integrated SQL Server 2008 R2 installation integrated with Sharepoint 2010 for both Reporting Services and Powerpivot. Upgrade to SQL 2012 gotchas out of the way.
First give the Upgrade 2012 Advisor a shot http://msdn.microsoft.com/en-us/library/ms144256(v=sql.110).aspx – I had a few issues installing however expect this to be resolved.
1. Ensure Windows 2008 R2 is on SP1
2. Ensure SQL Server 2008 R2 is on SP1
3. Sharepoint 2010 is on SP1
4. If you have multiple instances e.g. a Powerpivot Analysis Services instance as well as a regular SQL Server 2008 R2 instance, you need to run SQL 2012 setup twice, one for each instance.
5. If you are attempting an upgrade and are using Eval edition 2012 to upgrade a Dev edition 2008 R2 you are out of luck …
6. Once the upgrade is complete for both MSSQLServer and Powerpivot instances, you are just about done – surprised ? The integration improvements in SQL 2012 are impressive.
It is worth mentioning here that whilst the Reporting Services Configuration Manager remains in the SQL 2012 Configuration Program Group, this is for configuring Native mode installations only. SSRS 2012 Integrated is now exclusively managed under Sharepoint as a Service Application – hence the Reporting Services Configuration Manager is not applicable for an integrated instance. You will need to make good friends with the Sharepoint team if you havn’t already.
If you are fortunate enough to be able to administer your own server, run through Sharepoint Central Administration, go to Manage Service Applications and make sure the Sharepoint SSRS service application (and proxy) are listed.
7. You will still need to configure the Provision Subscriptions and Alerts screen to allow Reporting Services to access SQL Server Agent. Other SSRS management features managed through the Service Application include : System Settings, Manage Jobs, Key Management, Execution Account and Email Settings which will sound familiar to the screens of the Reporting Services Configuration Manager.
The level of business intelligence integration between Sharepoint 2010 and SQL 2012 is clearly the best thought out and executed to date. The biggest pain point however will be those SQL Server folk who have to go through a Sharepoint team to get these activities completed on their behalf.