What advice do you have for others considering SQL Azure?

I am currently looking into transitioning legacy systems to Microsoft Azure SQL Database to perform an on-premises migration from SQL infrastructure to Azure SQL. In this particular use case with Microsoft Azure SQL Database, it actually moves many of the hurdles away. Hosting these types of databases on-premises can be challenging, but if you have the ability to do it on Azure, that is beneficial, and it also removes security obstacles as well. I have no comments on anything they can improve on, change, or any additional release I would like to see. I would rate this review an eight overall.

Use the tools that Microsoft provides to assess your current environment if you are considering using Microsoft Azure SQL Database. I would rate this overall review as a nine.

I would assess the effectiveness of Microsoft Azure SQL Database security features in meeting compliance standards as currently pretty open, as we are just implementing policies for the database. We have not really gone into much of a compliance standard. Right now, it is an open network. We do plan on doing that in the next few months. The compatibility with SQL Server for transitioning legacy systems to Microsoft Azure SQL Database is important, but I got in when it was already established, so we did not really migrate much. Therefore, I cannot really speak to the migration. From their end point, I think they have mentioned that Microsoft Azure SQL Database is pretty efficient to use. It is pretty easy to manage as well on their end. Being straightforward is something that works well, and I did not face any challenges. Mostly it is documented, so it is pretty easy to do. My advice to another organization that is considering Microsoft Azure SQL Database would be that if they are on cloud, there are many options, but they should explore their options and see what makes more sense to their customers. Our customers really did not have a vision for anything else other than SQL, and they have also used it before, so it was easier for them. I would recommend exploring options and if it makes sense, going for it. I would rate this review a nine out of ten.

I would rate Microsoft Azure SQL Database as a five on a scale from one to five in terms of ease of use. I assess Microsoft Azure SQL Database's ability to integrate with other Microsoft applications as excellent, with no complaints. I have not had hands-on experience with Microsoft Azure SQL Database working with AI. I know that functionality exists, and part of what I am trying to focus on at Ignite this year is learning how I can integrate different AI solutions and workflows with Microsoft Azure SQL Database. I am not using the automatic tuning feature in Microsoft Azure SQL Database. I do not know what impact Microsoft Azure SQL Database's security features have on my data protection strategies, if any. I am not using the data encryption feature on Microsoft Azure SQL Database, or at least not knowingly. I have not used the backup and restore functionalities of Microsoft Azure SQL Database. Our database engineers have touched that before, but I have never used it. It seems to work as intended. We are still using other solutions alongside Microsoft Azure SQL Database. My advice for other companies that are considering Microsoft Azure SQL Database is to go for it, especially if you are using other Microsoft products. It seems to integrate with everything very well, and it just works. I have rated this review a nine out of ten overall.

We are exploring the usage of AI in our company. I think Microsoft Azure SQL Database has a place in that AI environment. I do not know about Microsoft Azure SQL Database's ability to power next-generation AI applications since I have not used that feature, so I only have information from the marketing slides from Microsoft and the sessions, but I have no real experience. I use the native backup option and have experience with the backup and restore functionalities. It works so far. I assess the reliability in terms of maintaining uptime and availability as good. Microsoft's expertise in SQL Server is not important to us when considering cloud database options. My advice for other companies thinking of getting Microsoft Azure SQL Database is to use it. They should start with a proof of concept and a test environment, and then if it is successful, roll out to the production environment. I would rate this solution an 8 overall.

I would give this review an overall rating of eight out of ten.

My advice to other companies considering Microsoft Azure SQL Database is to try it and realize how much it alleviates the burden of managing SQLs, especially since something typically goes wrong in critical situations. Azure SQL significantly reduces the number of failures, and I'd recommend using Azure Migrate to assess databases and test with the first solution, even checking pricing as you might be pleasantly surprised; it's a really worthwhile solution. I would rate this review an eight out of ten.

