Sqlserver
231 subscribers
18 photos
2.31K links
Download Telegram
SQLServer Just tweeted ********************************************** @SQLSouthwood 1/2 Hi Will, what kind of patch have you applied? If your patch updates SQL Server assemblies without updating SSISDB scripts/schema, you do not need to move SSISDB out from an AG to do an upgrade.
SQLServer Just tweeted ********************************************** @SQLSouthwood 2/2 If your patch needs to update SSISDB scripts/schema, you will still need to move SSISDB out from an AG to do the upgrade. Please let us know if this helps. Thanks!
SQLServer Just tweeted ********************************************** @biserdimitrov Hi Biser, are you still experiencing this issue? If so, please contact Microsoft Support for assistance: https://t.co/SU4Sx8zaXG. Thanks!
SQLServer Just tweeted ********************************************** @kdawg02 Hi Karl, we are sorry to hear this. Please log a bug on the SQL Server feedback forum: https://t.co/cLrbPLXTzW. Thanks!
SQLServer Just tweeted ********************************************** RT @Azure: Built on #Azure and #PowerBI, the Modern Data Warehouse lets users quickly leverage data to provide powerful analytics. See the solution architecture: https://t.co/EzQZPyhPl4 https://t.co/3ImTCVwa4R
SQLServer Just tweeted ********************************************** @biserdimitrov We're glad to hear this has been resolved. Thanks for keeping us updated!
SQLServer Just tweeted ********************************************** @monah1984 Hi Monah, thanks for reaching out. Is SQL Server running on an Ubuntu server, and is this Ubuntu server joined to an Active Directory Domain?
SQLServer Just tweeted ********************************************** @mogupta Hyperthreading is a feature of the CPU and does not require a separate license to be activated. The use of hyper-threading does not affect the number of core licenses required when running SQL Server software in a physical OSE. Read more here: https://t.co/c3clUYZyb0. Thanks!
SQLServer Just tweeted ********************************************** @stochasmos Please post this question the SQL Server forum for assistance: https://t.co/XUv6iOeXcU. Thanks!
SQLServer Just tweeted ********************************************** @chuckh1958 Hi Chuck, please post this question to the SQL Server forum: https://t.co/TbfYSfPiKr. Thanks!
SQLServer Just tweeted ********************************************** @weiln Hi Nathan, the Setup exe can be deleted if there are security concerns. It is only used when installing SQL Server or doing changes to the installation using the GUI, so the user can always use the Setup tool using installation media.
SQLServer Just tweeted ********************************************** @KenDarlingJr Hi Ken, what are you planning to do? Store a database backup to the file share? Use SSIS to load files from the file share? Something else? Thanks!
SQLServer Just tweeted ********************************************** @KenDarlingJr Are you using domain-level accounts (like Managed Service Accounts) when running SQL Server Services? Or are you using local virtual accounts?
SQLServer Just tweeted ********************************************** @KenDarlingJr Are you using domain-level accounts (like Managed Service Accounts) when running SQL Server Services? Or are you using local virtual accounts?
SQLServer Just tweeted ********************************************** @GunneyK We just verified that there will be an opt-out option (Tools | Options | …) in SSMS 18.3.
SQLServer Just tweeted ********************************************** @skreebydba 1/2 The ideal and recommended upgrade sequence is to: 1. Upgrade all secondary replicas first 2. Failover from the current Primary to one of the upgraded secondary replicas 3. Run sp_vupgrade_replication on the new primary 4. Upgrade the old primary (now secondary) replica