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

2020-11-24

44,594 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

Microsoft Purview FAQ

By

I get many of the same questions about Microsoft Purview, so I wanted to...

Undercover Catalogue 0.4.5 Released – Database Module Bug Fix

By

Full documentation on the Undercover Catalogue can be found HERE We’ve spotted a bug in...

Saving Emergency Space on my Laptop

By

With my new laptop, one of the things I realized I’d forgotten to do...

Read the latest Blogs

Forums

GIT Configuration and Automated Release for Azure Data Factory

By Sucharita Das

Comments posted to this topic are about the item GIT Configuration and Automated Release...

How to Add a New Shared Disk to a WSFC as a SQL Resource

By muhkam

Comments posted to this topic are about the item How to Add a New...

Beginner questions

By fk.da

Hello everyone and thank you for joining the forum. I am new to SQL...

Visit the forum

Question of the Day

Disabling Indexes

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