I would not know if Microsoft Azure Active Directory integration and Azure Key Vault have helped manage data security; I believe our data engineers would have that answer. The compatibility with other SQL servers for transitioning legacy systems to Microsoft Azure SQL Database is probably moderately important, as they need something to work with. If it is something they need to learn, it is not the end of the world, but the less they have to onboard different systems, the better. My data engineers would have better examples of how the features of Microsoft Azure SQL Database have benefited our organization than I would. One thing I plan to do in the next year with Microsoft Azure SQL Database is create more of a sandbox and testing environment and maintain consistent refresh data between the two. Currently, we refresh monthly, which is insufficient for my testing needs and for training and onboarding. In the next year, we plan to establish a more streamlined workflow to create sandbox and test environments. The advice I would give to another organization considering Microsoft Azure SQL Database is to evaluate what is most important to the organization and determine if it aligns with what Azure provides. Our company is fully committed to Microsoft, which is fortunate, but the key is to understand your actual needs; if you want more control and more ownership of the system, that is not necessarily the value proposition of this service. We want you to maintain it for us and manage everything for us, so I would recommend creating a thorough list of requirements. I would rate this product a seven overall.

My advice for other companies considering Microsoft Azure SQL Database is to understand their database requirements and, if they have a larger data size, to consider Managed Instance before committing to SQL Database. I rate this product a nine out of ten.

Microsoft Azure SQL Database is not being used to its full potential. Having a good amount of database engineers was probably one of the reasons for not using it to its full capacity. If your data is not reaching your application, what is the value of that data? My user misbehavior has less impact on my uptime and data flow. I might not know what will come or what will not come. However, because I am on Microsoft Azure SQL Database, I have better capability and better options than to go down. Definitely, if I compare it with my old days on premises, it is superior. The comparison from my IaaS implementation to PaaS implementation clearly shows the advantage. I would rate this review a 9 out of 10.

The decision to migrate was indeed a manager's decision, but he's not even there anymore. We're still moving; I'm still seeing what's available because it's caused some headaches. Now that that manager isn't there, who knows? We might be able to have another conversation about staying with Microsoft since we already have the account. There definitely were some challenges in the migration. The impact of Microsoft Azure SQL Database's security features on my data protection strategies is limited, as I don't work with security often. I'm not using the new feature of data encryption in Microsoft Azure SQL Database since that's also not my primary role. I have some experience with the backup and restore functionalities of Microsoft Azure SQL Database, but it's very minimal. We do our daily backups using Microsoft Azure SQL Server. My impression of its backup functionalities and restore functionalities is that we haven't had to restore, so I don't have much of an impression or any feedback to give on that. Backups run smoothly, and we haven't had any issues or failures with any of our backups so far. I would rate Microsoft Azure SQL Database as a seven on a scale of one to ten. I'm giving it a seven because it's something that I'm familiar with, and it's easy for me to work with. What would make it better would be expanding the support for different data types; I think that would be a big thing for me because right now, being able to support geography data types is important for our company. We work in land and building homes, and we are trying to use more geographical data to help us pinpoint good places to help build homes.

Our impressions of Microsoft Azure SQL Database's ability to power next-generation artificial intelligence applications are that we are still identifying those capabilities, as we are still learning because it is a new area which we have to explore.We are using the automatic tuning feature in Microsoft Azure SQL Database. Although I have not been in touch with the database administrators, they told us about a year ago that it is easy to use on a day-to-day basis. They are satisfied with how auto-tuning has made their jobs easier because they do not need to struggle to get a fix deployed, and they know when to deploy it specifically for non-production and production databases. Data encryption is a by-default requirement for us in Microsoft Azure SQL Database as it is a policy. I do not know of any impact that the automatic tuning feature has had on our data security strategies. My experience with the backup and restore functionalities of Microsoft Azure SQL Database is limited, as this is handled by the database team. I understand that feedback will go somewhere and possibly lead to changes, but I do not have much to add on this issue. My overall rating for this product is nine out of ten.

