Learning module:07

Unit of competence: Determine Suitability of Database Functionality and Scalability

Module Title: Determining Suitability of Database Functionality and Scalability
Occupational code: ICT DBA4 07 0710

LO1: Determine database functionality

LO2: Identify scalability and functionality requirements

LO3: Prepare report

Trainees manual and information sheet for DBA

level IV
Compiled by G.k
in 12/12/2007
 Lo1: Determine database functionality
Application Note – 08/14 Database functionality in ArtemiS SUITE Application Note – 08/14 │1│
Database functionality in ArtemiS suite Do you want to spend more time on analyzing your data than on
searching for a certain file? The database functionality of ArtemiS SUITE allows for convenient
management and organization of your data and makes it easy to find specific measurements, so that
you don’t lose time searching for recordings – instead you can start your work right away! This
Application Note explains how to create a database, how to index your data and how to take advantage
of the various database functions: Creating a database and indexing data 1 Important notes 2 Database
functions 3 Search functions 3 Special features of the database search 7 Using different navigation views
7 Database maintenance and organization 12 Note 13 Creating a database and indexing data In order to
create a database, you need an ArtemiS SUITE license that includes the Basic Database Module ASM 03.
Furthermore, an SQL server1 must be installed on your computer. If the server is not yet installed2 ,
insert the ArtemiS SUITE Setup DVD into a drive, wait for the startup screen to appear and click on
Browse medium content -> Applications -> HEAD ArtemiS SUITE -> SQL Server 2008 R2. Then follow the
on-screen instructions. When installing the server, make sure that the user who is supposed to work
with the database is entered as a user during the SQL installation. After the successful installation, start
ArtemiS SUITE, go to the Database menu and select the command Create database. The further steps for
setting up the database are described in detail in the online help section „Database Creation &
Connection“. Once the new database is set up, you can index your measurement data. This means that
an index (a “table of contents”) of the selected data is created in the database, which allows convenient
and quick searching of the data, for example. To create the index, go to the HEAD Navigator and right-
click on a folder you wish to add to the database. In the context menu, select Database -> Add to
database as shown in figure 1. 1 For information on the required version, refer to the online help of the
ArtemiS SUITE (section „SQL Server installation“). 2 To check whether an SQL server is already installed
on your system and running, go to Control Panel -> Administrative Tools -> Services. Look for the service
SQL Server (SQLEXPRESS) and make sure that its status is Started and the startup type is set to
Automatic. HEAD acoustics Application Note Database functionality in ArtemiS SUITE Application Note –
08/14 │2│ Figure 1: Context menu in the HEAD Navigator Depending on the size of the selected folder,
indexing may take several minutes. Once the data are indexed in your database, you can use the
database functions described in the next section. Important notes When creating your database(s) and
indexing your data, please be aware of the following: • The database type used in ArtemiS SUITE is a
relational database, i.e. the database merely creates an index of the data and manages its
documentation. The actual data are not copied into the database. This has the advantage that the actual
database is small compared to the size of the referenced data. Furthermore, you can recreate the
database at any time from the existing data, which makes a separate backup of the database
unnecessary, thus saving storage space. This also allows every user to create his or her own database. •
Data can be indexed in multiple databases at the same time, i.e., several employees can access the same
data and add items to their personal databases. • In order to accelerate database search, for example,
every user should only add data to their database that is actually relevant for their work. • Since the
data are not stored in a closed database system, individual users maintain control of their respective
data. Therefore, all they have to do is store their data in a consistent way: then they can immediately
start applying the database functions and take advantage of the database search feature, for example.
HEAD acoustics Application Note Database functionality in ArtemiS SUITE Application Note – 08/14 │3│
Of course, it is also possible to establish a consistent department-wide or companywide data storage
scheme. However, this is not prerequisite. Each user, each department, etc. can choose the degree of
standardization, and no one is restricted in their way of working. Database functions The database
functions available in the ArtemiS SUITE include extensive search functions and the display of navigation
views. Search functions The criteria that can be used for searching a database include not only the
content of the system documentation as well as the user documentation3 , but also file properties (e.g.,
file names). Clicking on Database -> Search opens a search form (see figure 2). Figure 2: Simple search
form When opened for the first time, the search form offers the possibility to enter a search term, which
is then searched for in all text fields of the system documentation and the user documentation. With the
checkboxes below the input field, you can restrict your search to the documentation of certain
Directories, Files, File Parts (i.e. Channels). To refine your search further, click on Show more options.
The search form now offers additional search criteria (see figure 3). 3 Please see the Application Note
“User documentation” for information on how to create and work with user documentation. HEAD
acoustics Application Note Database functionality in ArtemiS SUITE Application Note – 08/14 │4│ Figure
3: Extended search form The following example shows how to search data for which comprehensive
user documentation is available. An example of a filled-in documentation template is shown on the left
side of figure 4. Besides general information about the measured car in the Car section (Manufacturer,
Model, Segment, VIN, Date of Production, and Role), the template also contains the two subforms
Engine and Test with information on Displacement, Fuel type, Cylinder layout, Power, and Turbo, as well
as Status and Drive State Gear. As soon as the data documented with such a template have been
indexed in the database, the keywords contained in the template are available for selection in the
search form. The names of the main forms as well as the subforms are displayed together in a list. Under
the respective form name, you can then select the individual field names (see figure 4). Using subforms
thus allows you to structure not only your documentation template, but also the suggestions for the
database search. This provides a better overview and helps you to fill in the search form more quickly.
HEAD acoustics Application Note Database functionality in ArtemiS SUITE Application Note – 08/14 │5│
Figure 4: Documentation template and search criteria in the search form Likewise, in the right field of
the search form, where the value to be checked must be entered, ArtemiS SUITE provides the values
indexed in the database in a selection list (see figure 5). Figure 5: Searching for a user documentation
entry Using the list items has several advantages: You avoid typing errors, and you only search for
entries actually contained in the database. If there is no user documentation for your data yet, you can
perform a database search nevertheless. In this case, you can search for the parameters of the system
documentation automatically created by the ArtemiS SUITE. The fields of the system documentation can
be found in the upper section of the list in the left field and are marked with an @. Searching the system
documentation allows you to find, for example, channels with a certain measurement unit (see figure 6).
Figure 6: Searching for system documentation entry HEAD acoustics Application Note Database
functionality in ArtemiS SUITE Application Note – 08/14 │6│ In the following, the functions of the
database search and the search interface are described in detail. In the File System section of the
extended search form, you can enter various keywords for file names, folders, and file types: • File
Name: Searches the file names. Wildcards are supported (* = any number of unknown characters, ? =
one unknown character). • Directory: Here you can restrict the search to a specific directory. The
database search will then only deliver results from this folder, including any subfolders. Clicking on the
button allows you to select the folder directly from the file system. • Type: The selection list for types
includes the data types of the system documentation (marked with an @) and the names of all forms of
the user documentation. If the search is restricted in this way, only those results are listed which match
the selected system documentation or were documented with the specified main form of the user
documentation. If a field is not filled in, all possibilities for this field are included in the results. In the
Field Search area, you can search for specific information in the user documentation and in the system
documentation. The following entries define a search criterion (from left to right): • Select field: Clicking
on this field opens a selection list showing all documentation fields stored in the database, sorted by
their forms. System documentation parameters are marked with an @. Select the criterion you want to
search for. • Operator: This specifies the method by which the entries are to be checked. Depending on
whether the criterion to be checked is a text field or a numeric field, different operators are available. •
Operators for text fields: o equals: The value must be exactly identical. o like: Upper/lower case is
ignored, and wildcards are supported (* = any number of unknown characters, ? = one unknown
character). o contains: The value searched for must be contained. o contains not: The value searched for
must not be contained. o starts with: The value searched for must be at the beginning of the text field. o
ends with: The value searched for must be at the end of the text field. • Operators for numeric fields: o
equals: = (Caution: In case of real number, it is possible that a value entered manually is not found due
to calculation inaccuracies. Select a value from the list instead.) o less than: < o less or equal: ≤ o greater
than: > o greater or equal: ≥ • Field content: Enter the field content to be searched for in the field on the
right side. You can select an entry from the selection list or type it manually. By using the list items, you
can avoid making typing errors and searching for entries not contained in the database. HEAD acoustics
Application Note Database functionality in ArtemiS SUITE Application Note – 08/14 │7│ As shown in
figure 3, two criterion fields are displayed by default. You can add more criteria via the link Add Field
Criteria or remove existing criteria by left-clicking on the left field and then on Remove Criteria. Special
features of the database search • Using subforms allows you to structure not only the documentation
template, but also the selection list in the database search. • Since every user can create their own
database indexing only the data relevant for their work, the selection lists will always show only the
relevant documentation entries. • Furthermore, it is possible for a user to create multiple databases,
each indexing only the data of a specific project, for example. This, too, reduces the size of the list and
avoids the need to navigate through an extensive list in order to find the required criterion. • As soon as
the data are indexed in a database, the information contained in the system documentation is
immediately available as search criteria, i.e. the user can benefit from the database search even without
creating user documentation. • Please note that data is not indexed automatically. To ensure that the
index reflects the current status of the files in the file system, indexing must be repeated regularly!
Using different navigation views A navigation view is a possibility to display data indexed in a database
sorted by their documented attributes (system documentation as well as user documentation) in the
HEAD Navigator. Using navigation views allows users to choose the most appropriate structure for their
purposes, without the need to move the actual data. While the file system, too, allows you to sort and
catalog data by means of a folder structure, navigation views have significant advantages: You can
create any number of navigation views for the same database. And you can add or modify search paths
at any time without the need to copy data. Furthermore, multiple users can access the same data, but
each user sees it in a customized structure optimized for their needs. In the following example, the
measurements are stored in a simple folder structure on the hard disk. The first level of subdivision are
the folders Manufacturer 1 to 5. These folders contain subfolders specifying the exhaust system (e.g.,
Exhaust_Mod). Another subdivision level specifies the gear used (e.g., 2nd Gear). Figure 7 shows the
structure in a Windows Explorer screenshot. HEAD acoustics Application Note Database functionality in
ArtemiS SUITE Application Note – 08/14 │8│ Figure 7: Data structure implemented by means of folders
in the Windows Explorer In addition to the information implied by the folder structure, the files were
also supplemented with extensive user documentation. The user documentation provides detailed
information about the car and its components, such as engine and tires, as well as information about the
test bench where the measurement was made. Figure 8 shows the user documentation of a
measurement. HEAD acoustics Application Note Database functionality in ArtemiS SUITE Application
Note – 08/14 │9│ Figure 8: User documentation (For a better overview, some subforms have been
minimized, e.g., Power Train) By means of navigation views, each user can use the information of the
user documentation to structure the data according to his or her personal needs. Figure 9 shows
examples of navigation views with different group structures. For example, an engine developer might
want to replace the structure shown in figure 7 by the structure of the navigation view Engine. In this
view, the files are subdivided by Manufacturer and Model, Fuel type, Cylinder layout and Displacement.
An employee in the exhaust systems department needs yet another structure. In our example, this user
sorts the data using the Exhaust view. This view first subdivides the files by Fuel type, Cylinder layout,
Displacement, and Type of drive, and only afterwards by Manufacturer and Model. HEAD acoustics
Application Note Database functionality in ArtemiS SUITE Application Note – 08/14 │10│ Figure 9:
Example with different navigation views After creating a navigation view, the data can be viewed with
the new structure in the Database section of the HEAD Navigator. Figure 10 shows the structure in the
Windows Explorer compared to the structure of the navigation view. The new structure is a database
function affecting only the view in ArtemiS SUITE without touching the actual data. Multiple users can
therefore structure the data in different ways according to the respective task without moving or
copying the files on the hard disk. If required, different views can also be used at the same time! To
create a new navigation view or modify an existing view, open the Database menu and select Navigation
Views. When opened for the first time, the tree structure only shows one navigation view (Channels by
type and name). HEAD acoustics Application Note Database functionality in ArtemiS SUITE Application
Note – 08/14 │11│ Figure 10: Structure in the Windows Explorer (left), structure of the navigation view
(right) Clicking on the button opens a window where you can enter a name and a description for the
new navigation view. You can also specify which file properties are to be used as sorting criteria. These
parameters correspond to those in the search form described above and shown in figure 2. When you
have made all desired settings, click on OK to create the new navigation view and to close the properties
dialog. The next step is to add a grouping to the selected navigation view by clicking on the button. A
grouping corresponds to a level in the tree structure of the navigation and is the criterion by which the
items are grouped into lists. A dialog window is opened automatically, where you can select a sorting
criterion from all documentation fields stored in the database. System documentation parameters are
marked with an @. For backup purposes or for transferring your navigation views to another computer,
you can export all navigation views you created as an XML file. To do so, click on Database -> Navigation
Views and then on Export Navigation... With Import Navigation... you can reload navigation views stored
in an XML file. HEAD acoustics Application Note Database functionality in ArtemiS SUITE Application
Note – 08/14 │12│ Database maintenance and organization For maintaining and organizing the
databases, the ArtemiS SUITE provides various tools. If data stored in a database is moved or deleted
later, broken references can be the result. To repair such broken references, click on Database -> File
References. This opens a window where you can check the file references in your database and repair
broken references. After opening, the references are first checked automatically. All broken references
are then shown in a list with the default action (Leave). Instead of the default action, you can choose
one of the following error handling actions for each broken reference: • Relocate: Opens a file browser,
where you can assign a new path to repair the reference. • Delete: The broken reference is removed
from the database. • Leave: The path is not changed. This option should be used, for example, if the
missing files are located on a removable medium, which will be available again later. After selecting the
appropriate actions for each broken reference, click on OK to execute them. Clicking on Cancel, on the
other hand, closes the window and discards your changes. The command Database -> Database
Properties opens a window with general information about the database and the contained data.
Furthermore, on the Content tab, you can remove individual folders from the database, e.g. if they are
no longer required for the search. To do so, right-click on the desired folder and then on Remove (see
figure 11). Figure 11: Database Properties Another possibility to remove a folder from a database is
provided by the HEAD Navigator, where you can right-click on the desired folder and then select
Database -> Remove from Database. HEAD acoustics Application Note Database functionality in ArtemiS
SUITE Application Note – 08/14 │13│ Note In order to use the functions described above in the ArtemiS
SUITE, you need the ArtemiS SUITE Basic Database Module (code 5003) in addition to the ArtemiS SUITE
Basic Framework (code 5000). In addition to the information compiled in this Application Note, the
database functions are also explained comprehensively in the online help of the ArtemiS SUITE. Do you
have any questions or remarks? Please write to: imke.hauswirth@head-acoustics.de We look forward to
receiving your response!

Gather Information

Ways of collecting information

Once you have defined what you want to find out, and have set your key indicators, it is time to start thinking about what
questions you will need to ask and the best way to collect the information.

Top

Whom to ask, how, and what will you do with the information?

There are several decisions you need to make, including who you will need to approach to get the information that you need.
Organisations with large groups of people to survey may want to approach a sample of the total group, asking only a
percentage of people chosen at random to respond. It is also important to choose an appropriate format for collecting
information based on whom you are asking and what you are asking about. Information about the different formats, such as
questionnaires, focus groups, and telephone surveys can be found at Compare Research Methods. It is also important that you
have a clear idea at this stage of how you want to analyse, present, and use the information you collect. These decisions will
link back to some of the previous elements in the proving and improving cycle.

For example:

• Your motivations for proving and improving.

• Your organisation’s stakeholders, which will affect both whom

you will be consulting or asking questions of and to whom you will
be presenting the findings.

Top

Measuring or demonstrating change over time

In developing some quantitative information about your organisation’s outcomes, you may wish to set up a baselinesurvey.
This involves a series of quantitative indicators that you will measure at regular intervals with similar people or groups. This can
help you to track the organisation’s performance over time.

If you intend to show the ‘distance travelled’ by people who are employed by your organisation, it will be important to do an
initial interview, questionnaire, or survey when people first come into contact with your organisation and then at one or more
specified points later on. You will want to ask about the same aspects of their lives – the areas in which your organisation hopes
to make a change – at each point in time in the same way. These questions can be done either formally or informally as part of
an ‘intake’ or initial induction process and as part of periodic check-ins or reviews at regular intervals.

Top

Tips on asking good questions footnote 1

The following are some tips for developing your questions and how to ask them – your methodology. In defining the questions
you want to ask follow these helpful hints.

• Ask about the most important issues – ones that can be acted
upon.

• Be precise – ask the exact question you want to know the answer
to, and clarify it for yourself before writing the question by asking
‘what do we mean by that?’

• Keep it relevant– make sure the questions are useful to your

organisation. Surveys are not intended to be research studies, but
to give your organisation and its stakeholders important
 information.

• Be direct – ask about the respondent’s experience, opinions and

perceptions, not those of others

• Be unambiguous – use words clearly, and be sure to define them.

• Be thorough – ask around the question, ask why and how as well
as what and how many.

• Be consistent – don’t use a 10 on a 10-point scale to mean ‘very

much’ in one question and ‘not at all’ in another

• Keep it short – most people will only want to respond to one or

two pages worth of questions.

• Keep it simple. Don’t ask respondents to calculate things – you

can do these as part of the analysis. Do not ask people to
generalise or to summarise events that happened long ago.

• Stay neutral. Do not use loaded questions that encourage a

respondent to answer in a way they think you want them to!
Make sure that the questions have an equal number of positive
and negative answers. (e.g. definitely yes, probably yes, probably
no, definitely no).

Lo2: Identify scalability and functionality requirements

A functional requirement describes what a software system should do, while non-
functional requirements place constraints on how the system will do so.
Let me elaborate.

An example of a functional requirement would be that a system must send a an email whenever
a certain condition is met (e.g. an order is placed, a customer signs up, etc).

A related non-functional requirement for the system may be that emails should be sent with a
latency of no greater than 12 hours from such an activity.

The functional requirement is describing the behavior of the system as it relates to the
system's functionality. The non-functional requirement elaborates a performance
characteristic of the system.
Typically non-functional requirements fall into areas such as:

 Accessibility
 Capacity, current and forecast
 Compliance
 Documentation
 Disaster recovery
 Efficiency
 Effectiveness
 Extensibility
 Fault tolerance
 Interoperability
 Maintainability
 Privacy
 Portability
  Quality
 Reliability
 Resilience
 Response time
 Robustness
 Scalability
 Security
 Stability
 Supportability
 Testability
A more complete list is available at Wikipedia's entry for non-functional requirements.
Non-functional requirements are sometimes defined in terms of metrics (something that can be
measured about the system) to make them more tangible. Non-functional requirements may
also describe aspects of the system that don't relate to it's execution, but rather to it's evolution
over time (e.g. maintainability, extensibility, documentation, etc).

Functional Requirements: specify the functionality of the system. (e.g. fields in a form)

Non-functional Requirements: specify the quality of the system, is mostly related to thesatisfiability of
99dow the user. (e.g. minimium acceptable page load time)
n vote I got the above information from this link. There is some thorough discussion there.
  I'm wondering about functional or non-functional requirements. I have found lot of different
definitions for those terms and I can't assign some of my requirement to proper category.

I'm wondering about requirements that aren't connected with some action or have some additional
conditions, for example:

1. On the list of selected devices, device can be repeated.

2. Database must contain at least 100 items
3. Currency of some value must be in USD dollar.
4. Device must have a name and power consumption value in Watts.
are those requirements functional or non-functional ?

I think the distinction between "functional" and "non-functional" is misleading and tends to leave software with p
operability. I've found that thinking about "end-user features" and "operational features" leads to better softwar

    @MatthewSkelton I could not tell if (2.) is an en-user feature or an operation feature. Seems to be a "testing-
feature". –  moose Jul 23 '13 at 6:41

    @moose - the requirement for the DB to /operate within certain parameters/ given 100 items is more of an
operational requirement, although this might impact the end-user experience if performance were degraded.
Ultimately, we'd probably need a bit more context on the requirements in the OP to be able to split into F and NF
although - as I hinted - I think this is a bit of a spurious distinction anyhow :)   Matthew Skelton

