Azure Database for PostgreSQL Reviews

My main use case for Azure Database for PostgreSQL involves migration from on-premise to Azure Database for PostgreSQL using technologies such as a migration database DMA.

A specific example of a migration project I have worked on using Azure Database for PostgreSQL involves shipping all workloads from on-premise, locally inside the data center to Azure cloud using all structures and all reliability and security from cloud into Azure.

Regarding my use case and the types of workloads I have migrated, we need to ship first the schema, after moving each data access to Azure cloud. The ability to save all restore points in the backup point in time into Azure is very helpful with teams such as DevOps and DBA.

Azure Database for PostgreSQL has positively impacted my organization because it provides more CapEx and OpEx according to the type of the databases. When we needed to use on-premises data centers, the cost was very high. By moving to the cloud, we shifted costs from OpEx to CapEx.

Regarding the impact on costs after moving to Azure Database for PostgreSQL, we can spread each cost according to each client, and when we use a specific database, we can tag and monitor the cost of each resource to understand the budget, similar to on-premises.

Azure Database for PostgreSQL has facilitated the adoption of AI technologies in our database operations by allowing the use of tools such as GitOps, which provides greater flexibility for squads to utilize and promote resources in different environments.

Azure Database for PostgreSQL has influenced our application development process; using migration tools allows us to deploy in incremental flows, which results in tiny differences in resources while providing greater governance and replicability.

My organization's database uptime has changed after implementing Azure Database for PostgreSQL. I believe it has improved by approximately 90%, because during the deployment of on-premises PostgreSQL, we needed to stop the application for maintenance, but with Azure, we can restore at any time using point-in-time backups, which is very helpful for developers.

In my opinion, the best feature of Azure Database for PostgreSQL is the backup point in time, which is very helpful during migrations or any situation where we need to restore the database.

This backup feature has helped me in real-world scenarios due to scalability and elasticity in Azure cloud, which is very helpful when moving thousands of gigabytes in each database during the migration process.

When it comes to features of Azure Database for PostgreSQL, the integration with monitoring is very beneficial, such as accessing Azure Monitor, allowing us to check and receive alerts if there is any spike in usage. This is a very different approach compared to on-premises, but in Azure, it is very helpful due to its scalability and flexibility.

Concerning Azure Database for PostgreSQL's AI capabilities, its governance and security are much better because it is very helpful and does not require deep knowledge of queries or complex arithmetic, which is a beneficial feature.

My experience with the monitoring and management tools provided by Azure Database for PostgreSQL is positive; metrics can be sent from the cloud by another application such as DataDog, allowing for alerts and being very helpful in checking performance issues during incidents.

Regarding impressions of security features in Azure Database for PostgreSQL, the most valuable feature is the firewall security, which blocks any unauthorized access. I need to configure access for each developer by their IP address, which is critical for security.

In terms of improvement for Azure Database for PostgreSQL, the native applications can be enhanced, as we can use different tools to connect the database, but I believe the browser on the Azure portal can be made more user-friendly.

Regarding needed improvements, I find that the refresh time of the page being five minutes causes the same issues according to the types of scripts or queries when running. If the query takes too long to execute, I need to use a specific tool rather than the browser, which sometimes generates concerns for developers.

I have been using Azure Database for PostgreSQL for approximately eight years.

Regarding accuracy and reliability of output, Azure Database for PostgreSQL has proven to be very helpful, as I have not experienced any issues such as lack of performance or instability.

I have not experienced any significant latency with Azure Database for PostgreSQL, as the performance can be improved based on the pricing tier of the database, and I have not encountered issues according to the status page in Azure.

Azure Database for PostgreSQL is stable.

Azure Database for PostgreSQL's scalability is better; we can distribute resources according to the self-region and budget, while being mindful of how pricing tiers impact costs as scalability grows.

Whenever I need customer support, I receive excellent assistance from the Azure support analysts.

On a scale of one to ten, I would rate customer support a ten.

I previously used Azure MySQL server and Azure SQL server due to different approaches, but the logic behind them is similar to Azure Database for PostgreSQL.

I have seen a return on investment; specifically, I save money and time because in my recent project using Azure Database for PostgreSQL, I do not need a virtual machine in the data center. I can allocate all databases according to each client's usage of different resources, allowing cost savings by assigning costs to each client according to their requirements.

My experience with pricing, setup cost, and licensing is that pricing is very important due to budget constraints in each project; while migration costs can be high during the process, after migration, savings can be substantial compared to on-premises applications.

Before choosing Azure Database for PostgreSQL, I evaluated other options, but the licensing differences are significant, and we found that PostgreSQL has much better cost advantages compared to solutions such as Oracle or SQL Server.

I would rate Azure Database for PostgreSQL a nine out of ten.

I chose a nine because it is very helpful and easy to run some types of queries, but in some cases, I need specific tools installed locally, although it performs much better in comparison with on-premises use.

