TrustRadius Insights for Azure SQL Database are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Reliability and Accessibility: Users consistently praise Azure SQL Database for its constant availability, emphasizing its reliability and ease of access. They find it reassuring that the platform is always accessible when needed, ensuring uninterrupted workflow and data access.
Ease of Use: Reviewers commonly highlight the simplicity in creating data models and managing databases with Azure SQL, making these tasks straightforward and user-friendly. This ease of use streamlines their workflow, simplifies database management processes, and allows them to focus on more critical aspects of their work.
Integration Capabilities: Many users appreciate how easily all their applications connect with Azure SQL Database, enhancing usability and integration possibilities. This seamless integration allows for efficient collaboration between different tools within their ecosystem, promoting a cohesive working environment.
We use it globally across all member firms for Enterprise solutions. It's the back-end for corporate applications and going forward analytics.
Pros
Agility of the platform
No infrastructure maintenance and worry about upgrading, it's managed.
Always on and universal availabilities
No worry about backup recovery
Cons
PowerBI connectors need improvement across 365 platform
Data bricks can be inherent feature
More robust integration to flow
Likelihood to Recommend
It's well suited for enterprise applications, as development to implementation cycles are shortened and less risky. The Azure platform and ARMs are our favorite now for budget and time.
Azure SQL DB is a great service. It optimizes licensing cost and lets you pay per usage. You can grow as needed and it supports from small to large databases. Be aware it can require some networking/security steps to have it in large or more controlled environments.
Pros
It optimizes cost - pay per usage. It can scale up and down as needed.
It can be migrated to from Oracle, MySQL and other on premises databases.
It is always updated with management and administrative functionalities being added weekly.
Cons
Migration from on premises databases can be painful at first - but after couple of migrations it becomes easy.
Network capabilities and restrictions should be carefully evaluated.
It can be costly if you don't implement scale up/down automations.
Likelihood to Recommend
For large databases cost should be carefully evaluated as it can be very expensive. But for medium and small databases (usually 80% of the organization) it has perfect fit. Data replication (for disaster recovery), backup, security and performance recommendation are great tools and work very well. When planning to migrate from Oracle, start first with smaller databases - but be aware Microsoft is always improving its migration tools.
VU
Verified User
Analyst in Information Technology (Mining & Metals company, 10,001+ employees)
We had acquired a new casino and the move for them to be on our domain was TBD. We did, however, need data from some of their systems. Since they did not go through a full security evaluation yet, we were not willing to allow access to their end. As a solution, we implemented Azure SQL Database so we could push the data to the cloud, to then access it on our end. We would have the data without having to directly access their end from our domain.
Pros
Scales easily
Performance is solid
It just works
Elastic pools are great
Cons
It would nice to have Azure SQL Database provide closer to full support of T-SQL
Cross database queries
More performance reports would be nice
Likelihood to Recommend
It would perform great in a SaaS scenario. You could use elastic pools to manage multiple databases.
VU
Verified User
Engineer in Information Technology (Gambling & Casinos company, 10,001+ employees)
Azure database is currently used by a specific department at my organization and we mainly focus on auditing and monitoring so it pretty much serves our purpose and most importantly it is easily secured with firewall and DNS resolutions. Migrating databases is no more a hectic task from shifting a large scale database to a more managed engine.
Pros
The great thing about is even you are a pro or a newbie with Azure, you will not be tired of setting up SQL Server, the befitting pipelining of AZURE to cloud service where you don't need it onsite.
You always don't need to update services, patches and deployment of supporting services. Cloud does make it someone else's job to do this.
Generally obviates the need for building high availability architectures; Azure databases built within it are automatically highly available.
Highly scalable and has vast support for non Microsoft technologies.
One of the ways SQL Azure manifests being part of the whole stack is by offering multiple levels of implementation. If you simply need a website and a database, you can hitch an SQL Azure instance to an Azure website and be done with it.
Cons
No schedulers available in case you require cron jobs.
Certain username are not allowed (root, admin, administrator).
Likelihood to Recommend
Sync and migration tools: If you already have a clutch of SQL Server-stored data somewhere and want to either sync it with SQL Azure or passively migrate it via sync, Microsoft has published a service -- the appropriately named SQL Data Sync to accomplish this. Use of the service itself is free, and all inbound data to Azure costs nothing, so you won't have to worry about racking up costs by syncing gigabyte-sized tables.