Power BI Content and Feature Review

Download Report

Transcript Power BI Content and Feature Review

Scope - Goals
This is the approach we will review in detail today.
A
B
Report Server database (DB) is what exactly?
• In Native mode the DB is actually 2 SQL Server DBs.
• In SharePoint mode it is a set of 3 SQL Server DBs per SSRS Service application.
Database
Example SharePoint Name
Default Native mode name
Catalog database
ReportingService_[service application GUID]
ReportServer
Temp database
ReportingService_[service application GUID]TempDB
ReportServerTempDB
Alerting database ReportingService_[service application GUID]_Alerting
na
In SharePoint mode the content items (reports) are stored in the SharePoint content DBs….so where the items in your
document library are saved…and then there is a synchronization between the content DB and the report server catalog DB.
Full Database Backup/Restore
• Developing backup & restore plan for database files is critical to recovery strategy.
• Backup & restore is used frequently to move all or part of a Reporting Services
installation.
Database Backup (Native mode and SharePoint mode)
• Use full recovery model to backup the reportserver database.
• Use full recovery model to backup the dataalerting database (SharePoint mode only).
• Use simple recovery model to backup the reportservertempdb database.
Other Items to Backup
• Encryption Keys (*) always a good idea to backup…
• Configuration Files (different between native and SharePoint)
• Custom assemblies or extensions
• Data files
Content Migration
• The SSRS migration tool found on the download center–
•
easy to use
•
Limited scenarios
• RS Scripter
http://weblogs.asp.net/akjoshi/using-rs-scripter-to-create-deployment-script-for-reporting-services
• rs.exe scripts – more flexible and supports all scenarios. This is the tool we will review in detail
today.
What is the script?
•
from a SQL Server 2008 R2 native mode report server >>> to a SQL Server 2012 SP1 SharePoint mode report server.
B
C
A
Script Limitations – what is not copied
Database
Example SharePoint Name
Passwords
Passwords are NOT migrated. After content items are migrated, update the credential information on
the destination server. For example, data sources with stored credentials.
My Reports
The Native mode “My Reports” feature is based on individual user logins therefore the scripting
service does not have access to content in “My Reports” folders for users other than the –u parameter
used to run the rss script. Also, “My Reports” is not a feature of Reporting Services SharePoint mode
and items in the folders cannot be copied to a SharePoint environment.
Work around
• Create new folder(s) in Report Manager. Optionally, you can create folders or subfolder for each
user.
• Login as one of the users with “My Reports” content.
• Click the My Reports folder
• Move the reports to a general folder
• Repeat for each user.
• Then Run the script.
Report History
Settings migrated but not the history itself
Script output notes issues to help…
Local Native
mode server
Azure Virtual Machine running
SSRS Native mode server
rs.exe -i c:\_demo\ssrs_migration.rss
-e Mgmt2010 -s http://craigg2/ReportServer -u domain\user -p password
-v ts="http://ssrsnative.cloudapp.net/ReportServer" -v tu="testuser" -v tp=“password"
Local Native
mode server
SSRS
SharePoint
Server
rs.exe -i c:\_demo\ssrs_migration.rss -e Mgmt2010 -s http://craigg2/ReportServer -u
DOMAIN\USER -p password -v ts="http://uetestb04/sites/SSRS/_vti_bin/reportserver" -v
tst="sites/ssrs" -v tf="Shared Documents" -v tu=“DOMAIN\user" -v tp=“password"
Note the “sites”
syntax and “” for
destination servers
Local Native mode server for audit…
rs.exe -i c:\_demo\ssrs_migration.rss -e Mgmt2010 -s http://craigg2/ReportServer -u
DOMAIN\user -p password -v ts="http://craigg2/ReportServer" -v tu=“DOMAIN\user" -v
tp=“password"
Content links and resources
http://msdn.microsoft.com/en-us/library/dn531017(d=printer).aspx
http://msdn.microsoft.com/en-us/library/ms157231.aspx
http://1drv.ms/1uFIlfO
Detected SQL agent was not running
Now with SQL running
Errors because email is not configured
Now email is configured…