Conference ulysse::rdb_vms_competition

    Rick,
    
    I have developed some Case Histories of actual Rdb implementations. 
    These case histories are non-attrituable, but are based upon customers
    listed in VTX reference exchange.  The case histories can be accessed
    in:
    
                CIMNET::PRODUCTS$PUBLIC:CASE_HIST_*.PS
    
    Unfortunatly I do not have all of the information that you request
    regarding size of the database, cpu, or number of disks.  These case
    histories are useful to show that Digital's information management
    products are being used in actual production applicaations.  Contact
    me if you need to find the Digital account rep for any of the Case
    Histories that we have developed.

 So it "looks as though" there aren't any large production databases out there?

 Are large (10-30Gb) Rdb databases 'fact or fiction'?

 I have been trying to find some large production database sites, no even as a 
 formal reference site, just to find out how they might get around some of the
 maintenance issues, wihtout any luck.

  Plenty of:   	- yea I was going to....
	      	- yea I am going to.....
		- yea I thought about it....
  but No	- yea I've done that.

  Even just a few war stories would be better than the deafly silence this note
  has received.

  I know they must be out there and I have heard of a few.  It is going to be much
  easier to sell large Db's is the customer is comfortable in the fact they aren't
  going to be the first.

   Everyone seems happy to say we can do it but few people seem willing to say they
   have done it.  Come on.

	Any bites
	Vince

	Looking for a few large DB reference site to talk about ;^) 

    
    
    What you're seeing is a massive breakdown in Digital's Reference
    Account systems.  Several factors have led to this:
    
    1 - there is no reward whatsoever for a customer to be one...
    
    2 - Account Managers don't want to spend their time supporting the
        program
    
    3 - the few that we have had (Census is a classic case) have been
        pestered soooo much that they dropped out!
    
    4 - no coodination or consistency across area boundries
    
    
    Large databases are a FACT.  We're supporting them now.  But it is
    illegal to hand their names out unless they specificly give us
    permission.
    
    -Steve

Thanks for the answer to a intentionally provocative note.  

So I understand that reference sites are as scarce as hens teeth and this is 
a problem. But all the same in trying to sell a large database, 
	- you know that it has be done
	- I believe that it has been done

So where does our credability come from - just hear-say.  It would be a lot 
easier if the prospect could be told that we know of x number of sites with
approx. x number of Gb running on an X machine with X number of TPS. This kind 
of information does not need to be reference site material, just reference 
material.

If GIA cannot provide any informal (no names) information and Corporate cannot 
provide any such information, then I give up!!

Vincent

    
    I agree with Steve's comments completly, That is why I've been trying
    to develope non-attrituable Case Histories of actual implementations.
    The problem is getting cooperation from the field.  Everyone wants
    references, but no one will take the time or effort to noninate their
    account.
    
    See note .1
    
      One example of the Case Histories  contains a fairly large internal
      Digital Database.  The site is Digital's Field Manufacturing
      Information Center.  They have a 10 Gb DB  containing 24 million
      records  stored across 13 RA90 disk drives.  This is just one example
      of the Case Histories that I have compiled to date.  The others don't
      have statistics describing the size of the database, but they do
      describe large production applications.
    
      If anyone is working in a manufacturing account and knows of a
      production application using Rdb, I would be happy to write up a
      case history

    
    OK, we all agree that Rdb reference sites are a problem!!!
    
    Now, who in Digital is responsible for making sure we have reference
    sites?  I certainly do not think it should be engineering, they have
    enough to do.
    
    So who is it?
    
    Michael

    
    
    It has been a field program which varies from area to area.  U.S. Area
    had a system...which eventually became the VTX system that is in use,
    but as you know not very helpful.  I have contacted several people
    about the problem and hopefully we'll see some improvement.  As a
    Product Manager (is that what I am?) I fully understand the importance
    of good references...but alas I do not have the resources to manage
    them...as The New Software Group (TNSG for short) get's better
    organized perhaps we'll see some resource!
    
    -Steve

    Thanks Steve.  Hope to see an improvement soon !!!
    
    Cheers,
    Michael