close

SQL Server 2017

SQLServerCentral Article

Fixing "Login failed for user" error in SQL Server

  • Article

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 […]

You rated this post out of 5. Change rating

2025-12-31 (first published: )

55,162 reads

External Article

Understanding Migration from SQL Server to SQL Server 2017 using Data Migration Assistant

  • Article

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

Blogs

SQL Server instance metadata inventory with PowerShell and SMO

By

SQL Server instance metadata inventory with PowerShell and SMO The purpose...

5 SQL Tricks Worth Remembering Before You Close the Laptop

By

Disclosure: this post may contain links to books as an affiliate link. If you...

Claude Context Window

By

Every Claude conversation has a context window. It is the total amount of text...

Read the latest Blogs

Forums

Celebrating 30 years of PostgreSQL, A Thank you message

By Pat Wright

Comments posted to this topic are about the item Celebrating 30 years of PostgreSQL,...

provisioning sql server via VMware Cloud Foundation

By andreas.kreuzberg

Hello, has anyone here ever provisioned and actually used an MS SQL Server with...

No More Deadlocks

By Steve Jones - SSC Editor

Comments posted to this topic are about the item No More Deadlocks

Visit the forum

Question of the Day

No More Deadlocks

After detecting deadlocks in SQL Server 2025 and lowering the time threshold for detecting future issues, when does the Database Engine return to the 5s default interval?

See possible answers