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

42,294 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

What to Know about Power BI Theme Colors

By

Power BI reports have a theme that specifies the default colors, fonts, and visual...

A Global Team Meeting

By

The last few years at Redgate we’ve had the entire (or most) of the...

A New Word: sayfish

By

sayfish – n. a sincere emotion that seems to wither into mush as soon...

Read the latest Blogs

Forums

should i make as many datafiles for temdb as many cpus i have

By rajemessage 14195

hi, q1 As people said if u ghave GAM conention then u can go...

Script

By ramana3327

We have about 30 databases in server A.  All of them need to migrate...

Add alarms to database when a query, stored procedure, SSIS package hangs

By Lord Slaagh

Hello SSC, I am a SQL Server developer that has some DBA skills. I...

Visit the forum

Question of the Day

The Secondary Database Name in an AG

I am setting up a SQL Server 2022 Availability Group and I am ready to restore the database on the secondary. The primary database is named Finance. However, we also use this instance for QA and already have a database named Finance. How do I configure the AG to use a different database as the secondary?

See possible answers