Skip Navigation Links
Home
Overview
Features
Lifecycle
Downloads
Support
Purchase
Skip Navigation Links.
                  Design:
Click for larger image. Click for larger image. Click for larger image.
1) Provides ratings (0-100%)
    relative your database design.
Click for larger image. 
  • Overall
  • Integrity
  • Quality
  • Performance
  • Readability
NOTE: a 65% is not a passing grade; a passing grade is an 90%.
2) Identifies Integrity issues: 
Click for larger image.
  • Tables without Primary Key
  • Tables without logical unique key
  • Indexes with questionable uniqueness
  • Columns without foreign keys, which should be referencing a reference table
  • Columns in need of a constraint
3) Identifies Quality issues:
  • Tables with an identity column that do not have a Primary Key
  • Lonely tables, tables that do not reference any other table nor are referenced by another table
  • Column names used in more than one table with an inconsistent type.
  • Repeated Column Name appended with a number
4) Identifies Performance issues:
  • One or more primary key segments are not marked as identity.
  • Multiple segmented primary key. Define a single segmented primary key with an identity.



5) Identifies Readability issues:
  • The column name starts with the name of the table
  • A primary key should be the first column for the table
  • A column name of “Id” should be reserved for a Primary key

6) Generate Sql to fix these
     issues at the click of a button
Click for larger image.

A good design of any database is important, and the real question is, how good is your design? Just knowing that the rating of a database is less then stellar, while important, is only the first step. Second, you need to know what and where the specific problems are. Third, and last, you must fix these problems.

SqlTac addresses all of these items. SqlTac will provide an overall rating of your database (0-100), and identify specific items needing attention. We will classify each item as an Integrity, Quality, Performance or Readability issue. But wait, there’s more: SqlTac will fix many of the issues which it uncovers. Do not to wait until you have completely finished your design. SqlTac should be constantly run on a database during the Design phase. Run SqlTac after adding or modifying each table to minimize the impact and localize the possible corrections which might need to be performed. See the Design for specifics.
         Time is money!
 How much are you wasting?
SqlTac provides the Answers
                                                                                     Copyright © 2006-2010 Caber Computing, Inc. All rights reserved.