The integration of Azure Database for PostgreSQL with other Azure services has not impacted our overall cloud strategy, as we are not working with a multi-cloud strategy, but we can replicate with tools such as EAC for multiple applications while creating each structure in each cloud.

I would advise others looking into using Azure Database for PostgreSQL to pay attention to computing and storage, as they can improve the cost of resource allocation. Azure Database for PostgreSQL receives a rating of nine out of ten.

I have been using Azure Database for PostgreSQL for almost one year. My use cases for Azure Database for PostgreSQL include using it for my day-to-day data engineering purposes, as I am a data engineer and need to use it. It is useful for applications that depend on Agent SQL jobs, Link Server, and cross database queries, handling the queries to get the SQL queries.

The best aspect of Azure Database for PostgreSQL is that it is automated, featuring automated backup, security features, and compatibility with SQL server workload, being very useful for organizations planning to migrate to the cloud with minimal application changes.

Azure Database for PostgreSQL has influenced my application development process as it is used for modern web and cloud native applications, helping in many programming languages such as Java, .NET, Python, Node.js, and PHP, providing flexibility and a rich ecosystem of extensions while easily integrating with Azure services, making deployment and management easier, with high availability and an automated backup facility improving application reliability.

The integration of Azure Database for PostgreSQL with other Azure services has improved our overall cloud strategy by reducing database administration effort through automated backup, patching, and maintenance, enhancing reliability and scalability, and providing performance visibility through monitoring and diagnostic tools while lowering operational overhead compared to managing on-premises database infrastructures.

I would like to see improvements in Azure Database for PostgreSQL, such as more built-in performance tools, automated troubleshooting for complex performance issues, enhanced monitoring dashboards for faster root cause analysis, greater visibility, additional automation for scaling recommendations, and more integrated reporting capabilities.

I have been using Azure Database for PostgreSQL for almost one year.

After implementing Azure Database for PostgreSQL, our database uptime has improved significantly thanks to built-in high availability reducing unplanned downtime, faster recovery capabilities, and better monitoring and alerting which make planned maintenance easier and improve service reliability.

Azure Database for PostgreSQL's ability to scale workloads is straightforward, allowing scaling based on workload requirements, supporting compute and storage scaling, handling traffic spikes without major infrastructure changes, being suitable for both small and enterprise scale workloads, and maintaining consistent performance while reducing operational complexity.

I have not experienced technical support from Microsoft regarding Azure Database for PostgreSQL, but I have heard they have responsive and helpful support engineers that guide configurations, performance, connectivity, and migration issues while prioritizing critical incidents, and their extensive documentation is useful for self-service troubleshooting.

I do not have any experience migrating from on-premises PostgreSQL database to Azure Database for PostgreSQL as I worked on the same premises.

The security features in Azure Database for PostgreSQL, such as encryption and advanced threat protection, mean the data is encrypted at rest and in transit, with Microsoft Entra ID supporting centralized identity management and network security enhanced by private access, VNet integration, and firewall rules, along with RBAC roles for managing permissions and automated backups protecting against data loss, all contributing to improved visibility for security-related activities.

Azure Database for PostgreSQL facilitates the adoption of AI technologies by improving database monitoring and performance optimization, providing recommendations to identify slow queries, offering predictive analytics for workload trends and capacity requirements, and assisting in anomaly detection by identifying unusual database behavior.

My experience with the monitoring tools in Azure Database for PostgreSQL includes query performance insight, allowing me to use extensions such as pg_stat_statements to help analyze query performance and execution statistics, providing visibility into database health and workload behavior, and monitoring being centralized through the Azure portal, with Azure Monitor being the primary tool to monitor CPU, memory, storage, connections, and overall data performance.

In terms of latency, Azure Database for PostgreSQL provides very low and consistent latency for most workloads, relying on application design, query optimization, and network connectivity, resulting in generally consistent response times when the database is properly sized and optimized.

I would definitely recommend Azure Database for PostgreSQL because it has many advantages for modern applications and enterprise workloads, including its open-source nature reducing licensing costs, large community support, extensive ecosystem, and robust security, backup, and high availability features, resulting in a good balance of performance, scalability, security, and cost efficiency. I would rate my overall experience with Azure Database for PostgreSQL as an eight out of ten.

Azure Database for PostgreSQL provides a variety of data types that we utilize in our applications. For instance, we have an application where we need to store many different types of data. We store user data and any structured data that needs to be processed systematically in Azure Database for PostgreSQL. Longer files, videos, and projects are stored in Cosmos DB, while the metadata for those items is stored in Azure Database for PostgreSQL.

My experience with the monitoring and management tools provided by Azure Database for PostgreSQL has been positive. We have been using it and receive error details through the system. Whenever we have issues on the customer side, we can review those logs and find the issues straightforwardly.

