Overview

AppsAnywhere requires a single Microsoft SQL Server database in which to store configuration and application information.

Please refer to Latest Releases for the supported versions.

It is recommended that you host your database on an existing SQL Server cluster, however a dedicated instance can be created if preferable.

Management, backups and maintenance of the Microsoft SQL Server database remain the responsibility of the customer.

If installing a new Microsoft SQL server, please use the Microsoft recommended specification.

No additional features such as the Reporting Services are required, only the database engine.

Database Configuration

Two database containers will need to be created prior to deployment and configuration of any servers according to the details below.

A SQL script is provided below to create the required SQL logins and database users. 

The database container names and logins must be created exactly as shown. The database schemas will be created automatically during configuration.

Before running any of the scripts below, you must create the database containers.

The script should be edited and used to correctly create the SQL logins then map them to the correct databases.

As the scripts are creating SQL logins, they must be edited so that an appropriate password is set, replacing the [Password] variable shown below.

If Analytics is included in your deployment, refer to the Database Requirements section on the Analytics System Requirements article.

Database name:

AppsAnywhere

Usage:

This database will be used to store all AppsAnywhere configuration and details of the applications.

Permissions:

A SQL login named appsanywhere_user must be assigned db_owner permissions for the AppsAnywhere database.

Password:

Must not contain any special characters (£$%^*@ etc.) but must include at least one number, one uppercase letter and one lowercase letter.

Initial Sizing:

50MB-100MB (.mdf)

Database name:

StreamDB

Usage:

This database will be used to store all Cloudpaging configuration and details of the applications.

Permissions:

A SQL login named dbjbuser must be assigned db_owner permissions for the StreamDB database.

Password:

Must not contain any special characters (£$%^*@ etc.) but must include at least one number, one uppercase letter and one lowercase letter.

Initial Sizing:

300MB-500MB (.mdf)

Create AppsAnywhere and Cloudpaging SQL accounts

--Create the AppsAnywhere login and user
USE Master
GO
CREATE LOGIN appsanywhere_user WITH PASSWORD = '[Password]', DEFAULT_DATABASE = appsanywhere;
GO
USE AppsAnywhere
CREATE USER appsanywhere_user FOR LOGIN appsanywhere_user
GO
ALTER ROLE db_owner ADD MEMBER appsanywhere_user;
GO

--Create the Cloudpaging login and user
USE Master
GO
CREATE LOGIN dbjbuser WITH PASSWORD = '[Password]', DEFAULT_DATABASE = streamdb;
GO
Use StreamDB
GO
CREATE USER dbjbuser FOR LOGIN dbjbuser
GO
ALTER ROLE db_owner ADD MEMBER dbjbuser;
GO
SQL

If the accounts are to be created manually, the SQL logins should be created under SQL server security as a new login with SQL server authentication. Enforce password expiration should be unchecked and default database set. 

User mapping should then be used to create the database user in the database and set db_owner permissions. 

Database Sizing

The databases will grow over time based on the number of applications and delivery methods that you configure within your AppsAnywhere portal.

Please refer to the Database Tuning article for on going maintenance of the databases.

The following table contains approximate database size based on number the of applications and active users.

AppsAnywhere


Total number of active users

Apps

250

500

1000

2000

50

190 MB

359 MB

689 MB

1349 MB

100

191 MB

360 MB

698 MB

1374 MB

200

192 MB

361 MB

699 MB

1375 MB

400

198 MB

367 MB

705 MB

1381 MB

The calculations above assume that there is an average of 2 delivery methods per application. All applications have 1 Cloudpaging delivery method and each active user has an average of 5 active Cloudpaged applications/sessions.

Sizes are specifically for the SQL Server .mdb database file and do not include the SQL Server database transaction log.

The SQL Server database transaction log can grow significantly during use. In order to ensure it does not consume large amounts of disk space we recommend daily backups of the transaction log to flush old records.

The following table contains approximate data sizes for the type of information stored within the AppsAnywhere database.

Data Type

Row Size (per 50 rows)

Application Data

60 KB

Application Delivery Methods

200 KB

Audit Change Event log

42 KB

AppsAnywhere Active Session and Identity information

400 KB

Cloudpaging Active Session Information

3300 KB

An additional 10MB is used for static configuration data.

Data categories above may span multiple tables. The row size does not include the table index size.