The benefits I have realized from using Microsoft Azure SQL Database are currently limited since we've only done it in test and dev environments right now, and we haven't moved to production, so we haven't realized the full gain just yet.In terms of ease of use, I assess Microsoft Azure SQL Database as easy to use; it's just the migration of our database that presents a few challenges that we're having to change as developers, but it's a process we're getting through. My impressions of Microsoft Azure SQL Database's ability to power next-generation AI applications are still developing; we are just now dipping our toes in AI, and we're probably still a year or two away from integrating it fully, so I don't know much about its capabilities on that front just yet. I am using the automatic tuning feature in Microsoft SQL, and it's a great aspect of the platform. The primary reason I want to reduce the cost of ownership with Microsoft Azure SQL Database is that it offers more flexibility regarding scaling, and it fits our product better than what it is today versus what it was 20 years ago with the same back end that we had. During the migration or implementation of Microsoft Azure SQL Database, I didn't really find any challenges; as far as Microsoft Azure SQL Database itself goes, there are some database changes to manage, but there are really no issues with SQL to begin with; it works for us, and we have a team that manages it, so it's a good spot for us. Microsoft's expertise in SQL Server was very important when considering cloud database options; our database is legacy right now with the way it's designed, so we're still moving towards Microsoft Azure SQL Database. There are a lot of steps to get there, but we are making progress. Regarding Microsoft's expertise in SQL servers and databases, we haven't really leaned on them much yet; we've got a developer team of about 21 or 22, and they're pretty good with SQL, but we haven't had to reach out. I would rate Microsoft Azure SQL Database overall as a solution and a database at a nine on a scale of one to ten. A nine is my rating, and what would make it a ten for me is maybe cost, as cost can always come down, and that's always a factor.

My impressions of Microsoft Azure SQL Database's ability to power next-generation AI applications are that it's getting there; it's not as good as Cosmos DB right now, but we're seeing significant improvements in Microsoft Azure SQL Database space. My experience with the backup and restore functionalities of Microsoft Azure SQL Database is that they are very straightforward and easy to use. My advice for other companies that are considering Microsoft Azure SQL Database is that it's a great opportunity to reduce on-premise dependencies; it's an easy lift and shift to a modern platform. If you're looking for a way to begin your cloud adoption journey and start making an adoption move, Microsoft Azure SQL Database is a great way to start. I would rate this product a nine out of ten.

I'm not using the Automatic Tuning feature directly. The biggest benefit from Microsoft Azure SQL Database is that we are choosing to use an Azure VM, where we are using our own database instead of using SQL Server; we have migrated from Microsoft Azure SQL Database to our internal SQL database. I don't think there are any features left to add to Microsoft Azure SQL Database; I see everything is there. All self-documentation is okay; I have no concerns about this. The review rating for Microsoft Azure SQL Database is 9 out of 10.

My client does not use Amazon services at all, including the Azure Data Box. I am not familiar with just the Data Lake Storage because we are just using the SQL Server database, not the other products that are supposed to be dedicated to this kind of use of a data lake. The Microsoft Azure SQL Database is not the latest version of Microsoft SQL Server. It's a really old engine that does not have the newest features. It's very slow and too expensive. I really don't think it's a good solution for most cases, except when you specifically need to put your data on the cloud. The client is already planning to move back on-premises because it is not working well in terms of performance. Now that we are starting to move big volumes of data, the system starts to slow down. Queries are slow, and the performance is impacting the application. On a scale of one to ten, I rate this solution a six.

I advise users to adopt Microsoft Azure SQL Database, as it simplifies life for users and applications. Applications can connect from anywhere, and it reduces headaches for administrators and infrastructure teams. The disaster recovery plan and backup features are easily enabled. The overall rating is nine out of ten, considering pricing concerns.

On a scale from one to ten, I rate the overall product an eight.

I rate Microsoft Azure SQL Database 10 out of 10.

I'd give Microsoft Azure SQL Database a nine out of ten.

I rate Microsoft Azure SQL Database nine out of 10. It's still missing some features, so I deducted one point.

I rate Microsoft Azure SQL Database nine out of 10.

I would rate the overall solution between eight and nine, as it covers the majority of our needs and competes better than most other databases we use.

I would rate Microsoft Azure SQL Database a nine out of 10.

