2023-03-13
391 reads
2023-03-13
391 reads
2021-09-08
761 reads
In this article, I am going to explain fixing a problem related login failure error with SQL Server. The Problem One of the common error in the SQL Server error log is "Login failed for user 'DomainName\ServerName$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]". Even though it says that […]
2020-11-24
44,594 reads
2024-09-11 (first published: 2018-12-18)
8,551 reads
An example of a database migration from SQL Server 2016 on Windows to MS SQL Server 2017 on Linux.
2020-07-09 (first published: 2018-06-05)
2,311 reads
Microsoft has released a version of SQL Server 2017 for Linux.
2018-03-26
2,567 reads
In this tip, Edwin Sarmiento looks at how to create the Always On Availability Group with a listener name when using SQL Server on Linux.
2018-02-02
3,045 reads
Jeffrey Yao explains how to generate backups based on the amount of data that has changed for differential and transaction log backups.
2018-01-02
3,457 reads
Ameena Lalani looks at cascading updates and deletes when using temporal tables in SQL Server.
2017-12-25
3,228 reads
You can use the Data Migration Assistant (DMA) tool to migrate your SQL Server instance to an on-premise SQL Server 2017 or to Azure SQL Database. DMA analyzes data migration issues and provides recommendations to resolve them. Read on learn about the features of DMA and how DMA eases your SQL Server instance migration as well as reduces overall risks, allowing you to complete the migration successfully.
2017-12-19
3,471 reads
By James Serra
I get many of the same questions about Microsoft Purview, so I wanted to...
Full documentation on the Undercover Catalogue can be found HERE We’ve spotted a bug in...
By Steve Jones
With my new laptop, one of the things I realized I’d forgotten to do...
Comments posted to this topic are about the item GIT Configuration and Automated Release...
Comments posted to this topic are about the item How to Add a New...
I want to disable an index so that it doesn't use any resources and isn't maintained. I am planning to drop this, but don't want to do it now. The index is named LoggerNCI and was created on the dbo.Logger table, on the LogID column. What code disables this?
See possible answers