Liquibase Community Forum
2010-11-10 10:32:02 UTC
A new topic, 'MSSQL2005: Controll tables allways in [dbo]-schema (using 2.0-RC7)', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=778.new#new
The text of the topic is shown below:
Hi all,
I am trying to run some scripts against a MS SQl 2005-DB. That works so far, but LB creates its controll tables (DATABASECHANGELOG, DATABASECHANGELOGLOCK) in the [dbo]-schema (assuming that the DB user has privs to write into the dbo schema) instead of the target schema where the DB objects of the scripts reside. This behaviour seems different from implementations of Oracle and DB2 for which the controll tables are created in the target schema (as far as I noticed).
If I run a dropAllDatabaseObjects (Ant) transaction against a MS SQL 2005 target schema LB creates additional controll tables in the very target schema. This latter case seems somehow strange.
Frank
Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.
You can see it at
http://liquibase.org/forum/index.php?topic=778.new#new
The text of the topic is shown below:
Hi all,
I am trying to run some scripts against a MS SQl 2005-DB. That works so far, but LB creates its controll tables (DATABASECHANGELOG, DATABASECHANGELOGLOCK) in the [dbo]-schema (assuming that the DB user has privs to write into the dbo schema) instead of the target schema where the DB objects of the scripts reside. This behaviour seems different from implementations of Oracle and DB2 for which the controll tables are created in the target schema (as far as I noticed).
If I run a dropAllDatabaseObjects (Ant) transaction against a MS SQL 2005 target schema LB creates additional controll tables in the very target schema. This latter case seems somehow strange.
Frank
Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.