SQLMINT

Microsoft SQL Server Blog

Posted by Steve M on July 24, 2023
Azure SQL, General, Microsoft SQL Server, SQL 2022 / Comments Off

Click here to be directed to Microsoft’s SQL Server Blog

Tags: azure, Blog, Microsoft, sql

SQL Server 2022

Posted by Steve M on November 17, 2022
Azure SQL, Microsoft SQL Server / Comments Off

Today Microsoft released SQL Server 2022 – their most Azure enabled version.

Below is a link on this latest SQL Server.

https://www.microsoft.com/en-us/videoplayer/embed/RE5cjeS

Microsoft SQL Server 2022

Posted by Steve M on June 22, 2022
Azure SQL / Comments Off

As per Microsoft, SQL Server 2022 is “Azure-enabled, with continued performance and security innovation” – and as of 6/22/2022 it is now in public preview.

For more information, click here.

What’s new in SQL Server 2022 – click here

Tags: 2022, SQL Server 2022

Field Notes: Move of cluster role ‘SQL Server (A)’ for drain could not be completed. The operation failed with error code 0x138D

Posted by Steve M on December 16, 2021
Microsoft, Microsoft SQL Server, SQL 2019, SQLServerCluster, Windows Server 2016 / Comments Off

This error below comes up each time l tried to failover a SQL Role/Instance (A) to Node2 from Node1, in a 2 node SQL Server 2019 Cluster, running on Windows Server 2016.

“Move of cluster role ‘SQL Server (A)’ for drain could not be completed. The operation failed with error code 0x138D”

Issue turned out to be SQL Role A’s CEIP service was inadvertently only checked/enabled for one of the Nodes it always sticks to Node1 as shown below.

For comparison l looked at a SQL Role (B) with similar services.

Solution:

Checking both nodes and clicking apply, then stop and restart the role, resolved this.

Tags: cluster, drain, failover, FCM, node, sql, SQL Server

SQL Cluster issue: Msg 5184, Level 16, State 2, Line 1

Posted by Steve M on December 10, 2021
Microsoft SQL Server, SQL 2017, SQL 2019, SQLServerCluster, Windows Server 2016 / Comments Off

Got this error message while completing moving SQL SAN Storage drives. The SQL instance came up online ok, and was accessible from SSMS, but each time l tried to create a test database – l got the error below.

Error Message:

Cannot use file ‘U:\MSSQL13.xxxxxxx\MSSQL\DATA\yyyyyy.mdf’ for clustered server.

Only formatted files on which the cluster resource of the server has a dependency can be used.

Either the disk resource containing the file is not present in the cluster group

or the cluster resource of the Sql Server does not have a dependency on it.

Msg 1802, Level 16, State 1, Line 1

CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

Solution:

Go to the FCM – failover cluster manager
Click on the SQL Server Role
Click on the resouces tab below
Right click on the “other resources” – line showing the SQL Server role/instance.
Re-insert the new SAN drives to this role as shown below
Click apply.
In my case, no restart was needed

Tags: cluster, FCM, sql, SQL cluster

Install SQL Server 2019 on Ubuntu 20.04 VM on Hyper-V

Posted by Steve M on October 10, 2021
General, Hyper-V, Microsoft, Microsoft SQL Server, SQL 2019, Ubuntu / Comments Off

Installation of Microsoft SQL Server 2019 developer edition on a virtual machine [VM] running Ubuntu 20.04 [linux] on Hyper-V.

Specifications of the VM:

Hard disk 47Gb
Processors: 2 Virtual processors
RAM: 4Gb – 8Gb [Dynamic]

Screenshots:

class=”alignnone size-full wp-image-931″ src=”https://sqlmint.com/wp-content/uploads/2021/10/Capture_Ubuntu_SQL04.png” alt=”” width=”1031″ height=”489″ />

class=”alignnone size-full wp-image-930″ src=”https://sqlmint.com/wp-content/uploads/2021/10/Capture_Ubuntu_SQL05.png” alt=”” width=”1023″ height=”760″ />