@jaredbusch said in Restoring a Windows MS SQL Server Database to Linux With Move SQLCMD:

@scottalanmiller I have not had to do that before with a normal backup to a .bak and then restore. Not some an place move like it seems you are doing.

Happens if going to a space with a different storage layout. If you are coming from Linux you are probably fine. But Windows injects the drive letter into the path (obviously) and so going from one machine to another that doesn't keep identical storage path names causes the issue.

@dustinb3403 said in Verifying MS SQL Server 2017 Licensing:

@jaredbusch said in Verifying MS SQL Server 2017 Licensing:

@scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

@jaredbusch said in Verifying MS SQL Server 2017 Licensing:

@scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

@jaredbusch one of the complications is that there IS no virtual core. vCPU is NOT core.

a vCPU has vCores. Always. It might just be one. That is how it works.

Not in any system I've seen. What people call vCores are actually vCPUs. The vCPU might tell the OS it has multiple cores, but the idea of a vCore has never existed, only vCPUs. Vmware, KVM, etc. all the same. Core means physical, it's like having a physical virtual, it cancels itself out.

I am almost certain that VMWare lets you make a 1 CPU VM with 2 cores.

Hyper-V just says virtual processors.
0_1536703623096_9bebc766-93a2-498e-aa75-f621eb5bb0da-image.png

KVM says CPUs.
0_1536703642847_0252def6-e3e4-40f0-93ec-98417b2bb6ff-image.png

But I very clearly remember some hypervisor letting me specify a vCPU and vCores.

XenServer and XCP-ng also allow this.

1cpu 2 core etc.

Topology lets you state presented cores, not vCores. Totally different things.