James Seymour is a graduate of the University of North Carolina at Chapel Hill with a BA in history and political science and the University of Kentucky with a MA in history. He became first involved with computer technology in 1965 with the mainframe environment at North Carolina.
While in the United States Army during the Vietnam War, he was on the small team which worked with the mainframe setup at the Pentagon for various military strategic scenarios.
Since 1972, he has been involved on many, varied computer environments with the second point-of-sale and inventory control project in the retail industry, analytical programs and database initiatives in the insurance and benefits industries, loss control start-ups, and many other inventory control and sales tracking projects throughout many different industries.
From 1987 through 1995, Mr. Seymour was an instructor of database management in the community college system of the state of Kentucky. In this capacity, he created the first database management and C programming courses in the state of Kentucky and helped both public and private entities with urgent training needs including the programming of guidance systems on cruise missiles for Desert Storm.
Before 1985, he was a system administrator, network administrator, programmer, and database administrator. Since 1985, Mr. Seymour has been a senior enterprise architect, senior data architect, and senior database administrator working primarily with DB2 and Oracle DBMSs on multiple platforms plus SQL Server beginning with version 7.0. During this time, he has successfully developed and managed several major business and information technology projects for a Fortune 100 corporation in the United States, Canada, and Great Britain.
Mr. Seymour was the CEO plus Senior Business and IT Consultant for Sneezing Dragon Business & IT Consultants, Inc. for four years. This firm helped small, medium-sized, and large businesses with solutions to various problem areas. It operates both in the United States and in many other countries around the world. He has been the CEO of Faith Word, Ltd. since 2001. Faith Word, Ltd. is a ministry that helps other ministries around the world with a variety of needs.
Mr. Seymour can be reached through the email address of firstname.lastname@example.org or the email address of email@example.com.
Where to find James Seymour online
Modeling, Designing, Implementing Databases
There are a large multitude of databases out in the private and public sectors which were never planned, designed, and/or documented well. And so no wonder there are operating problems around the world. This book, Modeling, Designing, Implementing Databases, covers the topics of database modeling, design, and implementation from start to finish.
IT System and Taking the ODS to the Enterprise System
Key to the success of any business or even of any large governmental operation, is the design of the ITSystem and its data/database structures. This is especially true for any critical enterprise environment - an environment that should be in existence in your operation from the lowest level to the highest level. Without such an environment, businesses are tragically fooling themselves.
Frameworks & Models in Business & IT
For business and information technology, to create new systems or to update and fix old ones, you need to understand and use frameworks and modeling. They are key points to designing and documenting systems successfully. This book, Frameworks & Models in Business & IT, presents the total topic for both the intermediate and the expert.
Understanding Business and Application Models
To be successful in business, you must properly design a professional business including all of its divisions and departments and their functions. Additionally, it is critical that each application within the business is also thoroughly completed and kept updated. This requirement mandates the use of models for the business and applications.
Business Risk Analysis & Business Impact Analysis
This short book presents professionally the why and how to do a business risk analysis and a business impact analysis. Both analyses are critical to a vast variety of systems, actions, and processes of business and information technology.
Data Archival: Pure Wisdom
The use of a well-conceived and clearly implemented data archival system is a purely wise action that any business must undertake to improve service for clients and themselves, improve profits, plus maintain accurate data successfully.
Best Practices for Web Analytics
The purpose of this document is to convey best practices for creating and properly using different aspects of web analytics on websites.
Best Practices for Business Intelligence
The purpose of this document is to understand how business intelligence (BI) works in general and what are considered some of the best practices when doing a project within business intelligence.
Best Practices for Data Cleansing
The purpose of this document is to understand how data cleansing works and how to do it. Besides being critical for the data from which decisions and services are done, there are now legal issues involved.
Best Practices for Business Impact Analysis
The purpose of this document is to understand how business impact analysis (BIA) works in general and what are considered some of the best practices when doing a business impact analysis within any project.
Best Practices for XML Schemas
The purpose of this document is to convey best practices for XML Schemas. This is pertinent since XML has been used for a number of years to move data from one platform to another. This usage is especially true for large batch jobs involving daily transfer of new and updated data from one database to another.
Best Practices for Coding SQL Statements
The purpose of this document is to convey best practices for coding SQL statements. While there are dialects of SQL among the various database management system vendors, including many variations and extensions, this document will deal only with general conventions that apply to the SQL use within Microsoft, Oracle, and IBM DB2.
Naming Conventions for Physical Database Objects
The purpose of this document is to convey the naming conventions for physical database objects such as tables, columns, relationships, and relationships. While physical object names should be derived from logical object names (e.g. entity, attribute, and relationship names), this document does not address logical names.
Naming Conventions for Logical Database Objects
The purpose of this document is to convey the naming conventions for logical database objects such as entities, attributes and relationships. The goal of these naming conventions is to provide a uniform method for naming logical database objects.
Best Practices for Referential Integrity
The purpose of this document is to understand referential integrity (RI) as a very important element in data integrity enforcement in database design and database management. It was standardized first with ANSI-89 – also approximately when ANSI and ISO started working together regarding international standardization of SQL.
Best Practices for Indexes and Their Use
The purpose of this document is to convey best practices for planning for the use of indexes in a database and for testing the functionality and worth of an index over other approaches.
Best Practices for Check Constraints
The purpose of this document is to understand check constraints as a very important general concept in data integrity enforcement in both database design and database management.
Best Practices for Data Audit
The purpose of this document is to convey best practices for auditing data changes to include such activities as inserting, updating, or deleting data in a database. Additionally auditing must include tracking of changes to authorizations/privileges, queries of sensitive data, and the logons and logouts of areas containing sensitive data.
Object Naming & Abbreviation Conventions
All systems and database models, objects within databases, and other areas of any businesses must conform to an established naming standard for those names and abbreviations. Without such a standard, there is nothing but chaos.
Best Practices for Enterprise Architecture
One of the most intense endeavors in any business is creating an enterprise architecture - especially for a total, large operation or set of operations. Though modeling an enterprise of any size is daunting, it is worthy of the organized, professional work to do it.
Best Practices for Capacity Planning
Without proper and thorough capacity planning, no business will continue to operate for very long. Costs and lack of performance in any and all systems will bring down even the largest corporation.
This best practices book by James E. Seymour, Jr. presents proved processes by which to plan, develop, test, and implement successful capacity planning and implementation for any operation anywhere.
Best Practices for Architecting Distributed Computing & Systems
When attempting the creation, test, and/or implementation of any system, strict and thorough planning and documentation is imperative from the start. This document presents the best practices with which to architect distributed computing and systems.
These best practices have been successfully used in various corporations around the world.
Best Practices for Data Archival
Data archival is mission critical for any database operation within any business. Without it, limited funds are needlessly spent, performance suffers, and clients are not happy.
This short book explains proven and successful best practices to follow to create a very successful data archival system and approach.
So You Want To Be A DBA?
This book discusses the many factors a person should consider before trying to become a database administrator.
The position of a database administrator is mission critical for any business dealing with digital data; but the position is a hard one with sometimes long hours.
Read this book and find out first what is needed for the position.
The Enterprise: Mystery Unraveled
Jim Seymour in his book, The Enterprise: Mystery Unraveled, follows with a beginning that leads step-by-step to a fully developed system with accurate data at all levels. Breaking it down so the all sides of the organization can go as far or as long as the need requires, he competently presents the mystery and systematically unravels it to its logical ending.
James Seymour’s tag cloud