|
|
|
|
Most software projects fail to capture how the database looked like at any release.
SqlTac will create a single script file containing the database’s entire structure
(Schemas, Tables, Columns, Defaults, Check Constraints, Indexes, Foreign Key, Triggers,
Stored Procedures, View and User Defined Functions). SqlTac determines the dependency
order of all of these items. The sql file generated by SqlTac can be used to recreate
an empty version of your database. This script file now can be checked-in to source
control, which allows you to safely go back to any particular version. |
|
|
|
Before releasing a new version of your database and application, a number of simple
tasks should be performed to provide basic sanity checks.
1) Validate your sql
2) Check the consistency of the data in your database
Many databases contain tens of thousands, some even hundreds of thousands of lines
of Sql (Stored Procedures, Views, User-Defined Functions, Triggers, Check Constraints
and Default values). Do all of your Sql statements still compile after all of the
database modifications that have been made to support your current release? SqlTac
will attempt to re-compile of these items at a click of the mouse. It will report
and any and all items which fail to compile, and allow you to edit and correct those
items right inside of SqlTac.
You would be surprised how many times a database is shipped with orphan data. This
can be a serious red flag. SqlTac checks all foreign tables to determine if any
orphans exist. SqlTac will report just the tables and a count of orphans in those
tables. With a click of the mouse, SqlTac will show you those orphans.
SqlTac can be used to show any structure and sql changes between any two versions
of your database. So make sure you keep a copy of database for each version you
ship. This simple step will allow SqlTac to save you a ton of hours, at one of pressure
sensitive time in the lifecycle of your product.
|
|
|
|
1) Validates all of Sql.
|
 |
- Stored Procs
- User Defined Functions
- Triggers
- Check constraints
- Computed Columns
|
Sql will not only report any Sql items which will not compile, but will allow you
to correct the Sql right inside of SqlTac. |
2) Check the consistency of your database
|
|
Detect any orphans before you ship. |
|
|
|
|
3) Back up your schema and document at the click of a button
|
 |
|
4) Diff your database to be any previous release.
|
 |
|
|
|