Azure Database for PostgreSQL has positively influenced my application development process. Before this, we used SQL Servers that were on-premises and there were many complications to integrate them. With Azure Database for PostgreSQL, that integration issue has been eliminated and it is easier to integrate, get started with, and begin storing and working with data.

Azure Database for PostgreSQL helps to speed up processes and really does impact the time to market for our applications. We can always have replicas and change the environment to use as a production one. Time to market is faster because once we have the development server ready, we can use the same steps for production and it spins up in approximately five minutes.

The features of Azure Database for PostgreSQL that I prefer include the ability to connect from anywhere. I can connect it to PGAdmin or through VS Code, and that connectivity and faster working from any location is valuable. Additionally, the dashboards that come integrated with Grafana are beneficial. We can look at the dashboard and see what issues exist. With normal databases, you need to set up these things and establish rules before you can see the analysis and monitoring portions. Here, all of it comes integrated already, and you just need to go to the dashboard menu, enable it, and you will be able to see it. I can also customize the panels. As a DevOps professional, this is what I find helpful.

My impressions of Azure Database for PostgreSQL security features, such as encryption and advanced threat protection, are positive. All queries that we run are already encrypted. I have seen from multiple layers of the application how it runs and it is pretty secure because it does not get decrypted until it reaches the application layer at the PostgreSQL server. We also have monitoring to verify whether the data is encrypted, how many authentications have occurred, and who has authenticated. We can provide a service-managed key or customer-managed key, so all of those options allow us to secure it properly.

Azure Database for PostgreSQL integration with other Azure services has positively impacted my overall cloud strategy. We have protected our databases regionally, so if our application is in that particular region, we can easily connect it. We also secure it based on the origin of the requests that are coming in. Integration is also solid and there is no issue.

I would like to see improvements in Azure Database for PostgreSQL regarding identity management on the server itself. If they provide identity management on the server itself instead of logging in and writing queries for that, it would be better. If they provide the flexibility of creating users on the Azure portal, that would be an improvement.

I have been using Azure Database for PostgreSQL for two years, and PostgreSQL has been used for different projects along with Cosmos DB for different projects.

My impressions of the latency and availability of Azure Database for PostgreSQL are satisfactory. It goes hand-in-hand with Cosmos DB. If we have the right region for the right application, the latency is pretty low. If we are accessing it from an application that is not really in that region, then the latency is high. However, it is under milliseconds for PostgreSQL and for Cosmos DB, it depends on the file size.

My impressions of Azure Database for PostgreSQL in terms of scalability are positive. Since it is on the cloud, they can always allot the volume for it. Scalability is not an issue on cloud.

I previously used an on-premises database before adopting Azure Database for PostgreSQL. We used SQL DB before on-premises and now it is PostgreSQL on cloud.

Azure Database for PostgreSQL has helped to reduce infrastructure costs for us. If you deploy these on servers, they will cost a lot, whether on-premises or on cloud. This is a better option.

The organization's database uptime has improved after implementing Azure Database for PostgreSQL. The uptime is better now than it was before.

Azure Database for PostgreSQL's pay-as-you-go pricing model has affected my database-related cost and resource allocation. I do not know the exact minute details of the database cost. For even minor projects, we allot Azure DB and they say that to an extent, it is free for certain amounts of GBs. For development purposes, it is fine, but on production, you need to have a check on the cost of it.

Azure Database for PostgreSQL has impacted my organization's data protection strategy compared to the previous on-premises solution. The encryption part is significant. For our PostgreSQL servers, we have encrypted using the service-managed key and they handle it completely. If we need to encrypt it ourselves, we do it using the customer-managed key. All of the networking rules can be set up easily instead of doing the manual process in our own servers. All of these Azure-managed settings have enabled us the ease to secure this instead of having the headache of creating everything ourselves, monitoring everything ourselves, and setting the alert rules.

Azure Database for PostgreSQL has not facilitated the adoption of AI technologies in my organization's database operations. There are no special or differently enabled activities for PostgreSQL. We do have some on Cosmos DB, but not on PostgreSQL.

The integrations that have been most beneficial to my operations include the integration with Function Apps and Azure Function Apps. Container Apps are also services that we can integrate with and all of those happen at the developer level. Microsoft Defender for Cloud integration is also easy and we can simply enable it, which is approximately fifteen dollars or so. That works and using this at the application is also easier.

To my knowledge, there are no missing features that I would see included in Azure Database for PostgreSQL in the future. For our application, it is fine as it is, though other people may want different features.

My overall advice to other organizations considering Azure Database for PostgreSQL is to proceed with it. I would rate my experience with this product a nine out of ten.

Our main use cases for Azure Database for PostgreSQL include security dates, security tools, and a couple of small applications that move data and read data from other sources such as logs or claims and process it. Some of our use cases are simple websites that use Azure Database for PostgreSQL.

