Designing Database Architecture - What Does this Mean?

  • I work with SQL databases on a high level... meaning I run queries and stored procedures, and backup/restore databases on the regular. I want to apply for a position that involves a little bit more in-depth SQL work, where I would be "working with Development staff to develop database architectures coding standards."

    What does this mean, and do you guys recommend an Internet resource that I can reference to learn more about this so that I can sound like I'm at least familiar with such practices, if I'm granted an interview?

  • I just came across this blog post, I will start here. Looks like it's on-topic.

  • vadon97 (1/31/2011)


    I work with SQL databases on a high level... meaning I run queries and stored procedures, and backup/restore databases on the regular. I want to apply for a position that involves a little bit more in-depth SQL work, where I would be "working with Development staff to develop database architectures coding standards."

    What does this mean, and do you guys recommend an Internet resource that I can reference to learn more about this so that I can sound like I'm at least familiar with such practices, if I'm granted an interview?

    You're looking for information to begin research so I'll do my best to be kind here.

    In specific:

    so that I can sound like I'm at least familiar with such practices

    Scares the living bejeezus out of me. I almost skipped this to let someone else come by and chew on you. However... I don't think you phrased that the way you actually meant it.

    A database architect and a database developer are actually two separate job items. I recently did an article on this so if you don't mind some self-referencing, check this out: http://www.sqlservercentral.com/articles/Career/71608/

    So, to answer your question, what you're looking for is database design standards. You want to look into normalization. You want to look into keys natural and surrogate. You'll want to look into naming standards. You'll want to look into indexing best practices (you're creating standards, not an actual design here).

    This will lead you to about... oh... one hundred and fourteen thousand, six hundred and ninety two more questions. 🙂 Come on back as soon as you've read, and re-read, normalization a few dozen times. It takes a few passes for it to sink in as to why you want to do that.


    - Craig Farrell

    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

  • vadon97 (1/31/2011)


    I just came across this blog post, I will start here. Looks like it's on-topic.

    Actually, my guess is that's way off target. That's server architecture, a whole different issue. Usually falls under the DBA (database administrator) tasks.


    - Craig Farrell

    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

  • The position is actually for a Database Administrator, which is what I eventually want to do. Even if I don't get the position, I'd like to learn as much as possible in the process of applying for positions. Do you think the link you provided provides some useful information on the what I mentioned in the first post, regarding one of the tasks?

    I'm a fast learner, and I have SQL 2008 installed on my machine at work. I use SQL all the time, just not to the extent that this new position will require.

  • vadon97 (1/31/2011)


    ... so that I can sound like I'm at least familiar with such practices, if I'm granted an interview?

    Don't exaggerate your skills. Don't tell then you are experienced with database architecture if all you've done is read a bit. It'll take just a few questions from a good interviewer to tell that you're lying.

    If you've read up a bit then by all means tell them that you've read up, don't tell them you have experience.

    The blog is on something completely different, unless you're planning to work at Microsoft with the SQL Server development team. If you're looking for database architecture/database design, this is a good reference (yes it's a book, it's not free. Deal with it.)

    http://www.amazon.com/Server-Relational-Database-Design-Implementation/dp/143020866X/ref=sr_1_1?ie=UTF8&qid=1296511190&sr=8-1

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • We have a series here to help you as well: http://www.sqlservercentral.com/articles/Stairway+Series/70199/

  • GilaMonster (1/31/2011)


    vadon97 (1/31/2011)


    ... so that I can sound like I'm at least familiar with such practices, if I'm granted an interview?

    Don't exaggerate your skills. Don't tell then you are experienced with database architecture if all you've done is read a bit. It'll take just a few questions from a good interviewer to tell that you're lying.

    If you've read up a bit then by all means tell them that you've read up, don't tell them you have experience.

    The blog is on something completely different, unless you're planning to work at Microsoft with the SQL Server development team. If you're looking for database architecture/database design, this is a good reference (yes it's a book, it's not free. Deal with it.)

    http://www.amazon.com/Server-Relational-Database-Design-Implementation/dp/143020866X/ref=sr_1_1?ie=UTF8&qid=1296511190&sr=8-1

    I appreciate your input. However the tone of your message seems to relay that I said I was going to lie. I never said that. Secondly for you to add your comment regarding, "it's not free... deal with it...", wasn't necessary, was it? I never said I had a problem paying for information. I'm currently reading "Beginning SQL Server 2008 Administration" that's part of that same series.

  • vadon97 (1/31/2011)


    I appreciate your input. However the tone of your message seems to relay that I said I was going to lie. I never said that.

    It's implied by the statement I originally bolded, which is why I tried to short circuit the reaction these usually get. We're a bit touchy around here about interviews, we've dealt with folks too many times who've crammed for the interview but forget it all after the weekend. Try not to take it too personally, it's a knee jerk reaction.

    No, the link I offered you was more a generic job description to someone wanting to break into SQL Server in general, and the different levels and job tasks that occur in SQL Server. I believe you will want to read through it, or at least skim it. It's an overview of the different tasks for different SQL positions for new/level I sql professionals. I believe it'll help you tremendously, as that sounds about where you're at for the moment.

    Database Administration and standards for architecture are really two different components of SQL Server. Think brakes and engine on the car, as a simplified example. Sure, you might know a bit about each but you'll tend to specialize in certain areas. It sounds like you're already doing some basic administration duties (the backups/restores) so hopefully it's just more exanding on your existing knowledge.

    As to resources to get you going, once again google is quite helpful. There's a number of basic tutorials and the like out there, once you know what topics to start looking for. You'll see a bullet list under Database Administrator in that article, and I'd suggest you start there, and begin digging into Books Online, using secondary sources as needed if you don't seem to understand a concept the first time through.


    - Craig Farrell

    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

  • vadon97 (1/31/2011)


    I appreciate your input. However ...

    Then you're one in a million, and I mean that literally.

    There's nothing in your initial post to indicate whether it was another person looking for free resources to memorise their way into a position (by far the most common) or otherwise.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply