multiSchema does not work with SQL Server schemas with dot in name (= databases)

Bug description

In sqlserver when declaring several schemas, it was not possible to perform a select. There was a table not found error in the database

How to reproduce

(https://github.com/prisma/prisma/issues/15077#issuecomment-1270280714)

Expected behavior

No response

Prisma information

Its work

datasource db {
    provider = "sqlserver"
    url      = env("DATABASE_URL")
    schemas  = ["database1].[dbo", "database2].[dbo"]
}

Does not work

datasource db {
    provider = "sqlserver"
    url      = env("DATABASE_URL")
    schemas  = ["database1", "database2"]
}

prismaClient.table1.findMany()

Environment & setup

• OS: Windows
• Database: SQL Server
• Node.js version: v16.14.0

Prisma Version

v4.4.0

[janpio]

Yeah, that makes sense. You “hacked” our system 👍 😆

I fear we will probably have to limit that first, before we can properly enable this. Right now the foreign keys are a important requirement for a relation in Prisma. We will open that up sooner or later, and then that would also enable doing multiDatabase for SQL Server with databases on the same server.

[pimeys]

Naturally this breaks in every engine. Here’s what introspection engine gives us:

Incorrect syntax near '.'. code=102
Error: Incorrect syntax near '.'.
   0: sql_migration_connector::apply_migration::migration_step
           with step=CreateSchema(NamespaceId(0))
             at migration-engine/connectors/sql-migration-connector/src/apply_migration.rs:21
   1: sql_migration_connector::apply_migration::apply_migration
             at migration-engine/connectors/sql-migration-connector/src/apply_migration.rs:10
   2: migration_core::state::SchemaPush
             at migration-engine/core/src/state.rs:402

We do not support multi-database schemas with any database. But, you should try out Prisma 4.8.0 tomorrow that does let you to migrate and introspect multi-schema databases with SQL Server.