BibSonomy ::  user :: gresch ::

AutoPatch was born from the needs of using an agile development process while working on systems that have persistent storage. Without AutoPatch, developers usually can't afford the maintenance headache of their own database, and DBAs are required just to apply changes to all of the various environments a serious development effort requires. The very application of database changes becomes an inefficient, error-prone, expensive process, all conspiring to discourage any refactoring that touches the model, or being a bottleneck when model changes are made. AutoPatch solves this problem, completely. With AutoPatch, an agile development process that requires a database change looks like this: * Developer alters the model, which requires a change to the database * Developer possibly consults a DBA, and develops a SQL patch against their personal database that implements the alteration * Developer commits the patch to source control at the same time as they commit their dependent code * Other developers' and environments' databases are automatically updated by AutoPatch the next time the new source is run This represents streamlined environment maintenance, allowing developers to cheaply have their own databases and all databases to stay in synch with massively lower costs and no environment skew. That's what AutoPatch does. Clusters with one database? Multiple schemas? Logical migrations, instead of just DDL changes? Need to do something special/custom? Need to distribute your changes commercially? All without paying anything? No problem.

RESTORE DATABASE Example. MS SQL is a pain, pain, pain. Hint: Use e.g. RESTORE FILELISTONLY FROM DISK='C:\MyData.bak' to get the necessary information. Here the command from the cited blog entry: ALTER DATABASE MyData SET SINGLE_USER WITH ROLLBACK IMMEDIATE RESTORE DATABASE MyData FROM DISK = 'C\:BackupMyData.bak' WITH MOVE 'MyData_Data' TO 'C:\Data\datafile.mdf', MOVE 'MyData_Log' TO 'C:\Data\logfile.ldf', REPLACE

The agimatec tools contain some utilities to enable generation of files, source code etc. from sql files and annotated java classes. The agimatec-dbmigrate tool is a database migration/script execution framework that can execute sql scripts, groovy scripts and provides a lot of features to assist in database schema migration. (tested with Oracle and Postgres)

Data Architects, DBA's, Analysts and Designers rely on Data Modeling tools to facilitate and simplify their data Modeling efforts, while maximizing the use of their resources. The Power*Architect allows these busy highly technical resources to perform this most intricate part of their job in a fraction of the time. The Power*Architect is a user-friendly data modeling tool created by data warehouse designers, and has many unique features geared specifically for the data warehouse architect. It allows users to reverse-engineer existing databases, perform data profiling on source databases, and auto-generate ETL metadata. Plus, the Power*Architect has the ability to take snapshots of database structures, allowing users to design DW data models while working offline. Whether you are building a Data Warehouse or using data models to communicate business rules, the Power*Architect will facilitate and automate your data modeling efforts.