I would rate Microsoft Azure SQL Database nine out of 10.

I would recommend Microsoft Azure SQL Database to others. For the price, you get an excellent balance of features and performance. I would suggest exploring AWS, although I am not familiar with its setup or the feature-to-price ratio.

We use the solution to store not really big data, and the database is less than one gigabyte. The solution's integration with other Azure services is easy because it just needs a connection string to connect. SQL Azure is deployed on the cloud. Users who can afford its price should use SQL Azure because it reduces setup time. Since it is a stable solution, you do not need to spend time to maintain it. Overall, I rate the solution an eight out of ten.

I rate the overall solution a ten out of ten.

The automated scalability feature of SQL Azure has proven to be highly beneficial, particularly when deployed in the cloud. It can be done remotely, eliminating the need for manual intervention. However, it may become more challenging if the infrastructure reaches its limits, especially in vertical scaling scenarios. Whether opting for AWS or Azure, the service offers guaranteed uptime, often around 99.9%. Additionally, it supports deployment across multiple zones and regions. The transition from on-premises to SQL Azure can impact operational costs depending on the setup. It offers options like pay-as-you-use or dedicated services running 24/7. However, it's essential to evaluate your business case thoroughly before deciding. I rate it an 8 out of 10.

As it is a database, price quantification is a little more complex. I think it is essential that some questions are asked?

1. Do you already have SQL Server licenses?

2. Do your licenses have software assurance?

3. Are you gonna use Servless or provisioned computing?

3. Do you need a local or zone-redundant database?

4. Yoy need backup storage?

5. What kind of long-term retention do you need?

Given these answers, you go to the Azure calculator:

https://azure.microsoft.com/en...

Please note that if you choose to pay 3 years in advance, you can get a discount of up to 70%.

There are other questions that need to be answered to have a more accurate value.

I would highly recommend it. Overall, I would rate it nine out of ten.

Overall, I would rate the solution a nine out of ten.

I would rate the overall solution a nine out of ten.

The affordability of the solution allows for the swift and effortless creation of proof of concept projects to determine if it is suitable for their needs. SQL Azure has all the enterprise features I need. To create enterprise solutions for a fairly good price point. I rate SQL Azure a nine out of ten.

I rate SQL Azure a nine out of ten.

AWS secured much business in Pakistan because of RDS for Oracle. There is not much difference between AWS and Azure’s prices. AWS and Azure differ in price by a few dollars. Technically both solutions have different capabilities. AWS has a far better capability. People prefer AD authentication by AWS over Azure. We have Microsoft-certified trainers in Pakistan. We have been asking our customers to choose Azure because they will get a lot of benefits by adopting a cloud solution. Since hardware is not easily available within Pakistan due to dollar disparity, a lot of people are choosing Azure. We have been pushing Azure very aggressively for the past four to five years. People continue to implement the solution despite policy challenges. One of our customers wants to host nine to ten applications on Azure. There is a lot of demand for AWS and Azure. Overall, I rate the solution a nine out of ten.

One should be clear about their reporting environment. For instance, Microsoft ecosystem reporting supports only Power BI. Secondly, one should ensure they utilize more customization options than already issued. I rate the solution as eight. It is a familiar product for users who already work on Microsoft environments. If you need a limited cut-down version, it also has an option for a single database.

SQL Azure is a cloud-based solution. We usually require one or two people to deploy and maintain the solution. I would recommend SQL Azure for other people who don’t want to manage their environment. The worst thing about Microsoft is that it has a very bad license agreement that nobody understands. Overall, I rate SQL Azure an eight out of ten.

I give the solution a nine out of ten. Maintenance is minimal and can easily be done. I suggest researching the solution on Microsoft.com where there is a good learning platform before using the solution.

The following are some benefits of utilizing SQL Azure:
Scalability: 

When your company demands change, SQL Azure makes it simple to scale your database up or down.
Security: To ensure that your data is shielded from unauthorized access, SQL Azure has strong security measures.
Reliability: Several replicas of your database are stored in various locations, giving SQL Azure a high level of availability.
Ease of use: SQL Azure is easy to set up and use, with a user-friendly interface and comprehensive documentation.

