August 6, 2014 at 3:01 pm
I was wondering if anyone had a form or suggestions to get me started with questions for a PM when asked to create a new database for an application?
So far:
•What is the data archive/purge strategy, or how long does the data need to be retained? Does the application manage this or will it need to be managed at the database level?
•What is the recovery time objective (i.e. how much downtime is acceptable is a disaster recovery situation)?
•What is the recovery point objective (i.e. how much data loss or work loss is acceptable in a disaster recovery situation)?
•Are there any requirements that differe from a standard SQL install (e.g collation.)
August 6, 2014 at 4:20 pm
Encryption requirements?
Usage pattern (OLTP, DW, reporting, etc.)?
August 7, 2014 at 2:20 pm
How about Security, who needs access/what kind of access.
August 7, 2014 at 2:48 pm
Are there licensing Implications for a new instance (Database licensing, monitoring software)
Can Instance/Database reside on existing Instance/Database that is supporting the same/similar business function or application? and Will combining the instance/database be causing security risks?
August 7, 2014 at 4:22 pm
Wow, I don't even go near that until I have some conceptual concepts of the model.
IE: Archiving usually only happens on a few tables. Security may or may not be deeply discussed depending on how the application intends to get involved. And other things.
I usually start with "Can I see the thing?" and go from there. Are you in a medical repository and do you need to obey HIPAA, and do the lawyers care about this database? Sure, point in time recovery versus overnight backups and things are definately things to discuss, but that's never where I'd start. You need to know what you're protecting and administrating before you can start to ask intelligent questions and offer solutions for the expectations.
Well, I do, anyway. Don't know about you guys.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
August 8, 2014 at 11:46 am
I think I would start from "What is the data and what application is it there for?", which I suspect is jsust a different way of describing what Craig described as "Can I see the thing?".
Tom
August 8, 2014 at 12:17 pm
Thanks for the flame, now I know why they call you evil:-D Yes you need to start with an understanding of the application. In my experience, all questions must be raised up front too. Typically a meeting with a PM is a learning session for every party involved. The DBA should not assume he knows everything or assume they can figure it out on their own. All the answers given are relevant to the initial conversation, period.
August 8, 2014 at 12:31 pm
JeepHound (8/8/2014)
Thanks for the flame, now I know why they call you evil:-D
Now now, not exactly a flame. 😛 Certainly not aimed at any one of the particular people above me, just the methodology. It seemed to skip the first steps, at least as I perceive them.
All the answers given are relevant to the initial conversation, period.
A perfectly fair statement. It's a branching logic tree though for me as to where you go from there. Example: Sometimes the 3rd party app has to have SA as per the contracts. You can't do anything about that (other than stick it on an isolated instance). Sometimes they've decided to run poorly implemented ORM, so you can't run FULL recovery without a few hundred gigs worth of tran log space.
I just get concerned about open ended questions like this. It's too easy to just take a list, bring it to a meeting, and not understand all the different concepts that goes behind every question you need to ask.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
August 9, 2014 at 10:27 am
churlbut (8/7/2014)
How about Security, who needs access/what kind of access.
+1 Billion. I also want to know if there are things like personally identifiable information (especially tax IDs, CC #s, etc) stored in plain text. I won't even talk at the conceptual level if there are problems with such things.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2014 at 1:06 pm
I'd like to know about the concept of the app accessing data.
Is it through queries constructed at the app side? (including DML statements)?
Is there any "Wannabe-Converter" (like NHyperhate) involved?
How much influence do I have regarding decisions how data access concepts will be designed?
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply