SQLServer Just tweeted ********************************************** @msedej Hi there. We suggest posting this to our feedback forum so the proper team can look into this for you: https://t.co/1B64Brhw5z. Thanks!

SQLServer Just tweeted ********************************************** RT @Azure: Push your apps and data to the next level, and do even more with Linux on #Azure. Learn how from Linux rock stars at #OpenAzureDay, November 18. Register now: https://t.co/rjzN03CoYZ #LinuxOnAzure https://t.co/lreNwj3KVp

SQLServer Just tweeted ********************************************** In this episode with @SysAdminDrew, you'll be introduced to a new experience for database development with the #SQL Database Projects extension for Azure Data Studio. Watch and learn how you can easily build SQL database projects: https://t.co/qhqFMdoyjx https://t.co/H8fZGe3Xzo

SQLServer Just tweeted ********************************************** Watch episode 18 of Azure SQL for Beginners and learn how to load data into #AzureSQL and how it compares to SQL Server: https://t.co/RsOugkT8Ij

SQLServer Just tweeted ********************************************** @yacovr Hi there! Unfortunately, transactional or merge replication does not work on columns encrypted with Always Encrypted. For more information, we recommend reading through this documentation on Always Encrypted here: https://t.co/ZiyOXs27qo.

SQLServer Just tweeted ********************************************** @ObsidianDev Hi Fergal! Can you let us know which version of SQL Server you are using, so we can help you better?

SQLServer Just tweeted ********************************************** @ObsidianDev Thanks for letting us know! Do you mind explaining further what you mean by “during an INSERT operation”? Are you using a different user session to query @@ROWCOUNT while another session is doing an insert?

SQLServer Just tweeted ********************************************** @marrowyung Hi there! Standard edition supports failover clusters between two nodes. However, if you are planning to have an active/active configuration, you need to have a SQL Server license for both nodes. (1/2)

SQLServer Just tweeted ********************************************** @marrowyung This is because node 1 would be active for instance1 and passive for instance2, node 2 would be active for instance2, and passive for instance1. We hope this helps! (2/2)

SQLServer Just tweeted ********************************************** RT @Azure: Upgrade your mission-critical OSS apps with tips and demos from Linux rock stars at #OpenAzureDay on Nov 18. Do more with Linux on Microsoft Azure! Register now: https://t.co/iEeLQZo9d8 #LinuxOnAzure https://t.co/pC2lg8cs4R

SQLServer Just tweeted ********************************************** @ObsidianDev We're looking into this and will get back to you as soon as possible!

SQLServer Just tweeted ********************************************** RT @Azure: It's almost time for #PASSsummit 2020, the virtual event where you can learn about the latest Azure Data innovations directly from our engineering team. See what you can expect this year: https://t.co/t1foGvlj64 https://t.co/uVxi1qXSjO

SQLServer Just tweeted ********************************************** Learn how to bulk insert data from Azure Blob storage into #AzureSQL with a PowerShell notebook in Azure Data Studio. Watch episode 19 of Data Exposed: https://t.co/cuysN4NR1a

SQLServer Just tweeted ********************************************** Learn about the latest Microsoft innovations, including Big Data Clusters, Azure SQL, Arc enabled data services, and Synapse Analytics, with @RohanKData―all happening during #PASSsummit! Register now: https://t.co/ThRQfSpxEP https://t.co/nhh9aztZwE

SQLServer Just tweeted ********************************************** Hi there! Thanks for your patience. Do you mind sending us a DM, so we can share a contact with you to get this resolved? https://t.co/v1P0lR957j

SQLServer Just tweeted ********************************************** @ipvharish Hi there! Mainstream Support of SQL Server 2017 ends 10/11/2022, Extended Support ends 10/12/2027. Mainstream Support of SQL Server 2019 ends 1/7/2025 and Extended Support 1/8/2030. (1/2)

SQLServer Just tweeted ********************************************** @ipvharish Using SQL Server 2012 compatibility level for your databases does not affect the support of your SQL Server version. But you will not be able to leverage enhancements that are only available in a higher database compatibility level. We hope this helps! (2/2)

SQLServer Just tweeted ********************************************** @marrowyung Hi Marrow! Please DM us so we can help you further. https://t.co/v1P0lR957j

SQLServer Just tweeted ********************************************** @gusgeet Hi there! Do you mind providing more details, so we can help resolve this? What do you mean by "null search"? Can you provide screenshots of what you are seeing?

SQLServer Just tweeted ********************************************** @gusgeet Glad to hear it! Feel free to reach back out with any future questions. 🙂