/explore
|
You are here 
|
blog.sqlauthority.com | ||
| | | | |
tarynpivots.com
Recently, I kicked off a project to start moving us to SQL Server 2019. During my initial review of our servers, I found quite a few (9 total) that were still running on Windows Server 2012 R2. This meant that I would need to upgrade the operating system and move us to SQL Server 2019. Having completed plenty of SQL Server upgrades, as well as operating system upgrades, I couldn't possibly make a mistake, right? |
|
| | | | | ||
| | | | |
alwayssql.wordpress.com
This is one of the common issues that you would see as a DBA in your environment : Whenever Restart of SQL Server happens, it tries to perform theSQL Server Instance Recovery and during this process all databases tried to come online (Basically trying to Recover themselves) and they stuck in "In Recovery" mode. This... |
|
| | | | | ||
| | | | |
erikdarling.com
[AI summary] A SQL Server consultant discusses challenges with foreign key constraints and deadlock issues caused by an eager index spool in a merge operation, leading to the decision to disable the foreign key to improve performance. |
|
| | | | | ||
| | | | |
blog.crossjoin.co.uk
Something cool has just been announced for Azure SQL DB: the ability to call a limited number of REST APIs direct from TSQL. The announcement is here: https://devblogs.microsoft.com/azure-sql/azure-sql-database-external-rest-endpoints-integration-public-preview/ There are code samples here: https://github.com/Azure-Samples/azure-sql-db-invoke-external-rest-endpoints And guess what, the Power BI REST API is one of the APIs you can call! This means, for example, you... |
|
| | | |||
