datamarts

what are the advantages of building a datamart in sql server as opposed to DB2 or vice versa?? any thoughts would be appreciated.the biggest one is analysis services are free in sql.|||This would go back to the same arguments for any software purchase. My criteria is usually what do you have the most experience in at your shop. Database software at this level is getting pretty generic. SQL Server, DB2, and Oracle do mostly the same things, and generally have their shares of rabid followers. Look around your shop, and if you have mostly SQL experts, then go with SQL. If you have more DB2 expertise, go with DB2. The cost of ownership will be less, if you do not have to send people out for a lot of training, and spend needless hours chasing simple problems that experienced people would laugh at.

Database/Application Documentation

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?You could run a trace on the server and analyze the output for missing
procedures
http://sqlservercode.blogspot.com/
"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 applicatio
n
> -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?
>
>
>|||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.dokmanovich@.unisys.com> 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?
>
>