1. Moving BI and OLTP to the Cloud

    To react quicker and more cost effective to the load changes and the necessary hardware planning, we moved over 20 OLTP databases to the Amazon cloud. This involved two SQL Servers with databases mirrored to each other for failover purpose. Before the move, we performed a detailed analysis of the I/O subsystem performance of the Amazon Cloud (I2.large, M2.4xlarge, M3.large) versus the corporate SAN and planned the necessary adjustments to the databases. Upon successful execution, we then moved a 2TB BI system along with all the SSIS Based ETL processing as well.

  2. Credit Card Processing and Phone Mashups

    Metaphor Technologies, Inc. is experienced in successfully integrating web applications with the webservice based Customer Information Manager (CIM) from Authorize.Net for credit card payment processing complying with the Visa's Cardholder Information Security Program and the Payment Card Industry Standard (PCIS). We also know how to create phone mashups with ifByPhone for example that allow customers to enter their phone number on your website and your system will automatically contact the customer at their pre-determined time.

  3. Data Modeling

    There are many areas where the experience of a developer comes to shine but none is so obvious as the skill of a good data modeler. A good data modeler has experience in a plethora of business domains and has the ability not only to draw from them, but to analyze requirements and reduce them to the similiarities faced in other areas. A good data modeler will strive to solve the general issue, rather than the specific one at hand. This is demonstrated by a resulting model that needs few or no modifications when unexpected extensions are required and those modifications are typically benign in natue...

  4. Performance Analysis

    It is astonishing to witness how many developments of systems of various kind are undertaken with very little capacity planning or performance analysis in mind from the beginning. If one is lucky, one can actually see some development effort geared towards what is commonly called "logging" for the purpose of error analysis and support. Those hooks are then the last resort from which performance data is hoped to be gleaned when things go bad over night. The author had been sent out to a customer site after a 2 year development effort resulted in a system that performed badly on a 4 proc...

  5. Canonical XSD Data Exchange

    When faced with the problems of many to many systems data exchange, they only viable solution is to build a canonical schema to and from which all data exchange has to take place. This is an essential strategy especially for Service Oriented Archiectures with an added concept that is labeled "Reader Makes Right" Configuresoft was facing this problem not only for the exchange of configuration data to and from various versions of their own configuration database, but also for the consumption of vulnerability information from organizations such as CERT, NIST, and MITRE which is provided...

  6. Bi-Temporal Database for Health Care

    There a numerous domains in which a bi-temporal datamodel as a basis for an OLTP database would provide a solid foundation. In some of those industries, a combination of an enterprise data warehouse along with a snapshot OLTP database is an acceptable selection. When you really need your database to fill the role of a time machine along with being an OLTP database such as in a health care clearing house application at Recondo Technologies in Denver, a bi-temporal database fits perfectly. This implementation allows for evaluation of queries as of now, in the future, in the past, and based on transaction...