document what include_schemas does and include notes about the significance of default schema name

I am using MSSQL.

For each "dbo" table I have a mirrored design for a "stage" table.

Due to the workflow I have, I bulk insert data into a "stage" table and then trigger a merge process on sql server wrapped in a stored procedure I call from sqlalchemy.

Everything is working good but the schema migrations continuously detect changes in the foreign keys - generating stuff that shouldn't be generated after the initial migration.

I read a bunch of forums and the workarounds seem a little dated and really complex. I was curious is there is a better way to work with schema migrations?

What I have done is just use all dbo schema and attach "stage" to the end of the stage table name. I'd prefer to have two schemas but I struggle to understand the workaround.

https://groups.google.com/forum/#!topic/sqlalchemy-alembic/FA8wpmPJc7U

https://stackoverflow.com/questions/41150956/alembic-not-generating-correct-changes/41193382#41193382

Start by locating the existing documentation for include_schemas and the default schema name. Document what include_schemas does and explain why the default schema name matters, including the schema-migration context described in the issue; done when a reader can understand these options without relying on external forum posts.