Re: Hiding data model
Date: Fri, 30 Jan 2015 09:55:52 +0530
Message-ID: <CAEWC_QBe2GeLSQGExEDAY6rwKANs9RtO3-fbJyguKr3Wa7uPEw_at_mail.gmail.com>
Stefan.. I dont think mgmt will go for this due to high cost
Totally agreed with your suggestions.. i cant stop laughing at the innovative solutions of cutting cables with scissors and writing names in Latin !!!
Thanks,
Harmandeep Singh
On Thu, Jan 29, 2015 at 6:08 PM, Niall Litchfield < niall.litchfield_at_gmail.com> wrote:
> <serious>
> I'd suggest that the data model is extremely unlikely to form worthwhile
> IP for your company in and of itself (and if it does, well of course you'll
> want to consult an IP lawyer), unless you are also supplying support and
> maintenance contracts for the database (that is you are acting as DBA for
> the customer). The names and data types of objects and columns are
> important information for support staff to be able to do their job
> effectively. Hiding this from them against a threat of IP theft when there
> are perfectly good alternatives seems to be setting yourselves up for bad
> customer relationships.
> <serious>
>
> <not so serious>
> If you wish to obscure it from customers, can I suggest that Latin or
> Ancient Greek might make excellent languages to name your objects and
> columns in. Your programmers undoubtedly love learning new languages so I'm
> sure they'll be all for it.
> <not so serious>
>
> On Thu, Jan 29, 2015 at 4:34 AM, Harmandeep Singh <singh.bedi_at_gmail.com>
> wrote:
>
>> Thanks all for the inputs. I am going to use your inputs as perfect
>> support to my answer
>>
>> Best Regards,
>> Harmandeep Singh
>>
>> On Thu, Jan 29, 2015 at 3:56 AM, MARK BRINSMEAD <mark.brinsmead_at_gmail.com
>> > wrote:
>>
>>> Indeed.
>>>
>>> There have been many times where I have contacted software vendors to
>>> report errors in their application code, or even their design. And to
>>> supply the fixes.
>>>
>>> Why would you choose to cut yourself off from thousands of free
>>> troubleshooters, some of whom are probably better than any you can afford
>>> to keep on your own payroll?
>>>
>>> That aside, a common side-activity for DBAs is to *evaluate*
>>> potential software purchases. When faced with competing products, one with
>>> a well-documented data model and the other with a "closed" or "obfuscated"
>>> data model, I will always favour the open one. The better I am able to
>>> understand a product, the better I am able to support it.
>>>
>>> You can be certain that an obfuscated data dictionary will shut you
>>> out of at least some sales opportunities.
>>>
>>>
>>> On Wed, Jan 28, 2015 at 3:15 PM, Hans Forbrich <
>>> fuzzy.graybeard_at_gmail.com> wrote:
>>>
>>>> On 28/01/2015 4:39 AM, Harmandeep Singh wrote:
>>>>
>>>>> Hi Experts,
>>>>>
>>>>> We are having data model for our product, which we do not want to
>>>>> expose to our customers. That is we want even the DBA of customer with sys
>>>>> privileges should not understand /access the data model( like table
>>>>> definitions, columns ).
>>>>>
>>>>> I am aware of options like VPD, which is data level security feature
>>>>> as per my understanding.
>>>>>
>>>>> Please let me know your thoughts
>>>>>
>>>>> Thanks,
>>>>> Harmandeep Singh
>>>>>
>>>>>
>>>> One solution - put the protection into the contract. Model leaks out,
>>>> you get to sue the customer.
>>>>
>>>> Otherwise, realize that the data dictionary (which is different from,
>>>> albeit related to, the data model) is the primary tool the DBA has to
>>>> ensuring your product can be secured and tuned.
>>>>
>>>> The DBAs are actually on your side. Why tick them off?
>>>> /Hans
>>>> --
>>>> http://www.freelists.org/webpage/oracle-l
>>>>
>>>>
>>>>
>>>
>>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Jan 30 2015 - 05:25:52 CET