Some tips and advice for using SQL Azure include:

Choose the right pricing plan: SQL Azure offers different pricing plans to suit different business needs. Be sure to choose the plan that best suits your budget and requirements.

Optimize your database: To get the best performance from your SQL Azure database, you need to optimize it for the cloud environment. This may involve using partitioning, indexing, and other techniques.

Monitor performance: Regularly monitoring the performance of your SQL Azure database will help you identify any issues and optimize it for better performance.

I give the solution a ten out of ten. I don't see anything wrong with SQL Azure. I believe it's actually an advantage because previously we had to install SQL solutions on a physical computer. The good thing is that has been translated onto the cloud and that makes it a very good feature. SQL Azure itself, is a robust application that does a lot and integrates with a lot of applications. The reason I like SQL Azure better is that it's easily accessible and the setup is almost exactly the same as we do on the physical machines, but the good thing is there's no machine to maintain the grid. We selected SQL Azure because it was recommended to us by the safety provider of our accounting software. I recommend the solution to others.

I rate the solution a nine out of ten.

I rate the solution as eight out of ten. The solution is good but can be improved by reducing the constraints on cloud and improving support response times.

We're a Microsoft customer. I'm not part of the development team. I'm not sure which version our company is on. I'd rate the solution six out of ten. While it's fine for use online, we'd like it to be more mobile. If it were on mobile, I would rate it higher.

I give the solution a nine out of ten. In some cases, our customers need to move forward with their SQL projects and when they try to budget in the Azure pricing calculator some costs appear that in the production environment are very different. This becomes problematic for customers when they use SQL Pass services. We are an IT company, so I'm an architect for that company using Azure solutions. Many users in many companies use SQL. I estimate maybe around 1,000 final users and technical staff from each company are using SQL Azure.

I'd recommend the solution to other users. Based on the experience I've had, I would rate it seven out of ten.

I would rate SQL Azure an eight out of ten.

I rate SQL Azure eight out of 10. I would recommend it to others depending on their needs. It might be beyond the budget of some companies. Generally, what I like about Azure as a cloud is the analytics you can apply on top of that data. Azure provides a number of high-performing solutions for data science and analytics. The main issue is that you need to build the architecture to create a product that provides value for your customers. It's about imagination and creativity, and most of the tools are there. In my case, ease of use matters because I lack the knowledge to explore more, but our development team could do that easily.

SQL Azure is a really good tool. I recommend using this solution instead of a normal SQL server, its an improvement, I rate SQL Azure a nine out of ten.

I would rate this solution an eight out of ten.

My company is using the cloud version of SQL Azure, so it's always the latest version. There are thousands of people using the solution for business applications. My client is a big company with at least one thousand users of SQL Azure. In terms of maintaining the solution, it's already managed as a Microsoft-managed product, so in that sense, you don't need people to maintain SQL Azure, but for the application database, you need one person for maintenance. My advice to others looking into implementing the product is that if you are building a solution on Microsoft Cloud, you should choose SQL Azure for your data warehouse, database for your application, and your enterprise Data Lake needs. My rating for SQL Azure is nine out of ten. My company is a service company, so it's a partner, a customer, and a reseller.

I would advise going for it and exploring it. We've only dipped our toes in the water. We haven't put any of our main things. We're just toying with a few new applications, and we haven't brought everything across, but I would recommend it. I would rate it an eight out of ten.

I would recommend this solution to others. I would rate it a ten out of ten.

I would recommend this solution to others. I rate SQL Azure a nine out of ten.

I rate SQL Azure a nine out of ten.

Microsoft Azure is something that we are using. We are using Microsoft Azure from the Cloud. It's the public cloud we are using. We use multiple services on Azure, e.g. mDNS, Traffic Manager, Database, etc., depending upon the attributes and aspects. We're using Azure SQL. We have a cloud team made up of 10 people who use this solution, then there are various application teams that also use Azure SQL. At the moment, we have no plans of increasing usage for this solution, but we're open to it. I would recommend this solution to others looking into using it. I'm rating Azure SQL a 10 out of 10.

