--- title: "TIR DBaaS FAQ" description: "Short answers about TIR DBaaS, from engines, regions, and billing to connecting, storage, parameter groups, extensions, snapshots, and delete." content_type: "faq" product: "tir-dbaas" platform: "TIR" url: "/tir/tir-dbaas/faq/" topic: ["faq"] --- # TIR DBaaS FAQ For help with a specific message, see [Troubleshooting TIR DBaaS](/tir/tir-dbaas/troubleshooting/tir-dbaas/). ## Getting started ### Where do I find DBaaS in TIR? With Chennai selected as the region, open your project, and in the side menu, under **Databases**, select **DBaaS**. DBaaS is offered in Chennai only, so you create databases in Chennai projects. See [Get started with TIR DBaaS](/tir/tir-dbaas/get-started/). ### Which database engines can I create? PostgreSQL only. You choose its version when you create the database, from the versions E2E currently offers for new databases, and the version stays fixed for the life of the database. See [Create a database](/tir/tir-dbaas/how-to/create-a-database/). ### How many nodes does a database have? One. Every database has a single node, the primary. See [How TIR DBaaS works](/tir/tir-dbaas/concepts/how-tir-dbaas-works/). ### Which permissions do I need? DBaaS has its own permission in a project, with read, create, update, and delete. It covers databases and parameter groups. Read opens the lists and the details pages. Create covers **Create Database**, taking snapshots, restores, and new parameter groups. Update covers **Edit**, start, stop, restart, and password resets, and delete covers **Delete**. A project member has DBaaS permission only when their policies grant it. See [TIR Access Control](/tir/tir-iam/). ### How is a database billed? The plan is priced per hour, and the disk is priced per GB per month, separately from the plan. You see an estimated cost for both before you launch. After you increase the storage, **Price** on **Overview** covers the new size. Prices are on the [pricing page](https://www.e2enetworks.com/pricing). See [Billing for TIR DBaaS](/tir/tir-dbaas/concepts/billing-options/). ## Connecting ### How do I connect to my database? Open the database's **Connect** tab once it is **Running**. It gives the full connection URL, the host, port 5432, the database `defaultdb`, and SSL mode `require`. It also has ready-made strings for psql, JDBC, and a `.env` file, and code for common frameworks. See [Connect to a database](/tir/tir-dbaas/how-to/connect-to-a-database/). ### Is SSL required? Yes. Every connection from outside the database must use SSL and a password, so every network login is encrypted. Use `sslmode=require`, as the connection strings on the **Connect** tab do. ### Why is there no password in my connection string? Connection strings always carry `` in place of the password, and you replace it with the user's password. If you have lost the password, set a new one with **Reset Password**. See [Reset a user's password](/tir/tir-dbaas/how-to/reset-a-user-password/). ### Who can reach my database? Only the IPv4 addresses and ranges in the database's IP allowlist can reach its public endpoint. When you create or edit a database, the list needs at least one range. Connections from inside an attached VPC skip the allowlist. See [Control network access to a database](/tir/tir-dbaas/how-to/control-network-access/). ### Can I create more database users? Yes, with SQL. The portal lists every login on the database under **Connect as**, including users created with SQL, and resets their passwords. You create, rename, and delete users with SQL, not in the portal. See [Connect to a database](/tir/tir-dbaas/how-to/connect-to-a-database/). ## Changing a database ### Can I change the plan, the PostgreSQL version, or the name later? No. After creation you can increase storage, change the IP allowlist, the VPC, and the parameter group, and add extensions. The name, plan, PostgreSQL version, and admin username stay as they were created. See [Edit a database](/tir/tir-dbaas/how-to/edit-a-database/). ### Can I increase or reduce storage? You can only increase it, up to 1,000 GB, and each increase is permanent. The database keeps serving connections, and shows **Scaling** until the change is done. See [Edit a database](/tir/tir-dbaas/how-to/edit-a-database/). ### What does stopping a database do? Stopping drops every open connection, and nothing can connect until you start the database again. Its data and storage are kept. See [Stop, start and restart a database](/tir/tir-dbaas/how-to/stop-start-and-restart-a-database/). ## Parameter groups and extensions ### What is a parameter group? A parameter group is a saved set of PostgreSQL settings that you attach to databases. One group can be attached to many databases, and a database uses at most one group. Attach a group from **Edit Database** while the database is **Running**. See [Use parameter groups](/tir/tir-dbaas/how-to/use-parameter-groups/). ### Does attaching a parameter group restart my database? No. Attaching applies the group's values while the database keeps running, and values that PostgreSQL reads only when it starts take effect at the next restart. To apply everything at once, choose **Update & Restart**. See [Use parameter groups](/tir/tir-dbaas/how-to/use-parameter-groups/). ### Why is Delete not available for my parameter group? **Delete** is available only once the group is detached from every database. Detach it, then delete it. See [Use parameter groups](/tir/tir-dbaas/how-to/use-parameter-groups/#delete-a-parameter-group). ### Which extensions can I add? pg_stat_statements, vector (pgvector), pg_trgm, uuid-ossp, pgcrypto, hstore, citext, btree_gin, btree_gist, ltree, and unaccent. pg_stat_statements and vector are chosen when the create page opens. pg_stat_statements is installed on every database. See [Add extensions](/tir/tir-dbaas/how-to/add-extensions/). ### Can I remove an extension? No. An installed extension stays, because **Edit Database** only adds extensions. See [Add extensions](/tir/tir-dbaas/how-to/add-extensions/). ## Snapshots and restore ### Does taking a snapshot take my database offline? No. The database stays online while a snapshot is taken. See [Take a snapshot of a database](/tir/tir-dbaas/how-to/take-a-snapshot/). ### Does restoring a snapshot overwrite my database? No. **Restore** creates a new database from the snapshot, with the source's plan, PostgreSQL version, region, and storage size, and the data, databases, and users in the snapshot. The source database stays as it is. The new database starts with an empty IP allowlist, and you set the VPC, the parameter group, and the snapshot schedule again yourself. It is a separate database with its own price. See [Restore a database from a snapshot](/tir/tir-dbaas/how-to/restore-from-a-snapshot/). ### How many scheduled snapshots are kept? As many as you set in **Snapshots to Keep**, from 1 to 60. After each scheduled snapshot, the oldest scheduled snapshots beyond that number are deleted. The schedule removes only scheduled snapshots and leaves the ones you take yourself in place. See [Schedule snapshots of a database](/tir/tir-dbaas/how-to/schedule-snapshots/). ### What happens to my snapshots when I delete a database? The snapshot schedule is turned off at once. Once the delete finishes, the database's snapshots go with it, so you can restore one only before the delete. To keep the data, restore a snapshot into a new database first. See [Delete a database](/tir/tir-dbaas/how-to/delete-a-database/). ## Monitoring and deleting ### Can I see slow queries or the server logs? No. The portal's monitoring covers the node's resources: **Nodes & Monitoring** charts the node's CPU, memory, storage, disk, and network, and **Activity Timeline** records every action on the database. Slow or failing queries, connection counts, and database server logs are outside it. See [Monitor a database](/tir/tir-dbaas/how-to/monitor-a-database/). ### How far back do the charts go? The longest time range on the charts is **30d**. The others are **1h**, **6h**, **1d**, and **7d**. See [Monitor a database](/tir/tir-dbaas/how-to/monitor-a-database/). ### Can I delete a database that failed to launch? Yes. **Delete** is available in every status except **Terminating**, including **Creating**, **Stopped**, and **Failed**. Deleting a database removes its data permanently. See [Delete a database](/tir/tir-dbaas/how-to/delete-a-database/).