AdHoc reporting against SQL 2K w/meta data?

Okay... We have a SQL2K database that has about 500 tables or so. It is normalized to a reasonable level and enforces all relationships with PK/FKs, not triggers. Hence, for a database-minded person it is fairly easy to read (as easy as a 500+ table database can be!).

Our users need adhoc query capabilities. Our report writer is simply overwhelmed. He doesn't need to be spending time writing a report that is intended to be run once.

I expect the best alternative would be to use some sort of adhoc reporting tool that is based off meta data. We (the DBAs) could be responsible for maintaining the meta data and STILL have a manhour savings over developing all these reports.

Here's the catch... We are on a TIGHT budget (aerospace industry is still reeling a bit). Is anyone using a product or aware of a product that might be just the ticket for us? We have been investigating a product by LogiXML called LGX AdHoc (http://www.logixml.com/products/AdHoc/adhoc.htm). Looks promising. Anyone use or familar with it?Can you describe what it does (I didn't find their eval)? I am using ActiveReport from DataDynamics, but it does require some knowledge and time to spend designing reports.sql

Adding drive dependencies to WIN2k/SQL2k cluster resource

I need to add two additional SAN attached volumes to be dependencies
for my SQL Server Cluster resource. Do I have to restart the cluster
service for this to take affect? Is there another way for the cluster
resource to re initialize it's dependencies without restarting?
If you want to create databases on these drives, you need to add them to the
SQL Server resource dependency list. To do that, you don't need to restart
the cluster service. But you do need to take the SQL Server resource offline,
add the drives as the dependencies, and then bring the SQL Server resource
online.
Linchi
"zoneranger@.gmail.com" wrote:

> I need to add two additional SAN attached volumes to be dependencies
> for my SQL Server Cluster resource. Do I have to restart the cluster
> service for this to take affect? Is there another way for the cluster
> resource to re initialize it's dependencies without restarting?
>

Adding column problem

I consulted the SQL2K help for adding a table and copied the code and
substituted my own variables, but I get an error message about incorrect
syntax regarding the AS in line 1. I'm a newbie and am bummed that the code
provided in the help doesn't work--I'm assuming there's something I don't
know here. Here's the code:
---
Dim t_AssessmentItem As SQLDMO.Table
Dim OutputAssessmentLevelID As New SQLDMO.Column
OutputAssessmentLevelID.Name = "ShelfLife"
OutputAssessmentLevelID.Datatype = "CodeID"
OutputAssessmentLevelID.AllowNulls = False
OutputAssessmentLevelID.DRIDefault.Int = "AssessmentLevelID"
Set t_AssessmentItem = _
oSQLServer.Databases("PowerSuasionDevLocal").Tables("t_AssessmentItem")
t_AssessmentItem.BeginAlter
t_AssessmentItem.Columns.Add OutputAssessmentLevelID
t_AssessmentItem.DoAlter
--
Thanks for your help,
karolus> OutputAssessmentLevelID.DRIDefault.Int = "AssessmentLevelID"
I don't see an Int property for the DRIDefault object. You might try
specifying a default constraint name and value instead. For example:
OutputAssessmentLevelID.DRIDefault.Name = "DF_t_AssessmentItem_ShelfLife"
OutputAssessmentLevelID.DRIDefault.Text = "0"
Hope this helps.
Dan Guzman
SQL Server MVP
"Karolus" <Karolus@.discussions.microsoft.com> wrote in message
news:DA68ACB7-098B-4282-92C6-23A24E024C1B@.microsoft.com...
>I consulted the SQL2K help for adding a table and copied the code and
> substituted my own variables, but I get an error message about incorrect
> syntax regarding the AS in line 1. I'm a newbie and am bummed that the
> code
> provided in the help doesn't work--I'm assuming there's something I don't
> know here. Here's the code:
> ---
> Dim t_AssessmentItem As SQLDMO.Table
> Dim OutputAssessmentLevelID As New SQLDMO.Column
> OutputAssessmentLevelID.Name = "ShelfLife"
> OutputAssessmentLevelID.Datatype = "CodeID"
> OutputAssessmentLevelID.AllowNulls = False
> OutputAssessmentLevelID.DRIDefault.Int = "AssessmentLevelID"
> Set t_AssessmentItem = _
> oSQLServer.Databases("PowerSuasionDevLocal").Tables("t_AssessmentItem")
> t_AssessmentItem.BeginAlter
> t_AssessmentItem.Columns.Add OutputAssessmentLevelID
> t_AssessmentItem.DoAlter
> --
> Thanks for your help,
> karolus|||"Karolus" <Karolus@.discussions.microsoft.com> wrote in message
news:DA68ACB7-098B-4282-92C6-23A24E024C1B@.microsoft.com...
> I consulted the SQL2K help for adding a table and copied the code
and
> substituted my own variables, but I get an error message about
incorrect
> syntax regarding the AS in line 1. I'm a newbie and am bummed that
the code
> provided in the help doesn't work--I'm assuming there's something I
don't
> know here. Here's the code:
> ---
> Dim t_AssessmentItem As SQLDMO.Table
> Dim OutputAssessmentLevelID As New SQLDMO.Column
> OutputAssessmentLevelID.Name = "ShelfLife"
> OutputAssessmentLevelID.Datatype = "CodeID"
> OutputAssessmentLevelID.AllowNulls = False
> OutputAssessmentLevelID.DRIDefault.Int = "AssessmentLevelID"
> Set t_AssessmentItem = _
>
oSQLServer.Databases("PowerSuasionDevLocal").Tables("t_AssessmentItem"
)
> t_AssessmentItem.BeginAlter
> t_AssessmentItem.Columns.Add OutputAssessmentLevelID
> t_AssessmentItem.DoAlter
> --
> Thanks for your help,
> karolus
Karolus,
You say your problem is about "incorrect syntax regard the AS in line
1".
It looks like you are using VB/VBA. Have you set a reference to the
"Microsoft SQLDMO Object Library"?
If you haven't, then "SQLDMO.Column" will not work.
Check:
VBA = Tools > References
VB = Project > References
Sincerely,
Chris O.