Configure a Report Service
- 2 minutes to read
To store temporary data (generated documents, files ready for export and so on), the report service uses a cache, which may be located in memory or in a database. By default, a Microsoft SQL Server database is used, but you can use any database to which it is possible to connect using XPO. To view the full list of the supported database formats, refer to the Database Systems Supported by XPO topic.
By default a report service stores its cache in a database specified by the connection string named xpf.printing:
<connectionStrings>
<add name="xpf.printing"
connectionString="xpoprovider=MSSqlServer;
data source=(localdb)\v11.0;
attachdbfilename=|DataDirectory|\ReportService.mdf;
integrated security=True;connect timeout=120" />
</connectionStrings>
If no connection string is specified, the cache is stored in memory.
The connection string examples are shown in the table below.
Relational Database System | Connection String Sample |
|---|---|
Microsoft SQL Server | XpoProvider=MSSqlServer;Data Source=(local);User ID=username;Password=password;Initial Catalog=database;Persist Security Info=true The MS SQL Server data provider is automatically specified if you set the “Initial Catalog” parameter and do not use the word “Provider” (for instance, the “XpoProvider” parameter) in the connection string. |
Microsoft Access | XpoProvider=MSAccess;Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\mydatabase.mdb;User Id=admin;Password=; XpoProvider=MSAccess;Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\mydatabase.accdb;User Id=admin;Password=; |
Microsoft SQL Server CE | XpoProvider=MSSqlServerCE;Data Source=MyDatabase.sdf;Password=MyPassword |
Oracle Database | XpoProvider=Oracle;Data Source=TORCL;User ID=MyUserName;Password=MyPassword XpoProvider=ODP;Data Source=TORCL;User ID=MyUserName;Password=MyPassword XpoProvider=ODPManaged;Data Source=TORCL;User ID=MyUserName;Password=MyPassword |
Amazon Redshift | XpoProvider=Amazon Redshift;Server=127.0.0.1;User ID=MyUserName;Password=MyPassword;Database=MyDatabase;Encoding=UNICODE |
Google BigQuery | XpoProvider=BigQuery;ProjectID=myProject;DataSetId=myDataSet;OAuthClientId=myClientId;OAuthClientSecret=mySecret;OAuthRefreshToken=myRefreshToken XpoProvider=BigQuery;ProjectId=project;DatasetId=dataset;ServiceAccountEmail=example@gmail.com;PrivateKeyFileName=key.p12 |
Teradata | XpoProvider=Teradata;Data Source=myServerAddress;User ID=myUsername;Password=myPassword; |
SAP Sybase Advantage | XpoProvider=Advantage;Data Source=\myserver\myvolume\mypat\mydd.add;ServerType=local;User ID=ASSSYS;TrimTrailingSpaces=true |
SAP Sybase ASE | XpoProvider=Ase;Port=5000;Data Source=MyAseServer;User ID=MyUserName;Password=MyPassword;Initial Catalog=MyDatabase;Persist Security Info=true |
SAP SQL Anywhere | XpoProvider=Asa;eng=server;uid=user;pwd=password;dbn=database;persist security info=true; |
IBM DB2 | XpoProvider=DB2;Server=server:port;Database=database;UID=user;PWD=password; |
Firebird | XpoProvider=Firebird;DataSource=localhost;User=SYSDBA;Password=masterkey;Database=MyDatabase.fdb;ServerType=0;Charset=NONE |
MySQL | XpoProvider=MySql;Server=MyServerAddress;User ID=MyUserName;Password=MyPassword;Database=MyDatabase;Persist Security Info= true;Charset=utf8 |
Pervasive PSQL | XpoProvider=Pervasive;Server=MyServerAddress;UID=MyUserName;PWD=MyPassword;ServerDSN=MyDatabase |
PostgreSQL | XpoProvider=Postgres;Server=127.0.0.1;User ID=MyUserName;Password=MyPassword;Database=MyDatabase;Encoding=UNICODE |
VistaDB | XpoProvider=VistaDB;Data Source=C:\mydatabase.vdb4 XpoProvider=VistaDB5;Data Source=C:\mydatabase.vdb5 |
SQLite | XpoProvider=SQLite;Data Source=filename |
XML file | XpoProvider=InMemoryDataStore;data source=D:\Contacts.xml;read only=True |
Note
The connection strings demonstrated above are examples. You can specify alternative variants.
The name of a connection string used to access the cache may be changed by specifying the documentStore.connectionStringName parameter in the Web.config file, or by implementing the IDocumentDataStorageProvider MEF extension (for more information, see Extend a Report Service with Custom Functionality).
It is strongly advised that you use a separate database instance for storing the report service cache. This allows you to safely delete the cache, which may be required for migrating between different versions of DevExpress controls.
Additional parameters are set in the xpf.printing configuration section (e.g., the life-cycle of the database entities in milliseconds that is defined by the keepInterval parameter).
<devExpress>
<xpf.printing>
<documentStore keepInterval="1200000" connectionStringName="xpf.printing" />
</xpf.printing>
</devExpress>
The server automatically creates the database scheme when the first connection is set up.