I design and maintain schema with Notepad script files and ISQL. View/Manage via Foxhound (because it is a real-time, easy to read view). Use PowerDesigner to reverse engineer a diagram when needed for collaboration with outside contractors.

1. No
2. Don't
3. No
4. How do I create and change schema? classic Wordpad and dbisql 99.9%, then Sybase Central.
5. How do I browse actual database schema(1)? Foxhound 99%, then Sybase Central.
6. How do I compare actual database schema(1)? dbunload and CompareIt! 100%

PowerDesigner was once useful but is now bloated and overpriced beyond human comprehension :)

Note 1: "actual database schema" means "as stored in the system tables" as opposed to "as stored in source code scripts".

I use Power Designer in two ways :

1. Before the dev phase to share with others programmers on the major evolution of the database schema.
2. After the dev phase with a reverse engenering on the database schema to create a visible (PDF) and printable document for documentation purpose. This document is a starting point for the reflexion on the next release.

Actually the production databases use SQLA 11.01 (UTF-8) and the next release use SQLA 16. I have a problem with Power Designer that don't support the column defined as CHAR(10 CHAR). Could you do something about that ?

Only use PowerDesigner very occasionally, basically when someone insists in having a pretty ER diagram - with hundreds of tables it never does them any good - but they don't believe that 'till they have it! Easier to use Sybase Central to produce localised ER diagrams of a particular group of tables.

Development of data structures done in notepad / isql / Sybase Central (the copy & paste of data objects from Sybase Central is particularly useful).

Once in production - our applications have an internal model of the database structure appropriate for their version and when run in update mode will execute the necessary DDL (and possibly SQL) to bring the database structure up-to-date and carry out any data migration required.

Yes, we use PowerDesigner to design and maintain our database schemas. We export the sql from PowerDesigner and run it through ISQL. We have no other licensed copies other than what we get through our SQL Anywhere licensing. We would be extremely disappointed to lose yet another component (already lost Infomaker, which we use) of the SQL Anywhere releases.

1. Yes, we use PD to maintain the tables, views, triggers and store procedure for two of our older products. PD is then used to generated update scripts based on the different model versions.
2. Many of the changes to the model were previously edits in Sybase Central, pasted from the database log window and inserted in PD.
3. No, we're only using the physical model.

Our latest product was designed to be self-generating, so it keeps all model (meta-) data in it's database, no need for PD anymore.