Database/Application Documentation

1 Oct 2005 3:47 AM

Chad

Just general thoughts...

It seems to me that there is a lack of compile time binding between a .NET
application and the a SQL server database.

Can someone suggest the best way to do things like
-identify stored procedures that are no longer being used by an application
-genrerate a call tree of .NET classes and modules which flows all the way
to database SPs.

Is using strongly typed classes, something i am not very familiar with,
helpful?

I've looked at Project Anayzer by Avisio and the output is confusing.

Does Rational have something to help document an application that spans
tiers by analyzing the code?
Is the output quality or quantity?

1 Oct 2005 10:02 AM

SQL

You could run a trace on the server and analyze the output for missing
procedures

http://sqlservercode.blogspot.com/

Show quote

"Chad" wrote:

> Just general thoughts...
>
> It seems to me that there is a lack of compile time binding between a .NET
> application and the a SQL server database.
>
> Can someone suggest the best way to do things like
> -identify stored procedures that are no longer being used by an application
> -genrerate a call tree of .NET classes and modules which flows all the way
> to database SPs.
>
> Is using strongly typed classes, something i am not very familiar with,
> helpful?
>
> I've looked at Project Anayzer by Avisio and the output is confusing.
>
> Does Rational have something to help document an application that spans
> tiers by analyzing the code?
> Is the output quality or quantity?
>
>
>
>
>

4 Oct 2005 12:11 AM

Mary Chipman [MSFT]

That is correct. When you compile a .NET application, it only compiles
the managed code. SQL Server objects are considered to be external
resources, and are not compiled or checked in any way. Only the
provider syntax is checked, embedded strings, parameters and SQL
statements are not. There are other Microsoft partners who provide
third-party tools, which you may like better than the one you tried. I
used FMS analyzer a long time ago, which I liked at the time, but I've
not kept up with the available tools. See
http://www.microsoft.com/sql/partners/dbtools.asp for a complete list.

--Mary

On Fri, 30 Sep 2005 23:47:54 -0400, "Chad"
<chad.dokmanov***@unisys.com> wrote:

Show quote

>Just general thoughts...
>
>It seems to me that there is a lack of compile time binding between a .NET
>application and the a SQL server database.
>
>Can someone suggest the best way to do things like
>-identify stored procedures that are no longer being used by an application
>-genrerate a call tree of .NET classes and modules which flows all the way
>to database SPs.
>
>Is using strongly typed classes, something i am not very familiar with,
>helpful?
>
>I've looked at Project Anayzer by Avisio and the output is confusing.
>
>Does Rational have something to help document an application that spans
>tiers by analyzing the code?
>Is the output quality or quantity?
>
>
>