on 11-12-2007 10:16 AM
Hi forum,
SQL Studio and Database Manager are great tools in most of cases. I would need better tools for managing datas and databases.
My main aim would be a database upgrading tool. I mean a MaxDB complient tool to add/remove/update tables, stored proc, cursors and so on between an A and a B MaxDB database.
Well a MaxDB database versionning tool.
King regards
LiquiBase recently added support for MaxDB <a href="http://www.liquibase.org">http://www.liquibase.org</a>.
LiquiBase is an LGPL Java-based tool for managing and applying database changes.
I ran across this messaging looking for somewhere to mention that MaxDB support has been added. Is there a good place for that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oughhh I don't know if your reply is a good new or not 😛
I think it's a good one because I would probably have been betrayed by
the tool when becoming too confident in it's rightness. But it's also
a bad one because the working scheme you describe requires a lot of
work a lot of time and time is money We are a team of two
programmers. How to ensure one of us won't forget something ? And what
if our team grows ? In the meantime we'll have to find the best
organization scheme not to forget any of the changes...
It would be tricky if there would be a MaxDB log analyser tool which
would provide such features :
- human readable activities
- filter between two dates statements which modify the database
structure (as they are identified by SQL syntax it is possible)
- export filter results to a text file
it would ease the job 😛
kind regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vincent,
It would be tricky if there would be a MaxDB log analyser tool which
would provide such features :
[...]
it would ease the job 😛
Well,here I disagree.
Of course it would be nice to be be able to just "diff" two states of a database and get a script that performs the transition between these two.
BUT: how can you be sure, that the last state of your database is the one you want to deliver? Basically you can't,
How do you get back a database structure for version 6 of your program when your current development is on version 12?
Using a version control management also for the database structures is the only way to be able to define a release version of all your coding.
Think of database structure as part of your code - than it's obvious to put it into source control isn't it?
Concerning the additional effort: it's possible for sure to do all development without any version control, yes.
But I heavily doubt that you are more efficient by doing so.
Using a source control makes your development manageable from a central point - that's nice for a single programmer but necessary when more people get involved.
Hope that helps your decision.
KR Lars
> BUT: how can you be sure, that the last state of your database is the one you want to deliver? Basically you can't,
> How do you get back a database structure for version 6 of your program when your current development is on version 12?
The idea would be to have a reference database (v1 of the software), a frozen for release database (v2 of the software) and a dev database (v2.x until I freeze it). Thanks to filters I'd know what happened between two states and I'd be able to update my customers databases.
Anyway it was just an hypothesis and I agree with your way to manage versioning. We already use Subversion to manage our delphi code. It's pretty efficient. Doing it with MaxDB will need a lot more of attention and care but should be alright.
Thank you for the analysis.
Hello,
thanks for all answers
I'm happy with MaxDB as Database Engine but I'm suffering not finding
enough third parties software. By example I'm wondering how you folks
are managing database versioning. Do you write every ALTER,UPDATE...
on a paper ? Have you created a specific tool to generate a script to
move from a v1 database model to a v2 model (Tables, procedures, views, triggers) ? Have you found a tool I
don't know ?
Kind regards
Vincent
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vincent,
database versioning is a problem for most DBMS.
Since the database objects are actually part of your code you should save the definition into scriptfiles and keep them together with your application code in your versioning repository like CVS or MS SourceSafe.
I used to use MS VISIO as a data modelling tool, generated the DDL and saved the VISIO file AND the DDL script in SourceSafe together with the application code.
With other tools like MaxDB Databasestudio or the SQUIRREL SQL client you can create scripts for the changes to db objects you want to apply.
Usually (and I know that it is quite a common practise) it is not a good idea to modify db objects directly in your development database and then use a kind of "database diff"-tool (like the one in TOAD) to generate your "Upgrade"-scripts.
Better take the "longer walk" and put each and everything into a script and the script into the version control.
Once you're done with your development, assemble the scripts and perform a upgrade of a testinstance.
KR Lars
Hello Vincent,
1) The Installation Manager for the MaxDB software is a graphical interface tool enabling
you to install the entire MaxDB software package or individual software components and
also create, upgrade and uninstall a database instance.
Please see more information at
"Using the Installation Manager" < SDBSETUP > at
http://maxdb.sap.com/currentdoc/74/df234239f75733e10000000a155106/content.htm
< And all MAXDB users could review the documentations to install the MAXDB
at https://www.sdn.sap.com/irj/sdn/maxdb
< -> "Installation on MS Windows and Linux" >
<-> The Complete MaxDB Documentation Set -> Installation >>
2) You could use the dbmcli & sqlcli tools. Documentation available at
http://maxdb.sap.com/currentdoc/default.htm ->
"Database Manager CLI" & SQLCLI < Database tools >
3) Please also review documentation on the database tools "Loader" & "Synchronization Manager"
at http://maxdb.sap.com/currentdoc/default.htm ->Tools
And Loader Tutorial shows examples for commands of the Loader tool for exporting and importing data.
Thank you and best regards, Natalia Khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
A new Open-source project (java/jsp) could help you to manage your DB. It's a kind of phpMyAdmin, but written in JSP and multi DB (Maxdb/Sapdb , mysql and oracle for the moment).
http://sourceforge.net/projects/db-everywhere/
Regards,
Greg
Hi Vincent,
the first thing you should have a look on is the new DB Studio (check my
<a href="/people/lars.breddemann/blog/2007/10/15/maxdb-database-studio-77-is-available for details).
If this is not fulfilling your needs, than you might want to have a quick google
<a href="http://www.google.com/search?q=maxdb%20sql">http://www.google.com/search?q=maxdb%20sql</a>
There are some 3rd Party tools - to be honest I've not used them yet.
Actually I'm not too sure about what you really want to do (moving cursors??)... are you looking for a database synchronization?
If you're looking for a kind of schema versioning, than you'll likely to be lost in the open source area. Most development/design tools I know that are capable of things like that are not for free.
Best regards,
Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
71 | |
26 | |
10 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.