Main Points

Databases are a tremendously powerful tool. We're still wrapping our heads around how to use them exactly on our website, but their abilities are well documented. Every online store has a database with all its product information, customer information, order and shipping information, stored with maximum efficiency to make finding that information and sending it out as quick as possible. A database stores all that information and provides any piece or pieces on demand to help build webpages. The beauty of this system is that a user can then provide some form of electronic ID via a login, and the user can then see a customized page just for them, for example they could review an order they have placed.

Beginning ASP.NET Database Development

  • 1. Displaying Access (.mdb) Database Data - This is my first attempt at building a webpage that incorporates information from a database, in this case an Access database.

    [chroniclemaster1, 2008/01/23]

  • 2. GridView CSS Control - Our first go at displaying data from a database raised some CSS issues. This is our attempt to wrestle as much CSS control as we can away from the data controls, in this case a GridView.

    [chroniclemaster1, 2008/01/25]

  • 3. SQL Server Database Display - Our first attempt to display data from an MS Sql Server 2005 database.

    [chroniclemaster1, 2009/04/11]

  • 4. Data Access Layer (DAL) - Here we build a couple layers for low level database access; an excellent n-tier / OO design technique that forwards Separation of Concerns (SoC).

    [chroniclemaster1, 2009/10/10]

  • 5. DAL - Data Retrieval - Now that we've got the basis for some generalized and instance specific data access, we're building a robust set of database retrieval methods and planning the higher DAL architecture.

    [chroniclemaster1, 2009/10/10]

  • 6. Custom Data Access Layer - We constructed a working DAL, but it's just a demo. Now we need to customize the DAL and Business logic to perform the functions that we need.

    [chroniclemaster1, 2009/10/20]

  • 7. MySQL Installation - We've put in a significant amount of work with Access and MS SQL Server 2005 databases. Let's complete the trilogy by installing and configuring a MySQL instance to work with.

    [chroniclemaster1, 2009/11/12]

  • 8. MySQL Data Retrieval - We've taken care of installation and done some initial testing. Can we actually use this to do some serious work.

    [chroniclemaster1, 2009/11/14]

  • 9. MySQL: Copying to Production - Let's see if we can complete the circle: program against live data and copy everything up to the production server.

    [chroniclemaster1, 2009/11/20]

  • 10. MySQL Membership / Role Providers - Setting up the basic Membership and Role Providers for ASP.NET to run through the MySQL database using MySQL's .NET Connector.

    [chroniclemaster1, 2009/11/26]

  • 11. Data Access Layer Architecture - We've built a one-function DAL, but we need additional tests before settling on a final implementation for Earth Chronicle.

    [chroniclemaster1, 2010/04/22]

    • 11 - 1. Generalizing the DAL Code - Our final implementation wasn't so final after all; new discoveries, new DAL extensions that should be built in now.

      [chroniclemaster1, 2010/05/08]

  • 12. Database Architecture Practices - Recommendations and patterns in database architecture, and when to normalize and denormalize.

    [chroniclemaster1, 2011/02/14]

Major Projects

Language Tables

Most of my projects are primarily about C# programming. Hopefully, this one will eventually turn into my Perrill Translation application. However, that's such an ambitious project that it will require some setup, and this seems like a good place to figure out the DB architecture for the language tables I'll need for linguistics projects.

[chroniclemaster1, 2011/02/01]