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 ««12

The Costs of Data Expand / Collapse
Author
Message
Posted Thursday, August 22, 2013 9:11 PM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 4:23 PM
Points: 601, Visits: 1,737
I worked with HIPAA data.

When I was working with the developers, the test DB they would develop against had about 65K rows of patients and about 10 facilities. The production DB had over a million residents and over a 1000 individual facilities.

They had a function that looked up the list of active therapists -- but didn't discriminate by facility id. So the function was returning over 23K lines to look for one out of maybe ten. But using the limited DB it worked well. With the production DB it sucked.

But they would never let me sanitize the Production DB to test or develop with.




----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
Post #1487620
Posted Friday, August 23, 2013 9:33 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, March 10, 2014 5:44 PM
Points: 2,225, Visits: 1,258
Jim P. (8/22/2013)

But they would never let me sanitize the Production DB to test or develop with.


And Jim this is a challenge I face as well, and probably many others.

The confidentiality of the data is seen to be so high that many believe that it should not be replicated, or the physical resources to do it are not seen as too valuable and a waste of space. The problem with this lack of insight and strategy is limiting to those who would like efficiency and a better user experience. And to them the amount of time spent waiting is not an issue as long as they believe the data is safe and the resources as limited as they can be.

Little do these folks realize that a 1 minute wait over 25k transactions a week, or other like metric will add up to a fill salary every month this is foolishness is allowed to continue. And they also do not realize is that any DBA who has the needed password has full access to every bit of data in the system and that the security of that data is already at the mercy of the DBA.

These same people would never let a person tune their car or repair their house without needed testing like doing it on the best guess. They would be horrified to know that their plummer just took their best guess at what was wrong and what was needed to make the water flow at an acceptable rate and thus ended up with a bill of 10k. They want the real testing and real estimate when it involves their money but who knows what drives them when they spend the companies cash.

<End Friday Rant #1>


Not all gray hairs are Dinosaurs!
Post #1487885
Posted Friday, August 23, 2013 8:02 PM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 4:23 PM
Points: 601, Visits: 1,737
Miles Neale (8/23/2013)

<End Friday Rant #1>


That is what I ran into. And then the one that I found that was left alone. I found XML data that was never obfuscated or de-identiified stored in the test DB before me. I had a "s--t-fit" and brought it to management in a way that I was covered and left their butts hanging.

I can't afford +$100K in fines.




----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
Post #1488080
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse