Welcome to Jay P. Com
I have several plans for this website including new products, several technical links, practice techniques, interactive resume, and just my person ranting about things. This personal ranting starts with “True north principles”, the ability to put first thing first. This is not always a easy practice in my chosen career field, sometime we get so busy with the “TPS-Reports” that we forget to get the work done. Also, in my career field, we also have a habit of being super proficient and inefficient things. The ability to go through the motions without any benefit to your employer or your employees sometime shocks me. I am taking the first step toward starting my own company called JPVision (more to come..). All the ideas I have in my head, on napkins, whiteboards, notebooks, ect.. I plan to start putting into action.
Technical and Career Overview
ASP.NET 4.0, 3.5 / VS2010, VS2008 / SQL 2008R2, 2005 Database Solution/ Reporting Services
Experience as an ASP.NET 4.0 & 3.5 (Visual Basic, C#) / SQL (2008 r2, 2005) Database
Developer position with a well‐established company. Offer 20 years of extensive
hands‐on experience in the information technology industry including recent experience
with web development using ASP.NET 4.0 along with hands on production database development.
Motivated, self‐starter with a passion for solution development using new and emerging
technologies to provide new solutions to current problems pursuing a career with
a professional team that can benefit from my skills and experience.
Purpose driven, solution oriented and technically proficient as an ASP.NET Web Developer
and SQL Server Database Developer with 6 years of experience solving data related
business problems from an SQL Server database development perspective. Success working
with major end users to define needs and provide data oriented solutions. Being
certified as a Microsoft Certified Technology Specialist (MCTS) has allowed me to
put several SQL 2005 tools and processes in place.
Featured Project ‐ 1 (Risk Management Tracking System – RMTS):
The original system was developed in 4 MS Access databases. Each database produced
a report that was copied into a power point presentation for committee reporting,
also, data was imported from an external system. The goal of this project was to
gather different sets of data from multiple departments, including different states
using the company’s intranet. After gathering the data, we map the key indicators
(Reporting Status: High Medium or Low, Issue Status: Open or Closed, Issue State:
Current, Coming Due or Past Due). The challenged is to map several different issue
types to the same key indicators used for committee reporting.
Accomplishment: ASP.NET 3.5, SQL 2005, SSRS, SSIS We designed and created an ASP.NET
3.5 application that combined all 4 separate databases into 1 SQL Server 2008 database.
Using SQL Server, we created user defined functions and views to map different values
to same key indicators. Using Reporting Services to create the committee reports.
Featured Project ‐ 2 (Operational Loss Manager– OLM):
The Basle Committee on Banking supervision has recently initiated work related to
operational risk. Managing such risk is becoming an important feature of sound risk
management practice in modern financial markets. The biggest challenge of this project
is to import and document several GL transaction on a monthly basis.
Accomplishment: ASP.NET 3.4, 4.0 / SQL 2008 / SSRS, SSIS / MS Access
We designed and created an ASP.NET 3.5 application using a SQL server database that allowed
the administrator to import thousands of GL transactions and allow the users to
search and document the appropriate GL transaction in accordance with BASEL II Compliance.
By storing the information in SQL server, we were able to provide reporting and
user metrics.
What is Third Normal Form (SQL)
In the design of a relational database management system (RDBMS), the process of organizing data to minimize redundancy is called normalization. The goal of database normalization is to decompose relations with anomalies in order to produce smaller, well-structured relations. Normalization usually involves dividing large, badly-formed tables into smaller, well-formed tables and defining relationships between them. The objective is to isolate data so that additions, deletions, and modifications of a field can be made in just one table and then propagated through the rest of the database via the defined relationships.
Definition: Normalization is the process of structuring relational database schema such that most ambiguity is removed. The stages of normalization are referred to as normal forms and progress from the least restrictive (First Normal Form) through the most restrictive (Fifth Normal Form). Generally, most database designers do not attempt to implement anything higher than Third Normal Form or Boyce-Codd Normal Form.
I’ve heard it said Normalize till it hurts, then de-normalize till it works. (JPH)
- First Normal Form: remove all repeating elements
- Second Normal Form: add Primary keys.
- Third Normal Form: all duplicate entries are placed in sub-tables.
One benefit to using Database normalization in Application Solution development is when entering data in a user screen, some of the options can be applied using drop down boxes. If the name or description of the selected option needs to changed, it can be changed in one place and flow throughout the application. (from my experience and IMHO).
Jay P. Hayes – 03/29/2011
- Notes from Wikipedia and database.about.com.