We are starting with Copilot and agents built from Copilot. It will almost be the year of our agent for next year because many people are asking for Copilot Studio. On the keynote, we saw the old App Maker or App Builder. I am always looking at how people can make small things and be out the door already using the Azure Copilot environment. We are looking forward to that.

we are working to a proof of concept. so we are totally ready to see what can be improved.

The most valuable features of Azure Database for PostgreSQL for us are reliability, performance, and cost, making it a good cost-benefit for us.

For Azure cost-benefit, not having an on-premises solution and having Azure Database for PostgreSQL on Azure means we leverage Azure Database for PostgreSQL being built and maintained by Microsoft engineers who know far more than I do. They already have the experience to ensure that the application is up and running and any recommendations that come from it. For example, they provide recommendations such as 'you should probably run it like this' or 'you are missing some optimizations.' That is the kind of information I would like to see.

Patching is seamless. The applications we have running there, SharePoint, and all the other services, those get patched and we never get any downtime. Having databases up and running all the time would be great because it is a struggle now.

We would love to definitely see scalability. We would love to see it grow as more people use it and it can handle the data and maybe tell us some optimizations by reporting on what we have. Hopefully, we will see more security features. We can ensure that we are doing good governance on that and that the data that should be there is there and we are controlling access to it.

I have been in my current role for about five years.

Azure Database for PostgreSQL is very stable. Many companies have blips when their internet goes down and things happen. All cloud platforms experience downtime, but it has been very available for us.

It is something we can spin up and test and start running for applications on a small level. Once you can prove that, we can go big. We do not have to buy everything and build it. It is already there. We just throw on a switch, and it is ready to go. We can use that much. Later on when people say they like it, we can say great and really ramp up using it.

We have not expanded usage at this time.

I have used Microsoft Support, but not for Azure Database for PostgreSQL. I have used it for other services.

I would rate it an eight because sometimes I get someone who knows their material and they solve the problem quickly. Sometimes I have to jump through hoops of doing many things and then the person says they cannot solve it. That is when I realize they are just reading from a script. When I am in a time crunch, you want to get to an engineer level problem quickly. Sometimes it takes too long for me to get to an engineer level problem that I want, but sometimes I get there and find a person who has the solution. I think that is great.

Positive

We looked at Snowflake. We were looking at other options. We have a little bit of MySQL, but that is not really cutting it anymore. There is Azure Database for PostgreSQL running on another cloud vendor as well.

The setup is fairly point-and-click. We just look at the steps to grow it. All the other decisions on the other side are on Microsoft's side. When we want something this big, Microsoft makes it happen. I do not have to think about how much memory I need or how much RAM I need. I do not have to think about whether the server is going to be big enough or what we have to build or whether we have to build a cluster now. We do not have to do that anymore.

At this point, that is not applicable. Someone else sets it up. My manager and the vendors set that all up.

For us, the build was fine. It is mainly repointing information. We are kind of interconnected, so you have to find a database that is not something we move and that is pretty standalone. It is mainly figuring out what our own business is and what is pointing at it more than anything else. Once you figure that out, you can change the connectors and everything else. That is more from the application side and our UC4 and any automatic processes that we have running or SQL processes.

I would say the ROI is a nine because we are just starting to want to get it up there and it has been easy for us to build up and do a small thing. We have not stressed it out yet. We are trying to get to the proof where we are talking to one group and saying let us move something else over there now. That takes time. We are not quite there yet where we are really stressing something out.

advise to get E5 for better security and governance of your data and systems

I do use Azure Active Directory integration for security. Using Azure helps us say you only get a certain amount of access based on whether you are a corporate device or your own device. We are already using features like that to help secure and keep our data safe.

We are starting with Copilot and agents built from Copilot. It will almost be the year of our agent for next year because many people are asking for Copilot Studio. On the keynote, we saw the old App Maker or App Builder. I am always looking at how people can make small things and be out the door already using the Azure Copilot environment. We are looking forward to that.

I do not think we are there yet to really get that benefit. I do not think I am there yet either. Our overall review rating for Azure Database for PostgreSQL is nine.

Azure Database for PostgreSQL serves several use cases for me. I use it primarily for testing and development environments where I need flexible database access without long-term commitments.

The pay-as-you-go pricing model is one feature I truly appreciate. I can pay for only the amount of time I need the database, which is very efficient for my test environment and development work. I don't have to purchase upfront to gain access; instead, I just get billed for the specific hours I use the database. This makes me more inclined to develop when I know what I'm expecting. However, when I start planning for production where the service will be up for two or three years, I prefer to pay upfront, as the pay-as-you-go model becomes expensive for production use.

Another significant benefit is that I don't have to worry about power management and security concerns associated with physical servers. With a physical server, many people could potentially gain access, which makes tracking difficult. Azure Database for PostgreSQL allows me to create different user accounts with specific access levels, which greatly helps my monitoring process, logging, and incident response. I can monitor when my database is accessed by unauthorized users and receive alerts for those events.

