Duplicate tables created in django migrations when using SQL Server schemas - sql-server

Question

I want to place all Django specific tables and my custom Auth models into the default dbo schema, and have all my different app specific tables in a schema named after the app. Something to note is that all of my app tables will foreign key back to my auth model (I have _created_by and _last_updated_by fields on a base model that all apps inherit from). Basically I want the DB structure to be something like this:
DBO
- my_custom_auth_table
- django_migrations
- django_session
- django_content_type
- etc...
APP1
-table1
-table2
APP2
-table1
-table2
In order to achieve this, I tried creating a Login/User pair on the DB server for each app and implemented a DB router.
my allow_migrate method:
def allow_migrate(self, db, app_label, model_name=None, **hints):
if app_label == db:
return True
else:
return False
my database settings (I will use my doglicense app as an example):
IP = xxx
default_db_settings = {
'ENGINE': 'mssql',
'NAME': 'DB',
'USER': 'some_user',
'PASSWORD':'***',
'HOST': IP,
'PORT':'1433',
'OPTIONS':{'driver':'ODBC Driver 18 for SQL Server', 'extra_params': 'trustServerCertificate=yes'},
}
doglicense = {
'ENGINE': 'mssql',
'NAME': 'DB',
'USER': 'DogLicense',
'PASSWORD':'***',
'HOST': IP,
'PORT':'1433',
'OPTIONS':{'driver':'ODBC Driver 18 for SQL Server', 'extra_params': 'trustServerCertificate=yes'},
}
I have successfully migrated the custom auth app and all of djangos apps into dbo, however this is where the fun begins.
If I run:
python manage.py migrate DogLicense --plan
we can see that it only tries to create the new tables:
Planned operations:
DogLicense.0001_initial
Create model Breed
Create model Color
Create model Dog
Create model ZipCode
Create model Veterinarian
Create model Street
Create model Registration
Create model Owner
Create model DogType
Add field owners to dog
Add field type to dog
However when I try to specify the database connection in order to dump theses files into the doglicense schema:
python manage.py migrate DogLicense --plan --database=doglicense
I get:
Planned operations:
contenttypes.0001_initial
Create model ContentType
Alter unique_together for contenttype (1 constraint(s))
contenttypes.0002_remove_content_type_name
Change Meta options on contenttype
Alter field name on contenttype
Raw Python operation
Remove field name from contenttype
auth.0001_initial
Create model Permission
Create model Group
Create model User
auth.0002_alter_permission_name_max_length
Alter field name on permission
auth.0003_alter_user_email_max_length
Alter field email on user
auth.0004_alter_user_username_opts
Alter field username on user
auth.0005_alter_user_last_login_null
Alter field last_login on user
auth.0006_require_contenttypes_0002
auth.0007_alter_validators_add_error_messages
Alter field username on user
auth.0008_alter_user_username_max_length
Alter field username on user
auth.0009_alter_user_last_name_max_length
Alter field last_name on user
auth.0010_alter_group_name_max_length
Alter field name on group
auth.0011_update_proxy_permissions
Raw Python operation -> Update the content_type of prox…
auth.0012_alter_user_first_name_max_length
Alter field first_name on user
MSSAuth.0001_initial
Create model FailedLoginAttempt
Create model MSSUser
Create model AuthProfile
DogLicense.0001_initial
Create model Breed
Create model Color
Create model Dog
Create model ZipCode
Create model Veterinarian
Create model Street
Create model Registration
Create model Owner
Create model DogType
Add field owners to dog
Add field type to dog
You can see it wants to create every table all over again. And obviously running this migration without the --plan flag does indeed result in tables like doglicense.django_migrations being created.
How can I prevent these duplicate tables from being created? Is this a problem with my SQL Server user permissions? Perhaps my router is poorly implemented?
Any help will be appreciated.