[Sql Azure] migrate gets stuck without a shadow DB

Bug description

When I use prisma migrate with SQL Azure, the command gets stuck.

It also tries to create a database on SQL Azure, which might cause all sorts of issues (including billing) for people that don’t know what’s going on.

How to reproduce

• npx prisma migrate dev --name init

Expected behavior

A migration is created and applied. If there’s an error, I should see a clear message on what went wrong.

Fix

In order to fix this, one has to use the Shadow Database configuration to make it work.

Prisma information

datasource db {
  provider          = "sqlserver"
  url               = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["microsoftSqlServer"]
}

model User {
  id              Int       @id @default(autoincrement())
  createdAt       DateTime  @default(now())
  updatedAt       DateTime  @updatedAt
  name            String
  }

Environment & setup

Environment variables loaded from .env
prisma               : 2.20.1
@prisma/client       : 2.20.1
Current platform     : darwin
Query Engine         : query-engine 60ba6551f29b17d7d6ce479e5733c70d9c00860e (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 60ba6551f29b17d7d6ce479e5733c70d9c00860e (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 60ba6551f29b17d7d6ce479e5733c70d9c00860e (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 60ba6551f29b17d7d6ce479e5733c70d9c00860e (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : 60ba6551f29b17d7d6ce479e5733c70d9c00860e
Studio               : 0.365.0
Preview Features     : microsoftSqlServer

[pantharshit00]

I wasn’t able to reproduce it getting stuck but yes creating new database without consent on azure is a problem as you are billed per database, not the by database server on azure.

I think we can add a warning for azure which will warn the user about this. We can do this my check for windows.net in the hostname.

[tomhoule]

@luisrudge I went with your suggestion of checking the host in this PR: https://github.com/prisma/prisma-engines/pull/1964 — it’s a small change so it will probably make it in tomorrow’s release, and it can then be tested in the field. We should still investigate why prisma gets stuck on Azure SQL, but it’s probably a bit harder to fix.