Users can build custom conversational experiences using Google Assistant’s voice and visual APIs. Take users on journeys through a product, using Assistant’s natural language understanding (NLU) capabilities and developer tools.
I'm in a Me vs. The World environment rather often. I can connect to my outer realm when heading to live meetings. Auditions, job assignments all via my assistant. I like having the ability to capture the moment and rewrite it as well. This is a primary driver for me. Sometimes branching out or when collaborating, I think I work a little harder in the moment than Google Assistant might but that is moreso my limitations and not the feature so much. I catch this scene when I'm in a group environment or at times having to create and respond to a larger scale event. Not a deal breaker for me however.
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
I think newer, complementary ideas are a bit sharper than Google Assistant especially in a Q&A environment or when seeking some depth to a subject. That enhancement is to be expected I feel. And Google Assistant is not so self limiting so I don't have a lot of improvement needs because I use this for what I've become accustomed to and for the ability overall.
It is always important to do your best around hectic places, in bad tower signal areas or even if trying to do something new while using Google Assistant. Have patience in the setting. It pays off.
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
I feel this can be adjusted and after some trial and error you sort of start knowing what will work and how. And I have to say the overall impact becomes personal and we are all different. I'm small scale and as I've said, it works.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
I chose this because it was easier for me and can be accessed via mobile and laptop too because it enables cross device support because it helps in adding more depth to my life, and can help me save tons of time.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.
