Testers (SQL Server 2005 and up)

[GaryMazzone]

Mods move this if you thing it belongs somewhere else.

I'm working on an application that connects to a SQL Server database (2005 and up only) that will allow a user to see all the information on a table.

i.e. Tab 1 is field information - name datatype, size, defaults, is Identity and Nullable ....
Tab 2 is Referencing tables - Who are my parents - Parent table name, FK name, Key fields in the table and Referencing fields in parent table. Also tables that this on is a Parent of - Child table name, FK name on the child table, and field info again.
Tab 3 is Indexes on the table- Index name, Clustered or Non Clustered, File group the index is on, Is Primary Key, Index Columns and Is Unique
Tab 4 Check constraints - Constraint name and constraint values
Tab 5 Programability - Functions and Stored Procedures that reference the table. Procedure / Function Name, Type ( Function or SP), Date Created, Last Modified Date and SP or Function Text displayed if requested.
Tab 6 Triggers on the table - Trigger name IsUpdate, IsDelete, IsInsert, IsInsteadOf and Status (Enabled or Disabled)
Tab 7 Views that reference the table - View Name, Check Option, Is Updateable, Created date and View code if requested.


I was looking to see if any one would be willing to try the app and let me know of issues improvements.

Thanks

Gary

[RunsWithScissors]

I would love to check it out. I am working on some similar functionality, and would love to see some other approaches. In return, I can certainly let you know what issues, if any, I run into.

I have written a basic SQL and vb code generator (for generating specific, repetitive code related to the creation of CRUD SPROCS and associated vb Data Access classes. I have the mechanics of this part down, but would not mind at all saving some time on the parent and child table associations code.

My goal would be to auto-generate class definitions based upon selected tables in the SQL back-end, which would include functions to return COllections of child items and representation of view data in the SELECT procedure.

I am aware that vs provides alot of this via ADO.Net and Entity Modelling Framework. This has become more of an acedemic excercise than anything else (and a valuable one, at that . . .). However, it is pretty cool to push a button against a SQL server database with a large number of tables and "poof!" there are all my class def's. Obviously, there is some minor "tuning" of some of them, but as a while, I get Nice, consistent vb AND SQL code, just the way I would write it myself. Every time.

Lemme see what you got!