> For the complete documentation index, see [llms.txt](https://docs.cloudassert.com/wap-billing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudassert.com/wap-billing/2.1.7.41/installation/prerequisites.md).

# Prerequisites

Following are some of the installation pre-requisites and checklist.

**Cloud Assert Usage and Billing Database:**

* It is highly recommended to have Billing database in a performant SQL Server. Recommended system configuration is given below, 
  * Compute: CPU – 6 Cores 
  * Compute: Memory – 16 GB 
  * Disk Drive Type - SSD 
* (Optional) Create a SQL Database and note down the name. For example: CloudAssert.Billing.
* Create a database user with read-write, owner and admin privileges just to this database. This database needs db\_datareader/db\_datawriter permission for the following WAP databases.
  1. Microsoft.MgmtSvc.PortalConfigStore
  2. Microsoft.MgmtSvc.Store
  3. Microsoft.MgmtSvc.Usage


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloudassert.com/wap-billing/2.1.7.41/installation/prerequisites.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.