I recommend this solution and rate it 10 out of 10.

I rate SQL Azure eight out of 10. To anyone thinking about adopting this solution, I would recommend that they first decide what applications they need to migrate to Azure. Then you need to estimate the cost. All cloud vendors charge for incoming traffic, especially Azure, and it costs a lot. Around 500GB of data might cost a few thousand dollars.

I recommend this solution and I rate it an eight out of 10.

I would recommend it. We're very happy with what we have. It is very familiar because of our experience with on-premise SQL Server. If you are used to working with SQL Server, it is a natural progression. I would rate SQL Azure an eight out of 10.

We use the product and we offer it to customers as well. We are planning to move to the cloud in the future. I'd rate the solution at an eight out of ten. Our company prefers SQL Azure. We enjoy its capabilities. I'd recommend the product. Until now, we don't yet have full experience with it and just we just apply it in very small scenarios - just for feasibility and to take some feasibility tests. We have yet to start converging our ERP. We're checking if it's good or available and if it will fit in some scenarios.

I would absolutely recommend this solution to others. If they are going for Azure, they probably don't have a choice. I would advise others to get used to all the options and ideas of SQL PaaS, SQL managed instances, and SQL on VMs. They should get their head around which one is best for their company. They should make sure that it fits their company's vision of where they want to go with their databases because it may or may not be the best solution for everybody. That's why there are a couple of options, so just make sure to select the right one. I would rate SQL Azure an eight out of ten. It is best in many ways. There is nothing better than this from Microsoft from the database aspect.

If you are migrating from older systems, you should know that CLR is not supported in SQL Azure. Data migration can also be a challenge. I would rate SQL Azure a nine out of ten.

I would rate SQL Azure a seven out of ten. It works like any other SQL database, and it is pretty good.

We are partners. We are working on the latest version of the solution. I'd rate the solution at an eight out of ten. I would recommend the solution. There are not many cloud providers. Azure and AWS are some of the top providers. These are the two which compete with each other, and both of them have good services. That said, I would recommend Azure for sure.

I would recommend this solution and we plan to use it in the future. I rate SQL Azure a nine out of ten.

I would recommend this solution to others. I would rate SQL Azure a nine out of ten.

From a commercial perspective, I would rate this solution very low. From a technical perspective, I rate the product an eight out of 10.

I would recommend this solution. If anybody is using Azure Cloud, they should definitely use Azure SQL. Our strategy is to have all our applications on Azure, and we will keep using this solution. We will also be using it for our analytical data mart. I would rate SQL Azure a nine out of ten. It is a good product, and it has all the required features.

I would rate SQL Azure an eight out of ten.

I would rate SQL Azure a nine out of ten.

I would recommend this solution. I would rate SQL Azure an eight out of ten.

It is a good product for any new development or organization. I would rate SQL Azure a nine out of ten. It is working fine right now, and I am pretty happy with this solution.

Using SQL Azure really depends on the settings that you want to deploy, or the amount of money that you want to spend. If you are deploying and thinking that something will grow so that you can align your income to pay per use, then it's pretty good. If you are considering something where your payments or your income is not related to pay-per-use, you may consider using it on-premises during the beginning. It really depends on your settings. Overall, this solution is pretty good. There are still some areas that have to develop, but I would rate SQL Azure an eight out of ten.

I would definitely recommend this solution. It is a very good product, and it is difficult to beat. I haven't got anything that I saw missing in it in terms of features. It is always integrated within Azure and Microsoft Office 365 ecosystems. If there is something that the database can't do, it is quite easy to have another path of the offering to take over. They are almost like AWS. They have so many services that it is really difficult not to be able to achieve things. There is always something or someone. It is just a matter of price. You also have access to the service, documentation, and even the user community. I would rate SQL Azure an eight out of ten.

I would rate SQL Azure an eight out of ten.

