I first found SqlBuddy when looking for something with a decent schema report. That's an area I would really like to see expanded upon that probably wouldn't be too hard.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This area isn't too hard to expand upon really. Could you post a rough spec of what you'd like to see. I can't promist instant results, but it might be something myself or someone else could have a stab at.
Thanks for your interest, and sorry for the delay in responding!
Tobin Harris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In addition to displaying the sizes of the fields as mentioned in my other post on the subject I'd really like to see the following:
1. A saved Tools->Options value for whether or not to open reports in a separate browser window.
2. A print option dialog on the "View Schema Report" for a database.
2a. At a minimum I'd like to be able to include/exclude tables, stored procedures, functions, and views as well as the option to include/exclude objects not owned by the current user.
2b. Additional input fields for from/to object name would be nice but not absolutely necessary particularly since that wouldn't be useful unless restricting the object type to one particular option.
2c. For tables the option to include/exclude index information and column descriptions. The primary key field is already in bold on the report.
2d. For stored procedures and functions
3. The default values don't show on the report. This is more of something that wasn't implemented yet but was on the report.
4. Add table details for table description, owner, and create date.
5. The optional column description could be either at the end of the line with a fixed width and multiple lines or on the line below the column information; i.e. wrap the description to the same starting position on each line rather than creating a long horizontal scroll if there is a long one.
6. Use the same code to format a single table report that you use for the schema report. That way they look the same and don't have to be maintained separately.
7. Get the datatype and size of the stored procedure and function parameters.
I think this would show what most users would need.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I first found SqlBuddy when looking for something with a decent schema report. That's an area I would really like to see expanded upon that probably wouldn't be too hard.
This area isn't too hard to expand upon really. Could you post a rough spec of what you'd like to see. I can't promist instant results, but it might be something myself or someone else could have a stab at.
Thanks for your interest, and sorry for the delay in responding!
Tobin Harris
In addition to displaying the sizes of the fields as mentioned in my other post on the subject I'd really like to see the following:
1. A saved Tools->Options value for whether or not to open reports in a separate browser window.
2. A print option dialog on the "View Schema Report" for a database.
2a. At a minimum I'd like to be able to include/exclude tables, stored procedures, functions, and views as well as the option to include/exclude objects not owned by the current user.
2b. Additional input fields for from/to object name would be nice but not absolutely necessary particularly since that wouldn't be useful unless restricting the object type to one particular option.
2c. For tables the option to include/exclude index information and column descriptions. The primary key field is already in bold on the report.
2d. For stored procedures and functions
3. The default values don't show on the report. This is more of something that wasn't implemented yet but was on the report.
4. Add table details for table description, owner, and create date.
5. The optional column description could be either at the end of the line with a fixed width and multiple lines or on the line below the column information; i.e. wrap the description to the same starting position on each line rather than creating a long horizontal scroll if there is a long one.
6. Use the same code to format a single table report that you use for the schema report. That way they look the same and don't have to be maintained separately.
7. Get the datatype and size of the stored procedure and function parameters.
I think this would show what most users would need.
Thanks!
Thanks for that! Especially like the idea of allowing customisable range of objects to report on, and then using this for the single table report.
I'll add this to the TODO list and hopefully we can get some motion on it.
Tobin