add a comment

add a comment
up functional requirements are the main things that the user expects from the software for example if the
vote8dow application is a banking application that application should be able to create a new account, update the
n vote account, delete an account, etc. functional requirements are detailed and are specified in the system
design

Non-functional acquirement are not straight forward requirement of the system rather it is related to
usability( in some way ) for example for an banking application a major non-functional requirement
will be availability the application should be available 24/7 with no down time if possible.

thank you for your example 

add a comment
up Functional requirements will specify a behaviour or function.
vote4dow for example: “Display the name, total size, available space and format of a flash drive connected to the
n vote USB port.
Non-functional requirements cover all the remaining requirements which are not covered by the
functional requirements. They specify criteria that judge the operation of a system, rather than specific
behaviours.
for example: “Modified data in a database should be updated for all users accessing it within few
seconds.

I think functional requirement is from client to developer side that is regarding functionality to the user by the
software and non-functional requirement is from developer to client i.e. the requirement is not given by client but
it is provided by developer to run the system smoothly e.g. safety, security, flexibility, scalability, availability,
etc.

Some of the more typical functional requirements include:

 Business Rules
 Transaction corrections, adjustments and cancellations
 Administrative functions
 Authentication
 Authorization levels
 Audit Tracking
 External Interfaces
 Certification Requirements
 Reporting Requirements
 Historical Data
 Legal or Regulatory Requirements

So what about Non-Functional Requirements? What are those, and how are they different?

Simply put, the difference is that non-functional requirements describe how the system works,
while functional requirements describe what the system should do.

The definition for a non-functional requirement is that it essentially specifies how the system should
behave and that it is a constraint upon the systems behaviour. One could also think of non-functional
requirements as quality attributes for of a system.

A non-functional requirement for a hard hat might be “must not break under pressure of less than 10,000
PSI”
Non-functional requirements cover all the remaining requirements which are not covered by the
functional requirements. They specify criteria that judge the operation of a system, rather than specific
behaviours, for example: “Modified data in a database should be updated for all users accessing it within
2 seconds.”

Some typical non-functional requirements are:

 Performance – for example Response Time, Throughput, Utilization, Static Volumetric

 Scalability
 Capacity
 Availability
 Reliability
 Recoverability
 Maintainability
 Serviceability
 Security
 Regulatory
 Manageability
 Environmental
 Data Integrity
 Usability
 Interoperability

As said above, non-functional requirements specify the system’s ‘quality characteristics’ or ‘quality
attributes’.

Many different stakeholders have a vested interest in getting the non-functional requirements right
particularly in the case of large systems where the buyer of the system is not necessarily also the user of
the system.

The importance of non-functional requirements is therefore not to be trifled with. One way of ensuring
that as few as possible non-functional requirements are left out is to use non-functional requirement
groups. For an explanation on how to use non-functional requirement group, read this blog post which
will give you four of the main groups to use.
Lo3: Prepare report

Create a Report Server

Database (SSRS Configuration
Manager)
SQL Server 2016
 
