Date:         Fri, 12 May 1995 08:08:42 EDT
Reply-To:     The NOMAD2 Discussion List
Sender:       The NOMAD2 Discussion List
From:         "William J. Ryan"
Subject:      Nomad SQL/DS data warehouse

Need advice:

I am working with a company who uses Nomad to access as a corporate data
warehouse for a variety of SQL/DS corporate databases.  One of these is a human
resources database queried by some 100 users.  Currently all of the human
resource database users access SQL/DS through Nomad via a single SQL ID.

The situation: Regularly (each week?) the TRACK_NOMACC table, used to hold SQL
statements generated by the NOMAD SQL/DS interface, apparently fills up, causing
user's queries to fail.  The current work around is to delete stored SQL
statements from TRACK_NOMACC.

Questions:

1. Is this a common situation at other Nomad SQL/DS sites?  Is their work-around
the normal fix?

2. Is this side-effect in any way connected to many users accessing through a
single SQL ID?  Would coming in via individual SQL IDs help the situation?

3. Are there practical strategies to reuse SQL statements, considering the fact
that this is an ad-hoc query environment?

I would appreciate hearing your ideas.

Bill Ryan -- Information Works, Inc.
back to index