Salesforce Lightning Components & Developer Experience vs. Azure SQL Database

If you have a large customer base and a large amount of data on each of your customers, it is really strong in creating personalized content that your salespeople can use in their pitch meetings—and then setting up workflows for automated for lifecycle journey creations to automatically go out to customers.

Incentivized

We have found it's a great alternative for making older legacy applications work with online databases instead of only on-premises databases. We've converted over a dozen applications this way, and it has allowed our clients to have a distributed workforce using their applications without incurring the expense of a complete application rewrite.

Incentivized

• It has a very smooth integration with Salesforce and third-party tools, ensuring easy tracking of policies and assets.
• It also has impressive security features like used-based permissions and encrypted data.
• Everything can be managed from a centralized place which saves a lot of time.

Incentivized

• Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
• On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
• Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.

Incentivized

• It takes a while before it recognizes bounced emails.
• We get so many notifications from a single action. Not sure if this can be modified in the settings though.
• Error messages are sometimes unclear which makes it hard for us to identify the problem.

• One needs to be aware that some T-SQL features are simply not available.
• The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
• No SQL Agent so your jobs need to be orchestrated differently.
• The maximum concurrent logins maybe an unexpected problem.
• Sudden disconnects.
• The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
• Only one Latin Collation choice.
• There is no way to debug T-SQL ( a big drawback in my point of view).

Incentivized

This is best solution as a DBA one could expect from a service provider and as a cloud service, it removes all your hassles.

Incentivized

It's very good, but it's still living in a little bit in an older design aspect, but I think a lot of it is about to come out, just hasn't quite gotten there yet. Still a little clunky from a you have to know it to know it or you know it to use it. It takes a little bit of training to get into it. It's not quite the, anybody can come in and start using it immediately, type feel.

Incentivized

The interfaces are intuitive once you are familiar with all the functions. The ability to use different tools to interact with the platform, such as directly via a browser or code editors such as VS Code or Visual Studio is a great option and allows for integrating withn the project and other testing and developing tools.

Incentivized

I am not an administrator so there may very well be outstanding Support and I am just not privy to it. On a user level it's hard to gauge the effectiveness and responsiveness of Support because nearly everything has to go through an administrator

Incentivized

We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.

Incentivized

We were previously using an older version prior to it becoming Salesforce Lightning Platform so we were well adverse on the advantages of using a CRM, to begin with. It made sense to convert to Salesforce Lightning Platform after we were given a free trial of the platform. Certain reps were chosen to experiment with it and from there a decision was made to move forward. We've been customers ever since.

Incentivized

We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.

Incentivized

• Better visibility of Accounts and Contacts interactions makes it easier to maintain during employee transitions.
• Tracking of current jobs and relating them to past jobs is very useful.
• More efficient use of Sales Reps time.
• Sales Managers have good visibility into how their people are working.

Incentivized

• Perfect for small and medium databases, being very cost effective.
• As a Platform as a Service, there is no concern about patches, upgrades and end of life.
• Be aware of security and network capabilities. The service cannot run in the VNET as Azure Virtual Machines do.