Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Existing SQL Server Database #98

Open
digitalalchemist23 opened this issue Oct 5, 2024 · 4 comments
Open

Existing SQL Server Database #98

digitalalchemist23 opened this issue Oct 5, 2024 · 4 comments
Assignees
Labels
question Further information is requested

Comments

@digitalalchemist23
Copy link

Ask a question

what will be the steps in creating a new application if i have an existing database? thank you

@digitalalchemist23 digitalalchemist23 added the question Further information is requested label Oct 5, 2024
@joelsteventurner joelsteventurner self-assigned this Oct 5, 2024
@joelsteventurner
Copy link
Member

Hi @digitalalchemist23

Typically, you would model your domain in the domain designer which would set up everything for you. You would want to do database first there are several options.

If you are using Entity Framework and SQL Server (Or can get you DB Schema into a SQL Server database (if you are using Postgres for example))

Then you can use our Intent.SqlServerImporter module to reverse engineer the model. Simply install this module and import the Domain Model in the domain designer. Full documentation here.

If this is not an option, again assuming you are using our Entity Framework module, you can model out your database in the Domain Designer, using the various SQL Stereotypes like Table, Schema, Column etc. to capture any impedance between your model and DB. For example, if you have a SQL Table named 'tbl_customers' and you want your Domain Model to be called Customer simply add a Table stereotype to the Customer Entity and configure the table name to be tbl_customer

Documentation on EF modeling in the domain designer here.

We also have JSON importer which can be used to import model from JSON files which could be used
and scripting infrastructure which could also be used to create a custom import if required.

Let me know if you need more assistance around this.

@digitalalchemist23
Copy link
Author

digitalalchemist23 commented Oct 5, 2024 via email

@joelsteventurner
Copy link
Member

My pleasure, we do have a multi-tenancy module, specifically Intent.Modules.AspNetCore.MultiTenancy
which does multi-tenancy for Asp.NET core applications using FinBuckle.

Documentation available here.

@digitalalchemist23
Copy link
Author

digitalalchemist23 commented Oct 5, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants