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

37,952 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

Friday Flyway Tips–Quick Command Line Access

By

One of the things I had to do recently in a demo was access...

A New Word: Aesthosis

By

aesthosis– n. the state of feeling trapped inside your own subjective tastes – not...

A First Look at Redgate’s Subsetter

By

I have been a proponent of subsetting databases in dev/test for a long time....

Read the latest Blogs

Forums

Linked Server Connection Issue

By dinomike20

Hi all, I have 2 SQL servers on different domains (lets call them SQL-A...

Frustrated trying to get Cross DB Access by Signing SP with Certificate

By Ken McKelvey

Maybe it is lack of caffeine, but I cannot see why the following test...

SSIS Execute Package Fail in SSMS but Agent Job Succeeds

By jerryszz

Hello, I created a SSIS package to transfer data from an XML file to...

Visit the forum

Question of the Day

Writing to Clones

I run this code on SQL Server 2019:

DBCC CLONEDATABASE(imdb, imdb_dev)
I then change to the cloned database, imdb_dev, and run some queries. I then run this code while testing:
INSERT dbo.Title (TitleID, Title, DateReleased) VALUES (3234, 'Maestro', '2023')
GO
What happens?

See possible answers