Comments
Sort by recent activity
bill.wehnert wrote:
5. Ability to store all of the extended properties outside of the database so that if something were to happen and you had to rebuild your docs on a backup or on another server, you'd have all of your information available. This would be helpful too if while you are designing you would rather drop the table and rebuild it to put the fields in the order you want. It's a small thing, but would be helpful to me.
Seconded. While another thread has pointed to a script to save and restore these; it would benefit me if the documentation changes could be:
- Stored to a local file/database instead of the descriptions; this way a database can be documented without having to give write access to the schema to documenters.
- Then optionally apply/retrieve those locally saved descriptions TO a database.
I can't believe the original version didn't do things this way. Luckily, I found out during the evaluation period. These are must have's, I'm afraid. / comments
bill.wehnert wrote:
5. Ability to store all of the extended properties outside of the database so that if something were to happen and you had to rebuild your docs on a backup or on another serv...