> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/pentaho-installation-overview-cp/archive-installation/archive-installation-process/use-ms-sql-server-as-your-repository-database-archive-installation/initialize-ms-sql-server-pentaho-repository-database/step-4-verify-ms-sql-server-initialization.md).

# Step 4: Verify MS SQL Server initialization

**Note:** Unless you change it in Step 1, above, the default password for each username below is `password`.

After you run the scripts, perform the following steps to verify that databases and user roles have been created properly:

1. Open MS SQL Server Management Studio.
2. Log in as: *hibuser*
3. In the **Object Explorer** section, navigate to **hibernate** and verify that you can see the tables.
4. If you installed Pentaho Operations Mart, log in as: *pentaho\_operations\_mart*
5. In the **Object Explorer** section, navigate to **pentaho\_operations\_mart** and verify that you can see the tables.
6. Log in as: *jcr\_user*
7. In the **Object Explorer** section, navigate to **jackrabbit** and verify that you can see the tables.

   The jackrabbit tables may not appear until you have started Pentaho for the first time.
8. Log in as: *pentaho\_user*
9. In the **Object Explorer** section, navigate to **quartz** and verify that you can see the tables.
10. Exit from the MS SQL Server Management Studio tool.

You have initialized the MS SQL Server Pentaho Repository database.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/install/10.2-install/pentaho-installation-overview-cp/archive-installation/archive-installation-process/use-ms-sql-server-as-your-repository-database-archive-installation/initialize-ms-sql-server-pentaho-repository-database/step-4-verify-ms-sql-server-initialization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.