Apart from the scaling aspect, I would like to see improvements in the user interface. If a guided journey could be created, I would prefer that approach. Some cloud platforms I've used have journeys that guide you through processes, but with Azure Database for PostgreSQL, I have to know exactly what I want to do and navigate there myself. This was not beginner-friendly for me at the beginning.

I have been using Azure Database for PostgreSQL for four years.

Regarding availability and latency, I learned that placing all my services in one networking environment reduces latency significantly. I put them in different availability zones to ensure reduced latency of communication between virtual machines and all my services alongside the database. Once everything is in the same networking environment, the latency becomes much smaller compared to when I have everything spread across different availability zones and regions, which results in higher latency.

Azure Database for PostgreSQL demonstrates strong scalability capabilities for my workloads.

Microsoft technical support replies very quickly. I have had two issues, and when I raised support tickets, I received responses within two to three hours and they were able to resolve both issues. My first issue concerned my billing account where my credit card was not being accepted. I reached out to support about a credit card that had been working previously, and they resolved it for me. My second issue was concerning session hijacking. I was trying to figure out the best approach to protect my company against session hijacking, where people's session tokens get stolen and reused by attackers. Support advised me to use the feature of making sessions expire after 24 hours, which means users have to log in again after that period. This was accomplished using Entra ID. If a session gets hijacked, attackers would be logged off after 24 hours. The support team was very helpful in resolving this.

Before Azure Database for PostgreSQL, I used on-premises solutions. When I was working as an intern, most of our servers were Microsoft servers housed in-house. In terms of power consumption and power accessibility, the shift to Azure has been beneficial. Having to power the Microsoft servers we had at that time was quite burdensome on the organization I worked with then. We had to use inverters and other backup solutions because we were in Nigeria where power issues are common. Everything related to power was expensive, but with Azure Database for PostgreSQL, we were able to run operations easily because all of those infrastructure costs were offset.

I rate Azure Database for PostgreSQL a nine out of ten.

My main use cases for Azure Database for PostgreSQL are Edge, Edge AI, and edge data consolidation.

What I appreciate most about Azure Database for PostgreSQL is not one particular feature; I think it is the use case and the facility to have a single pane of glass for managing what is on the edge, what is on the cloud, especially now with Azure Local as well. It is not a product per se; it is the ecosystem integration overall.

The ecosystem integration of Azure Database for PostgreSQL benefits my company by having fewer moving parts, fewer points to break and touch. It simplifies operations and provides a seamless interface.

Microsoft needs to start developing specific agents that would be focused on Azure Database for PostgreSQL. It is almost like in the database world where stored procedures exist. Creating similar stored procedures but for agents within the database would be beneficial. This is not easy to implement as it requires architectural changes, but this would be a game changer for everybody.

I have been using Azure Database for PostgreSQL for approximately ten years.

I would not know if my company's database uptime has changed after implementing Azure Database for PostgreSQL because I am not tracking that. A team tracks that, and I have not heard any complaints, which I think is a good sign.

My impressions regarding the latency and availability of Azure Database for PostgreSQL are positive. Overall latency, especially for edge deployment, needs to be very short and very low, and that is what we are getting.

My impressions of Azure Database for PostgreSQL's ability to scale workloads are within what I expected. However, it is scalable up to a certain size and volume. Some of the use cases that I have on edge are simply not possible to do with PostgreSQL given performance requirements, which is why we are exploring other options with Microsoft.

I would rate customer service and technical support at Microsoft an eight out of ten. They have good technical support with no complaints.

Positive

Regarding my experience with the migration process to Azure Database for PostgreSQL, we did not use Microsoft support. We had the skill set in-house, so the migration was relatively simple to execute. We performed it at an application data layer rather than at a DBA level.

Azure Database for PostgreSQL has not helped reduce infrastructure costs.

The pay-as-you-go pricing model of Azure Database for PostgreSQL has actually increased costs. The licensing model that I had before in some use cases was very beneficial and included volume discounts. Once you move to that model, if you do not have it tightly integrated with FinOps, you will pay more.

In comparison to my previous expenses for maintaining an on-premises PostgreSQL database, the costs are higher.

Azure Database for PostgreSQL has not influenced my application development process.

Azure Database for PostgreSQL has not moved the needle in terms of my ability to innovate or stay competitive in my industry.

The integration of Azure Database for PostgreSQL with other Azure services has not impacted my overall cloud strategy.

We continue to share with different clients a positive view of Azure Database for PostgreSQL, and there are use cases for it, but it is not universal. There are other options available. We do have several pilots going on, especially for edge deployment. I would rate this review a nine out of ten.

My main use cases for Azure Database for PostgreSQL came from a personal project to scratch an itch, and it was the easiest one to go grab.

I appreciate how easy PostgreSQL is to get running locally. You can grab a container and run it, as opposed to the old days when having a local database was very challenging and required special scripts that would take hours to run. Now I can grab a container and be good to go in seconds, which makes life a lot simpler and has influenced my application development process.