I would, of course, highly recommend this solution. You cannot avoid SQL Server or SQL Azure if you are primarily working in the database domain. There are a lot of other databases available in the market, but the ease with which you can do the development and the overall support that you get cannot be compared with any other database. I would rate SQL Azure a nine out of ten.

I would recommend SQL Azure to others. On a scale from one to ten, I would give this solution a rating of ten. Right now, with Azure, we have everything we need. The only problem we have with Azure is regarding the price.

I would recommend SQL Azure. It is a good platform to use, and it has a lot of information, whatever you want. I would rate SQL Azure an eight out of ten.

If our clients are non-Microsoft clients and they have the money, then I recommend Oracle. But for ease of use, scalability, and value for money, I like SQL. I would rate this solution an eight out of 10.

I would rate SQL Azure a seven out of ten. In terms of experience, it is a very good product, but it is a little bit expensive.

We're Microsoft partners. The solution is constantly being updated. We're on whatever the latest version/update is at any given time. We're a consultancy, so we work with a variety of clients and adjust solutions based on their needs. I'd advise new users to take advantage of the documentation on offer from Microsoft. It will really help them understand the solution. Overall, I'd rate the solution nine out of ten.

We're a partner. We have a business relationship with the client. I use a few different versions of the solution, depending on my clients, and have worked with both the 2016 and 2019 versions, for example. I would recommend the product. Overall, on a scale from one to ten, I'd rate it at an eight.

Overall, I am happy with this product and I recommend it. I would rate this solution a nine out of ten.

We're simply customers. We don't have any professional relationship with Azure. I would recommend the solution. It's great. I'd rate the solution nine out of ten. I'd give it perfect marks if the pricing was more reasonable and if they offered better learning tools to guide our staff.

If you're looking for many features in one product with easy usability and UI, then this product is good. You can readily add on features and exploration and all those things. They are adding features all the time so they are creating one large solution, which is like a repository for things like big data and sensors. The SQL Server encapsulates all the requirements. I would rate this solution a seven out of 10.

I would rate it a nine out of ten.

When it comes to implementation, my advice would be to integrate between Microsoft platforms. I will rate it an eight out of ten as I would love to see faster integration.

This is the best product that Microsoft has. It is the same product as a normal SQL server but built on Azure. The management is different, depending on the hoster of the cloud. I would rate this solution a seven out of ten.

I'm currently moving my system onto the cloud. I'm using a hybrid version of the solution. My advice to anyone looking to switch to the cloud is to stabilize the technology and to consider Amazon, Azure, and Google. If you don't have experience in the cloud, you have to consider all solutions and pick the best one for your company. I decided to go with Microsoft Azure because of my past experience. So if you don't have the experience to fall back on, consider all technologies as well as their cost, money, and features. I would rate the solution eight out of ten because of the cost. I'd like it to be cheaper so we can afford to move more of our services to the cloud.

We use the on-premises version of the solution. I would rate it nine out of ten. I would definitely recommend it to an SMB, a small or medium-sized business.

We use the private cloud version of the solution. I would rate the solution nine out of ten. I would recommend it.

I recommend this solution, as long as the cloud environment is suitable. This is a good solution, but from the angle of security, everything can be breached. I would rate this solution an eight out of ten.

The solution is very user-friendly. I would recommend the solution. It's very easy to understand. I would rate this solution ten out of ten.

In terms of advice to others, I would suggest that they make sure they keep the system stable and to not add complexity. I would rate this solution eight out of ten.

We use a few different versions. It depends on the project. We use the S-1, 2, and 3, depending on the customer's requirements. If we compare, for example, the cloud infrastructure and on-prem infrastructure, there are lots of good things about cloud infrastructure because we can scale the product so that every single time when we need more performance, more computing, more storage we can just reach to the higher plan, and we can use it. There is obviously cost reduction because although we still need an on-prem trader for SQL parts, it's not hard like it was in SQL brand because we also had to care about the infrastructure too. Right now, we are concentrating on the software which is good and saves us money. I would rate this solution nine out of ten because it offers a lot, including statistics and other things which are very hard to get from Azure. However, you have to specify what you actually would like to monitor, which is not straightforward.