Message-ID: <17045421.1075840446685.JavaMail.evans@thyme>
Date: Fri, 24 May 2002 01:27:00 -0700 (PDT)
From: jeff.duff@enron.com
To: david.miller@enron.com, patricia.hunter@enron.com
Subject: DB Table Additions
Cc: hollis.kimbrough@enron.com, jeff.marecic@enron.com, mark.fisher@enron.com, 
	mark.walker@enron.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Bcc: hollis.kimbrough@enron.com, jeff.marecic@enron.com, mark.fisher@enron.com, 
	mark.walker@enron.com
X-From: Jeff Duff
X-To: David Miller, Patricia Hunter
X-cc: Hollis Kimbrough, Jeff Marecic, Mark Fisher, Mark V Walker
X-bcc: 
X-Folder: \mark fischer 7-12-02\Notes Folders\All documents
X-Origin: FISCHER-M
X-FileName: mark fischer 7-12-02 LNotes.nsf

To support the data storage of ZMET data here is a proposal for what the 
table structure should be.  In addition, after discussing the status messages 
it is important to differentiate between those which effect availability and 
those that do not.  The FAULTS table includes a flag field INCLUDE which 
serves this purpose for STAR. 

A improvement to this table would be to add a counter description field 
var(4) which would hold one of the following descriptions; SOT, LOT, DT, WOT, 
MT, RT, and EST.  This will allow us do differentiate status messages by 
which counter they are associated with.

Since the intent is to mirror the SQL Server and the STAR db we need to make 
these changes to both.  I'd like to get the SQL server changes ASAP so I can 
develop some additional reports.

Let me know what you think

JD