Reporting Services Native mode uses two SQL Server relational databases to store report server metadata and
objects. One database is used for primary storage, and the second one stores temporary data. The databases are
created together and bound by name. With a default SQL Server instance, the databases are
named reportserver andreportservertempdb. Collectively, the two databases are referred to as the "report server
database" or "report server catalog".
Reporting Services SharePoint mode includes a third database that is used for data alerting metadata. The three
databases are created for each Reporting Services service application and the database names by default include a
guid that represents the service application. The following are example names of the three SharePoint mode
databases:

Create a Report Server

Database (SSRS Configuration
Manager)
SQL Server 2016
Reporting Services Native mode uses two SQL Server relational databases to store report server
metadata and objects. One database is used for primary storage, and the second one stores temporary
data. The databases are created together and bound by name. With a default SQL Server instance, the
databases are named reportserver andreportservertempdb. Collectively, the two databases are
referred to as the "report server database" or "report server catalog".

Reporting Services SharePoint mode includes a third database that is used for data alerting metadata.
The three databases are created for each Reporting Services service application and the database names
by default include a guid that represents the service application. The following are example names of
the three SharePoint mode databases:

ReportingService_90a9f37075544f22953c4a62e4a9f370

ReportingService_90a9f37075544f22953c4a62e4a9f370TempDB

ReportingService_90a9f37075544f22953c4a62e4a9f370_Alerting

Important

Do not write applications that run queries against the report server database. The report server
database is not a public schema. The table structure might change from one release to the next.
If you write an application that requires access to the report server database, always use the
Reporting Services APIs to access the report server database.
The exception to this are the execution log views. For more information, see Report Server
Execution Log and the ExecutionLog3 View

Ways to Create the Report Server Database

Native Mode: You can create the Native mode report server database in the following ways:
 Automatically: Use SQL Server Setup Wizard, if you choose the default configuration installation option. In
the SQL Server Installation Wizard, this is the Install and configure in the Report Server Installation Options
page. If you chose the Install only option, you must use the Reporting Services Configuration Manager to
create the database.
 Manually: Use the Reporting Services Configuration Manager. You must create the report server database
manually if you are using a remote SQL Server Database Engine to host the database. For more information,
see Create a Native Mode Report Server Database (SSRS Configuration Manager).
SharePoint Mode: The Report Server Installation Options page only has one option for SharePoint mode of Install
Only. This option installs all the Reporting Services files and the Reporting Services shared service. The next step is to
create at least one Reporting Services service application in one of the following ways:
  Use SharePoint Central Administration to create a Reporting Services service application. For more
information see the “Service Application” section of Step 3: Create a Reporting Services Service Application.
 Use Reporting Services PowerShell cmdlets to create a service application and the report server databases.
For more information see the sample for creating service applications in the topic PowerShell cmdlets for
Reporting Services SharePoint Mode.

Database Server Version Requirements

SQL Server is used to host the report server databases. The SQL Server Database Engine instance can be a local or
remote instance. The following are the supported versions of SQL Server Database Engine that can be used to host
the report server databases:
 SQL Server 2016 Community Technology Preview 2 (CTP2)
 SQL Server 2014
 SQL Server 2012
 SQL Server 2008 R2
 SQL Server 2008
 SQL Server 2005
Creating the report server database on a remote computer requires that you configure the connection to use a
domain user account or a service account that has network access. If you decide to use a remote SQL Server instance,
consider carefully which credentials the report server should use to connect to the SQL Server instance. For more
information, see Configure a Report Server Database Connection (SSRS Configuration Manager).

Important

Report Server and the SQL Server instance hosting the report server database can be in
different domains. For Internet deployment, it is common practice to use a server that is
behind a firewall. If you are configuring a report server for Internet access, use SQL Server
credentials to connect to the instance of SQL Server that is behind the firewall and use
IPSEC to secure the connection.

Database Server Edition Requirements

When creating a report server database, be aware that not all editions of SQL Server can be used to host the
database. For more information, see the “Report Server Database Server Edition Requirements” section of Features
Supported by the Editions of SQL Server 2016.