Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Application Developers don’t own their data Expand / Collapse
Author
Message
Posted Saturday, June 28, 2014 12:30 PM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, November 10, 2014 12:04 PM
Points: 590, Visits: 2,565
Comments posted to this topic are about the item Application Developers don’t own their data


Best wishes,

Phil Factor
Simple Talk
Post #1587220
Posted Saturday, June 28, 2014 7:46 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, November 20, 2014 10:45 AM
Points: 14, Visits: 29
I wouldn't take "my" data to mean at the exclusion of others. It is a declaration of ownership, but usually in the context of taking responsibility for the data. That is a good trait for a developer to have and is much better than saying, "It's not my fault." or "That's not my job." Sometimes you have to take the good with the bad.
Post #1587288
Posted Sunday, June 29, 2014 11:49 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 9:17 AM
Points: 419, Visits: 1,187
Jeff Oresik (6/28/2014)
I wouldn't take "my" data to mean at the exclusion of others. It is a declaration of ownership, but usually in the context of taking responsibility for the data. That is a good trait for a developer to have and is much better than saying, "It's not my fault." or "That's not my job." Sometimes you have to take the good with the bad.


I agree. That's generally how I've used the term owned and generally how I've heard it used.

However, there are certainly those who 'own' data or an application and don't want anyone else touching it even when there are legitimate reasons.
And I have to admit that I have sometimes had to fight that tendancy in myself.
Post #1587460
Posted Sunday, June 29, 2014 6:56 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:44 PM
Points: 7,153, Visits: 15,639
marcia.j.wilson (6/29/2014)
Jeff Oresik (6/28/2014)
I wouldn't take "my" data to mean at the exclusion of others. It is a declaration of ownership, but usually in the context of taking responsibility for the data. That is a good trait for a developer to have and is much better than saying, "It's not my fault." or "That's not my job." Sometimes you have to take the good with the bad.


I agree. That's generally how I've used the term owned and generally how I've heard it used.

However, there are certainly those who 'own' data or an application and don't want anyone else touching it even when there are legitimate reasons.
And I have to admit that I have sometimes had to fight that tendancy in myself.


We internally have been having a lot of discourse around this concept of ownership. I think Phil's usage of custodianship rather than ownership makes sense from a dev or DBA point of view: we're responsible for making sure that the data is accurate and available. However our sphere of influence stops before it comes to deciding how long we hold onto that data, which is where the "true" owner needs to step in (the business stakeholders).



----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Post #1587489
Posted Sunday, June 29, 2014 7:27 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 5:52 PM
Points: 22, Visits: 131
You can often tell who owns data by asking who has the right to delete it.
Post #1587490
Posted Monday, June 30, 2014 3:03 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:42 AM
Points: 5,745, Visits: 3,670
As someone coming from the developers' side of the fence, with regards to the attitude of ownership of the data then developers (where there is a DBA function) do not own but are in part responsible for the data. This sits alongside a lot of other peoples' responsibility for the integrity of the data e.g. data entry teams.

I have talked about the data "being mine" against a DBA when in a development environment (where the developers define the database structure and develop the stored procedures) where a database has been assigned for the sole use of the development team (which may include a DB Developer) and a DBA external to the team has altered the schema in some way or removed or altered the data.


Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1587533
Posted Wednesday, July 9, 2014 7:57 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 13, 2014 6:02 AM
Points: 32, Visits: 125
Hi Phil,

I seek your help on this.....

Please help me on this.

I have 3 tables

Table A:- Driver Table

CAT Code, Parttype, BasePartNo, LikePartNo

MCN, FLOORMAT, MCNW10, MCNW10**

MCN, FLRLNR, MCN444410, MCN4*4410

Table B:- Build Table

CAT Code, Parttype, BasePartNo, LikePartNo1, LikePartNo2... LikePartNo50

MCN, FLOORMAT, MCNW10, MCNW10TN, MCNW10GR,-,-

MCN, FLRLNR, MCN444410, MCN454410, MCN464410,-,-

Table C:-

Application Table

make, model, year, remarks , part#, remarks2, footnote_list

58, 747, 2003, L; Automatic Trans, MCNW10TN, 2.0L, E009

58, 747, 2002, Base; Automatic Trans, MCNW10TN, 2.0L, E009

Requirement is like this:- Retrieve Application field like make,model as in application table for Basepart and Like Part Nos.
Run comparison between basepart and like part No in application table and build Report which must contain if any mismatch In make model etc..
i.e make model,remarks.. etc for basepart is not equal to the make, model, remarks etc... for likepartnos



Attribute means: make,model,year etc.. make model year,Model,part#,application#,remarks2,remarks3

for eg:-

likepart Attributes--

63,6853,2010,Silverado1500,MCNW10GR,5155634,5.7L,Rear

likepart Attributes

63,6853,2011,Silverado1500, MCNW10TN,5155640,5.3L,back

BasePart Attribute

63,6853, 2010, Silverado1500,MCNW10,5155640, 5.3L, Rear

Here attributes for base part is correct and act as a reference, and if likepart contain other attributes it should appear in result.

Result

63,6853,2010,Silverado1500, MCNW10GR, 5155634,5.7L, Rear

63,6853,2011,Silverado1500, MCNW10TN, 5155640,5.3L, back


Make, model,year,remarks.... etc for base part number need to compare it with Make, model,year,remarks.... etc for likepartnumber in application table.
here application table contain the part which is present in either likepartnumber1,likepartnumber2... likepartnumber50 of Build Table
so the comparison is need to be done with application data like make,model.. etc for base partnumber
to the application data like make,model.. etc for likepartnumber in application table

Thanks a ton....
Post #1590757
Posted Thursday, July 10, 2014 12:55 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 8:39 AM
Points: 3,277, Visits: 3,549
Agreed - I.T. departments rarely own data, they may protect it, manipulate it, distribute it and so on, but they don't own it. Other departments own it, it is however, from my experience, is IT's responsibility to fix when "it's not right"

-------------------------------
Posting Data Etiquette - Jeff Moden
Smart way to ask a question

There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan
I would never join a club that would allow me as a member - Groucho Marx
Post #1591021
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse