| |
| |
| |
|
Page: 1 2 3 4 5 6 7
Comments:
<0> brb
<1> k
<1> anyone else willing to help ?
<2> dude Database design is as much of an art as it is a science
<2> there's probably a dozen schools of design
<2> is it setup correctly? who the **** knows, that depends on your requirements and how you intend to use
<1> well yes , my requirements i want to tell you, and you can look the pic and tell me if it can be done ?
<2> if you want me to go over it my bill rate is $175/hr, this would take atleast 5 hours to really dig into it
<1> ...
<1> you know what i read ?
<2> if you have specific questions people can answer them here, but just asking "is my database designed right" and showing a diagram... well how do you expect experts in the room to do that for free when thats what we get paid to do
<2> and paid very well might I add
<1> i am not asking you to do anything... just to confirm if it's right for waht i want to do or not...
<2> which takes a significant amount of time to figure out, you want someone to arch your data structure for you, well I can do that for that for a rate, and you'll be hard pressed to find anyone in here to say anything different
<2> I have enough systems to arch that I get paid to do, why the **** would I want to do one for free?
<1> ok man if you don't want to help don't... i don't understand why you are intervening here all of sudden out of nowhere if you dont' want to help...
<2> because I'm saying what everyone else in this room who has any clue is thinking but doesn't even want to waste their time to tell you
<2> you're not going to get an answer on this question unless you pay someone
<2> because it's not a question, from the sounds of it you want us to do your job
<1> you are so sad man ...
<1> that IT people don't want to help, simply because their field is in reality so easy, so they don't want people to learn ... because they would become useless....
<1> ( i read that... )
<2> no, because to answer your question I'd have to do your job, I'd have to review the requirments of your project, analysise your data structure and see if I can find any ways to do it better or anything that doesn't meet the requriments
<3> if you're not familiar with any relational db design, i'd suggest you to get a book and learn first
<3> adyss3us: that is basically tuning where there are plenty of books about it
<1> it's a 6 table db... it's nothing big that you have to "analyze"...
<2> if you can't do that, then you shouldn't be designing relational databases, now if you want help on it, someone to walk you through it, etc, you'll have to pay, whether its a professor in college or a data arch, well take your pick
<2> without knowing indepth what your biz reqs are its impossible for me to determine wether or not that design is "correct"
<2> and I'm not doing that for free
<2> Japi: I don't really think a book or article can teach him the answer to the question he's asking, database design is too implementation specific for something like that, you have to know wtf you're doing
<1> Good For You
<2> SQL Server in 21 days won't help
<1> Odyss3us, you fool, i am an nuclear engineer,.. stop thinking you are genius, if i was thinking like you would be left without eletricity to run your geeky computer and without isotopes to take xrays of your broken face
<3> odyss3us: There are books that tell about designing relational databases, but i know that every db is specific and there are no books that will give a good answer, but they will teach the basics
<3> zoroxsta: So you are an nuclear engineer, i'm not coming to ask you to check my plant if i'd had any, you couldn't give me an straight answer without working on the sketches or anything for hours. i don't think you'd do that for free
<2> I'm not going to go to try and build a nuclear reactor without consulting a nuclear engineer, so why the **** are you trying to build a database without consulting a database archetict?
<1> what the hell... if you ask me a question here i will answer you , i am not going to say "oh am a nuclear engineer, my rate is this and that"
<2> ok how do I design a nuclear reactor?
<3> i wasn't asking that
<2> you're going to sit down and walk through a nuclear reactor design with me for free?
<1> first of all one single person can't walk you through a nuclear reactor design due to its complexity
<2> look, Database Design is very important to get right, it is the base of your application, if your database is designed poorly your project is basically doomed for failure, to design a database correctly you really need to have years of experience to know whats good practice and whats not as constrained by the requirments
<2> you just can't look at a diagram and tell if its right, because even something thats technically right on paper, might be the completly wrong solution for your project
<2> if you're an engineer you know there are many ways to skin a cat, and some are better than others
<3> my lecturer at school told me at a db cl*** that no db design is correct, some are good
<1> exactly, i did it my way, and i am wondering if it's the good way
<3> test it
<3> that's the best way to figure out if it is good enough for your needs
<2> there's no way to really answer that question without knowing everything you want to do with it now, and everything you could think you might want to do with down the road, and plan the design as best as possible around those requirments
<2> and I guaruntee theres no way you could tell me all of that, and have me understand it and think through the implications of those requirments in under 5 hours
<1> ok wahtever man
<0> odyssey
<0> you get 175 an hour currently?
<0> Zoroxsta
<0> your design is bad
<1> that's BS, odyssey can't get $175hr
<1> why ?
<0> employee can have more than 1 position?
<1> http://www.accessforums.net/ftopic73147.html
<1> yea of course
<0> what's sub2 sub3 program?
<1> sub categories
<1> it's like folders on a computer...
<0> ok
<0> so you gonna create a table each time?
<1> no it just stops at level 3 does not go deeper really
<0> so it cant go deepr?
<1> nope
<0> why two employee tables
<1> because there are owners of directories, and responsible of documents in those directories, an owner ***igns a responsible to a doc...
<1> so he tells you , review this doc, audit it... and blah blha...
<0> ok
<1> but a doc could have no resp, and a path coud have no owner ...
<0> EmpIDOwner shud go into employee table
<0> if no ownder then NULL
<0> i dont understand why 2 employee tables
<0> never repeat data
<1> why it should go in employee table ?
<1> because there are employees
<1> employees can be
<1> or owners or responsible
<1> you are owner of a "directory"
<1> you are responsible of a doucment
<0> i thought
<0> it meant
<0> employee could be above another employee
<0> then i dunno wtf EmpOwner table is
<1> well the owner is like a manager, you are a manager of a set of doucment, (folder)
<0> so tell me what that stupid table does
<0> i dont get it
<1> so the owner, manager ***igns doc to respbonsibles
<1> which stupid table ?
<0> EmpOwner
<1> ok empowner is the table containig managers
<1> now the table "responsible" is another table ... because there can be owners at different levels, company wide, site wide....
<0> something is wrong
<4> heh
<0> either empowner is missing something
<0> or yo umust move ownerID to Emp
<1> i don't think you get the logic behind it ...
<0> DUDE
<0> THE TABLE EMPOWNER IS RETARDED AT THIS POINT
<1> you can be an owner at the site leve, the company wide level... and so on
<0> DO YOU GET IT?
<1> hence joingning the owners and the level !
<1> man, i think i can do your job, without having to take even courses !
<0> it's not joining owners at the level
<1> a same employee can be an owner at the site leve, company wide level...
<0> but that table only has two fields you****
<0> it needs to have a levelID in it
<0> otherwise it makes no sense
<0> why can't your pea brain understand
<1> it has a field called tlevel, which contains" Company Wide, Site Wide, Ord, Project
<1> why would you need more fields ??
<0> i dont see it on your cumclotted diagram
<0> EmpOwner only has two fields on that diagram
<1> well you may want to buy a better pair of gl*** my friend, it's written tfield, black on white !
<4> quant, you're really abusing the adjectives today
<0> EmpID and EmpOwnerID
<0> df: sup man
<0> i dont even know this guys business logic and i alreayd know his DB is wrong
<4> i knew it two days ago
<0> he came in here b4?
<4> either the workflow is completely screwed, or the translation to the db logic is flawed
<4> or both
<0> tell him it doesn't make any sense
<0> most of the diagram
<4> i have man
<0> when was that?
<4> i was unable to help
<4> couple days ago
<0> ic
<1> EmpID links it to the master talbe of all the employees... not all of them are resp of docs or owners...
<0> [03:34] <1> man, i think i can do your job, without having to take even courses !
<0> zoro try populate with sample data
<0> maybe then you'll understand
<4> is he talking about the 'job' you have giving head in the men's restroom at the bus station?
<0> hehe
<0> that's my old job
<4> oh
<1> well I did populate with data
<1> you are the one not understanding logic man ... i know cmos logic mate...
<4> Zoroxsta`, the problem is that you are not being successfully getting anyone else to understand the logic
<4> not that anyone else is failing
<1> what's so hard to understand, there is no logic ???
<4> i've seen you explain this in depth to at least four not terribly stupid people
<4> clearly there's a workflow
<4> but no one else seems to 'get' exactly how it all works
<4> your descriptions aren't helping, imo
<0> not only that
<0> without knowing how it works
Return to
#sql
or
Go to some related
logs:
#solaris
#italy
#3dsmax
San Jose Google Shuttle
#sendmail
#computers
leafs caht
#beginner
#politics
#windows
|
|