My experience with the monitoring and management tools provided by Azure Database for PostgreSQL has been minimal, but the ability to see what's there and tweak it is a good feature to have.

Azure Database for PostgreSQL security features such as encryption and advanced threat protection are very helpful, especially when you have medical data and personally identifiable information that you need to protect. The fact that these security features are embedded certainly makes my job easier. The ability to encrypt personally identifiable information and health data at rest is what my company finds most valuable.

Azure Database for PostgreSQL integration with other Azure services has impacted my overall cloud strategy. Depending on the customer, having it there and having it be easy to utilize, with the ability to switch to it, is valuable. I have conversations where customers are using one data store, but maybe that's not the right data store and perhaps another should be used instead. The fact that you can do this with such a low barrier of entry makes it simpler to have those conversations. It isn't a situation where you have to hire somebody who knows how to stand this up; you just click and now you have that data store.

Azure Database for PostgreSQL integrations have been most beneficial to my operations with Azure Kubernetes Service and Container Apps. The different eventing systems provide another valuable conversation point about which of the three different eventing systems should be used. The different tiers available allow you to think in terms of crawl, walk, run. You don't have to go straight to the heaviest duty enterprise level until you need it. When you're just getting started and trying to find market fit, you can use something simpler that gets you up and running with some training wheels and fewer knobs you need to worry about. When demand requires it, you can graduate to the next tier up.

Azure Database for PostgreSQL has helped reduce infrastructure costs depending on the client.

Azure Database for PostgreSQL can be improved in ways I'm very curious to explore with Horizon. I'm interested in seeing how the fully enterprise-hardened features change things and where that blurs the lines with other data stores available on Azure, as that will probably make it harder to choose between solutions.

I've been working in my area of expertise for almost thirty years.

Compared to my previous expenses for maintaining an on-premise PostgreSQL database, Azure Database for PostgreSQL is far easier, far simpler, and far cheaper in my opinion. Having to maintain staff whose job is the care and feeding of the database and the time it takes to get a local version spun up for somebody was a burden. Being able to do that with some clicks is a huge win. Additionally, you don't have to worry about whether it's up to date, because it always is.

I have previously used an on-premise database.

Azure Database for PostgreSQL has influenced the adoption of artificial intelligence technologies in my company. Artificial intelligence is definitely in almost every conversation that happens these days. The clients I've worked with haven't used it yet, but it's at least in the air. That's another thing that will eventually have to tie in, depending on the customer.

Azure Database for PostgreSQL has had a significant impact on my company's data protection strategy compared to previous solutions. Not having to manage it yourself is a huge win. You can shift that responsibility to someone else who does it at scale and can hire the best people in the world to do it. It's one less thing that you need to spend cycles on, so it's just an overall win.

My experience with the migration process to Azure Database for PostgreSQL, particularly in terms of the technical expertise required and support received from Microsoft, is generally straightforward as I've seen it. It helps to have people who've done it before and know the pitfalls and can help you speed things up, but by and large, it's a fairly straightforward proposition. How much data you have does matter for the timeline.

I would rate Azure Database for PostgreSQL overall a nine out of ten, and we will see how the Horizon offering works.

My advice to other companies considering Azure Database for PostgreSQL is to choose the data store that makes sense for your use case. I've noticed a tendency to just grab whatever database was used last time, but maybe that's the right choice and maybe it's not. I've seen instances where people choose a data store because they think it's cool or they want to play with it and put it on their resume. Resume-driven design is a real thing. Make sure the data store you choose is the right one for your use case. If you're doing microservices, you don't have to have one-size-fits-all. If a service needs a time series database, then use that. If a service would benefit from graphs, then use graphs. Use the data store that fits your needs.

My main use case for Azure Database for PostgreSQL is managing MIS data and dashboard creation for the organization. I use Azure Database for PostgreSQL to create dashboards, generate MIS, and prepare and share MIS for resources.

I have been using Azure Database for PostgreSQL for the past two years, and I have not encountered any issues with it; it is smooth and time-saving.

The best features that Azure Database for PostgreSQL offers include generating reports with low time consumption and being time-saving. When I say it is time-saving for generating reports, it speeds up my work because pulling data from Power BI and collecting data through Microsoft Office and advanced Microsoft tools is very easy, and Azure Database for PostgreSQL delivers reports quickly.

Regarding the features of Azure Database for PostgreSQL, the reliability is very good and integrity is also good for using current database services.

Azure Database for PostgreSQL has positively impacted my organization through collaboration. It has helped with collaboration by allowing me to send the MIS database, such as generating a report within a second and sending the MIS for an employee or a team, making it very easy to display for business purposes.

I have noticed faster decision-making since using Azure Database for PostgreSQL, as it provides a faster decision-making process.

All features of Azure Database for PostgreSQL are good. No improvements are needed, as everything is good and the business is running fast.

