Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Separate Client DatabaseSeparate Client Database
Previous
 
Next
New Post
11/15/2006 1:42 PM
 

This is very helpful. You do it all at the database level which is clean and straightforward. It makes sense to me. Thanks a lot for the advice.

GM

 
New Post
11/15/2006 4:52 PM
 

Depending on what you are trying to do you could use out database access modules.

Brillnat ActiveHTML module
 A data access HTML module that functions like an asp:repeater control. For HTML savvy DotNetNuke implementers who want completely flexible data display capability. 

Brillnat DbHTML module
 A alternative to the core Text/HTML module that functions like it, but also allow tags to be placed in the text that will be replaced with data from several sources. 

1.  A selection set from a database
2.  Logged in user profile
3.  Portal information
4.  Querystring parameters
5.  User host information

For HTML savvy DotNetNuke implementers who want simple data access.
 


Michael Jackson
Brillnat.com
Custom module development
Database access tokenized HTML modules
 
New Post
11/21/2006 3:28 PM
 
 
New Post
11/22/2006 3:21 AM
 
gmitchell7 wrote

This is very helpful. You do it all at the database level which is clean and straightforward. It makes sense to me. Thanks a lot for the advice.

GM

I need to start doing this very soon; My plan was to create an additional database and set up replication with SQL 2005 between them - i'm not 100 % sure that I can replicate partial tables like this or not yet - however I plan to research this route because I need to support replication with a number of tables used in my custom modules; however it would be nice to get the users/roles/membership table data out and into my own data schema so that I can come up with a plan that will allow users to temporaraly work on a windows forms application in a senario when their internet connection goes down.

Has anyone gone this route before?

 
New Post
11/22/2006 11:46 AM
 

I had not considered using replication since the tables I am concerned with will be specific to the client and not any of the DNN standard tables. All updates are to be via a browser, i.e. these tables will be treated as OLTP tables and just backed up periodically. I don’t have a lot of experience with replication but you can choose the tables to copy and filter the data if you wish. If you use something like snapshot replication, it should be reasonably straight forward. Merge or transactional replication would be more complex. So far I haven’t seen anything in DNN that would preclude using all the replication tools available in SQL Server 2005 but then I haven’t done any in depth research. One thing that might be a concern is future schema changes to the DNN tables although they can also be replicated (I think by default) to subscribers. Of course applications used with the subscribers would have to deal with any changes.

GM

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Separate Client DatabaseSeparate Client Database


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out