Well, this should be something that you could do quite easily, though I don't completely understand the benefit of what you're trying to do - unless you actually did want to use a different database.  

All you should need to do is add a new connectionString to the connectionStrings section in your main web(dot)config.  Then, you can access it any way you wish.  That includes DAL2 (don't use the others ones at this point), raw DAL code, and any other common method (e.g., Entity Framework, Dapper, etc.).  

Just be sure that the connectionString is using the values you configured in SQL Server to achieve your desired result. 

Posted By Will Strohl on 1/19/2024 11:58 AM

Well, this should be something that you could do quite easily, though I don't completely understand the benefit of what you're trying to do - unless you actually did want to use a different database.  

All you should need to do is add a new connectionString to the connectionStrings section in your main web(dot)config.  Then, you can access it any way you wish.  That includes DAL2 (don't use the others ones at this point), raw DAL code, and any other common method (e.g., Entity Framework, Dapper, etc.).  

Just be sure that the connectionString is using the values you configured in SQL Server to achieve your desired result. 

Hi Will,

 

Thanx for taking the time to read my question and respond - much appreciated.

I have added a new connectionString - but would I need to create a new SQL user that only has access to my schema in order to accomplish this?
This might be an issue in terms of the web-hosting - I'd need to check what I can achieve in this regard.

In the model class (Invoice.cs) - would I specify the schema as part of the TableName attribute when using DAL2: [TableName("orders.Invoice")] ?

The purpose is simply to group the tables for my module into something that is easily identifiable and distinct from the rest of DNN:
like: orders.Invoices and orders.InvoiceItems instead of just dbo.Invoices and dbo.InvoiceItems.
the rest of DNN live in the 'dbo' schema and would be inter-mingled with my tables.

Thanx,
Alon

 

 

I played around with a test project and found that I am able to specify the schema and table in the TableName attribute like this:
[TableName("[orders].Invoices")]

Thanx
Alon

You're going to be putting this together a bit custom compared to how most folks would approach this.  I wouldn't be able to tell you exactly what to do, but the links in the resource below will give you all of the details you need to know on how to implement DAL2.  You'll need to read through some of it to find the part where you customize the query string and whatnot.  

https://www.dnnsoftware.com/wiki/dal-2