I have been using Azure Database for PostgreSQL for the past two years.

Azure Database for PostgreSQL has not influenced my ability to innovate or stay competitive in my industry, as everything is good and the business is running. There has been no change in my organization's database uptime after implementing Azure Database for PostgreSQL.

Azure Database for PostgreSQL is deployed in my organization as on-premises and hybrid cloud.

My experience with the monitoring and management tools provided by Azure Database for PostgreSQL is good.

My experience with the migration process to Azure Database for PostgreSQL has been good; whenever I required assistance, the Microsoft team helped me quickly.

This migration to Azure Database for PostgreSQL has been good with no issues reported.

Compared to my previous on-premises database, Azure Database for PostgreSQL is good, and PostgreSQL is better compared to other platforms.

Azure Database for PostgreSQL is deployed in my organization as on-premises and hybrid cloud.

We use AWS as our cloud provider for our hybrid deployment.

We purchased Azure Database for PostgreSQL from the AWS Marketplace.

The pay-as-you-go pricing model of Azure Database for PostgreSQL has not negatively impacted my database-related costs and resource allocation; it is good and there is no issue with that.

Azure Database for PostgreSQL has not influenced my application development process currently; if it is required, I will definitely collaborate with them.

I have not noticed any changes in time-to-market for my applications since using Azure Database for PostgreSQL.

I rate Azure Database for PostgreSQL a ten out of ten.

I give it a ten out of ten because Azure Database for PostgreSQL is providing a response quickly and generating reports faster, with good reliability and very low time consumption.

I think the governance and security of Azure Database for PostgreSQL's AI capabilities are good; I cannot send data outside of the organization, and Microsoft is very strict.

The accuracy and reliability of output from Azure Database for PostgreSQL are good.

The integrations that have been most beneficial to my operations include Power BI and Microsoft Office.

My impressions of Azure Database for PostgreSQL's security features, such as encryption and advanced threat protection, are that Microsoft security is the only feature I find most valuable.

Azure Database for PostgreSQL has facilitated the adoption of AI technologies in my organization's database operations; it is good and everything is perfect for the current organization and database.

Azure Database for PostgreSQL's integration with other Azure services has impacted my overall cloud strategy for generating MIS reports, creating dashboards, pulling data from Power BI, and arranging data through advanced Microsoft tools; it is good.

Azure Database for PostgreSQL is deployed in my organization as on-premises and hybrid cloud.

I would rate Azure Database for PostgreSQL a ten out of ten.

My main use cases for Azure Database for PostgreSQL are to use it as data storage for a lot of apps, involving different app services, functions, and other platforms, where we bring in and process a lot of data for integrating different cloud platforms. We have document management systems where we're pulling back-end data from on-premises systems or other cloud systems, using many Azure functions and different app services to pull data through Azure Database for PostgreSQL to track and sync with other systems.

Azure Database for PostgreSQL has influenced my application development process by enabling me to take some of what we used to do on-premises, with PostgreSQL hosted in virtual machines, and transition that process into a SaaS solution. This transition means we don't have to spin up a virtual machine for installation and configuration, streamlining the process and making it faster and allowing us to script much of it out, so whenever our developers need a new environment, it's just a couple of clicks and an automation, resulting in a consistent build every time.

The impact of moving to Azure has been significant; we can take what was already built on-premises and split it into services without needing to build a whole server, making the deployment much lighter, faster, and scalable.

My favorite feature about Azure Database for PostgreSQL is that it's quick and easy to set up and deploy, without a lot of overhead or configurations, making it fast and easy to include in any of our builds. When we automate for scaling up or scaling out, it's easy to do that automation side of it, and since it's PostgreSQL, it's lightweight and simple for the basic things we need to do from a data perspective, so it works well.

A benefit that Azure Database for PostgreSQL has for my company is that it serves as a native back-end solution for several utilities and tools that we use, making it a quick and easy solution that we deploy as part of larger problems or solutions. This capability helps us scale economically because we're often reselling these solutions, keeping our costs down and making deployment and rollout easier.

My impression of the security features in Azure Database for PostgreSQL, such as encryption and Advanced Threat Protection, is that it has met all of our security requirements; anytime our apps go through a security review, we've never had any issues while using identities and registering the app. It has been great, trusted, and it works without needing extra security reviews for implementation.

Regarding improvement in Azure Database for PostgreSQL, I would have to discuss that specifically with our lead developers.

I have been using Azure Database for PostgreSQL for approximately seven or eight years.

I can assess the stability and reliability of Azure Database for PostgreSQL as excellent; we have no issues or problems with it. Occasionally, we experience throughput issues due to bandwidth limitations of client setups with Azure, which have limited connections, but as far as the service itself goes, it has been rock solid.

In some ways, Azure Database for PostgreSQL has facilitated adopting AI technologies in my organization, mainly because we can take output from AI processes, particularly document and contract summarization, and dump that data into a database for later retrieval. We are only beginning to experiment with this and hope for more native solutions within the AI tools, which are now coming, and PostgreSQL has allowed us to lay the groundwork for this. I rate this product a 10.

We are an insurance company with many applications that handle policy processing, so we use Azure Database for PostgreSQL for those applications. We have different usage for every database, and for all of our in-house applications, we use Azure Database for PostgreSQL.

We have monitoring for Azure Database for PostgreSQL. Our on-premises monitoring is connected to LogicMonitor, which we use as a centralized monitoring tool. If a database has any task that has been interrupted or any connection issue, it will alert LogicMonitor, and we have a centralized panel for all the alerts.

Regarding Azure Database for PostgreSQL security, I have not received any report or incident indicating a breach to our database. However, I cannot definitively say this is because of Azure Database for PostgreSQL or our overall security ecosystem.

I am not certain if Azure Database for PostgreSQL helped reduce infrastructure costs because we are in the process of migrating to the cloud. Our on-premises cost and on-premises infrastructure cost is fixed, and we pay an annual fee to the data center. Once we migrate to Azure, I could check the cost bill, but I have not yet. This is not my main responsibility. The management definitely did an estimate, and I think it will probably save some money for them, which is why they chose to migrate. That is my assumption.

I am not a DBA, so for my experience with Azure Database for PostgreSQL on the database side, I do not know if it has certain capabilities. The most significant thing I do and communicate with our DBA about is performance tweaking. I think we still have to do it regardless because you still build on a server with the OS level on it. I do not know if in the future the database will have its native OS layer instead of using Microsoft and dynamically assign the CPUs and memories based on the transaction or task it is running. This could save us some time so it does not have to use sysadmin's time to constantly tweak and assign the CPU. Currently, most databases will try to use all the CPUs available and use all the memories available. We try to give all the databases one hundred percent of the hardware capacity, but sometimes because the OS layer itself will need some resources. If the database used everything, when we try to remote to it, sometimes you will just see a black screen. If we can make this better, why not?

On the deployment side of Azure Database for PostgreSQL, it is easy to deploy. The deployment of Azure Database for PostgreSQL is pretty straightforward, and there is not much to specify. It is very basic. Usually I will work with the DB team, they will give us all the instance, all the SSA, and all the accounts. We basically deploy, install it, and deploy it.

The deployment of Azure Database for PostgreSQL usually takes one hour for us to deploy it. I do not know if the deployment time for Azure Database for PostgreSQL is similar to other solutions. For MS SQL, I think it is also the same amount of time. For AWS, I cannot say because it is a cloud team thing, and I deploy on-premises.

I am the admin part, so I basically deploy Azure Database for PostgreSQL. I do not actually directly use the product, but I do the deployment.

I cannot say much about the features of Azure Database for PostgreSQL because I am not the actual user and just do the deployment.

Azure Database for PostgreSQL has influenced our application development process, which is the reason why we stick with Azure Database for PostgreSQL. Otherwise, we would not use it as heavily. Our company's strategy is always to not put all eggs in one basket. We have Azure Database for PostgreSQL, MS SQL as well, and some AWS databases. We have all kinds of DB and also MongoDB.

For our solution using Azure Database for PostgreSQL, I have never gotten any complaints from any incidents, security incidents, or any technical troubles. It is very rare, but incidents are code-based and not database-related. We have some code-based incidents because the application has some bugs, so we have to fix them. Based on the database itself, the most tweaking we did was the performance. We have to monitor the performance of all the transactions and all the journals, and we have to do tweaking such as determining how many CPUs and memory we have to reassign to those servers and applications. That is the only thing that we actually deal with. The patches happen on the Windows server side because we use Microsoft servers. Most of the patches happen on the Windows server side, though we have Linux servers too. When Microsoft releases some patches, it will sometimes interrupt some connections, but it is not a PostgreSQL issue and is just a server issue.

We are a hybrid environment including our on-premises AD. We are in the process to migrate and try to get rid of our on-premises AD and completely use Entra as our main identity management solutions. Currently, we are hybrid and everything is Microsoft. We also use Okta as well. We have Okta and Entra. The hybrid arrangement has its advantage because it really connects our old legacy technology. Everything has to be on-premises because we have not had time to completely convert it to cloud apps yet. The hybrid approach creates a bridge to both worlds. A native cloud approach actually has more advantage because it is easy to deploy, faster to deploy, and easy to recover and roll back. It is more agile and more convenient for us. It really shortens the time for us to deploy on-premises. When you try to deploy something on-premises, especially when a new product comes in, you have to get the hardware, set up all the firewall rules on-premises, and then deploy all the applications on those servers. Because we moved to AWS and moved to Azure, everything is basically just policies, and you can define everything in the cloud. It is way faster and more convenient for us. I gave Azure Database for PostgreSQL a rating of nine.