I am a graduate from college in 2000. While I just graduated, I have had a total of 5 years experience in IT working for very large to very small companies.
I find myself in a situation as a DBA that while I can code, I am far from where I feel I should be. I mean this because I seem to find something in my last 2 jobs that I support that pulls time away from me being able to truly spend time figuring out the basics in code that I am far behind. While I can quickly learn ASP, I tend to be programming but not really understanding the basics, I tend to intuitively code using previous code and yet I understand completely what I am doing.
Basically, my responsibilities get greater, the jobs get more complex from company to company and I find myself swimming but trying to keep up with the current because at my latest job, they have crammed 2 programming jobs into one. CRM and a bunch of other stuff. CRM takes a lot of my time which I do code visually, I could be spending more time on ASP.Net, C#, VB, or stuff that I as a young programmer should be working till 3am in the morning doing.
So I find myself in a scattered situation, learning tidbits as quick as possible but not enough time to really think about what I am learning, Ijust apply it on the fly. I suppose this is the senario at most DBA environments but the company I work for is a small one rather than big so my time is just not there to really develop.
Have you experienced this or is this just how it is out there. I feel like I am creating ASP pages, VB pages, JavaScript and while I understand, I feel that I am jumping ahead and have missed studying the very basics in syntax and find myself having to go back to learn a basic rule after I have already coded it.
hard to explain but what do you say to thisEasy situation to get into.
It's bad to get into a situation where you are implementing thyings you don't understand but sometimes unnavoidable.
Get a good laptop, spend some time on long train journeys and visit web sites to learn and ask people who've done it before.
It's amazing what you can get through in a weekend.
There are a lot of systems being written now by people who don't really understand what they're doing (and don't seem to want to) and it shows in the architecture.|||As it is with any programming language it takes time to get a good feel for it and totally understand all the concepts. I have been working with ASP/Sql Server professionally for the last 3 years and I'm still learning new things all the time, but now there are so many new things to learn that I get the same feeling you have all over again. With XML, ASP.NET, C#, web services and all this other new stuff I also get the feel that I'm just barely keeping my head above the water. But I guess that's what it's like in this business... once you start to get the grip of something there is always something else that is newer and better.
I usually comfort myself with all those poor guys working with COBOL and Fortran and all that old stuff. At least I get somewhat close the the new technology...I think thats alot better than to be stuck with the same old crap year in and year out.|||In this current cyberworld LEARNING is never ENDING process and I second whatever Frett proposed it helps when you share your knowledge with other and explore new technologies.|||I can certainly relate. It's a strugle just keeping up with new database and database access technologies. But, in order to make myself more useful to our programmers, I've been trying to learn ASP, Java, VB, etc., and it's nearly impossible to keep up. I seem to get mired in the syntax and lose the architectural perspective I need.
BTW, can anyone recommend a good book that focuses on the architectural aspects of building web applications (ASP and/or J2EE)rather than the syntax and general programming techniques?|||Have you tried UNLEASED series for building web applications.|||No, I have not. I see that ASP.NET Unleashed is pretty highly rated on Amazon, have you read it?|||Yes UNLEASHED is my first preference always to read, since 1995.|||I agree those are high rated, but still its worth each penny you spend.
Showing posts with label experience. Show all posts
Showing posts with label experience. Show all posts
Wednesday, March 7, 2012
Thursday, February 9, 2012
Are Relationships Necessary
My hosting servers have "myLittleAdmin" installed. I am new to ms sql I have some experience with Access but I have never set up Relationships inside the database server. I have always just relied on my application logic to call the relations. What is the benefit to setting up relationships in sql, if any?The closer you can put business rules to the hardware itself, the fewer things can go worng ;) enforcing them. If you rely on applications to enforce your business rules, the first application that forgets to apply a rule, or worse yet mis-applies a rule will cause problems. If the database server enforces your rules, you won't store any data that violates the constraints, which means LOTS fewer hours spent trying to figure out "what created the mess that we're in" and more hours on the beach with a margarita in hand!
-PatP|||i assume that you are referring to foriegn key / primary key relationships.
if this is the case, the hands down winner is referential integrity.
this type of integrity from the trinity( domain entity referential) is in many ways the star of relational databases.
it prohibits the modification of a 'PARENT' key value if there are 'CHILD' values present in the referring column.
It also Restricts the entry of 'CHILD' values in a foriegn key column if an appropriate value does not already exist in the 'PARENT' Table.
check out UNDERSTANDING RELATIONAL DATABASES by fabian pascal.
if you can get through the vendor attacks, it's a good book built on sound concepts. (although pat may disagree. he and fabian dont see eye to neck)
also database design for the mere mortal will help you with the process of becoming normal|||scott, the examples of relational constraints you gave are merely the defaults
don't forget you can also define ones like "if you change the value of a primary key, the database automatically takes care of updating all related foreign keys"
;)
let me take a guess at what CreativeLeaf was asking
in access, there's a menu option, Relationships, which, um, creates relationships between access tables
what happens when you do this is that this relationship information will be used not only to enforce RI but also when you build queries
when you drag and drop tables into the workspace in Query Design View, access automatically generates the JOIN syntax for you!
in other words, you (the person building a query) don't have to know a thing about how the tables could or should be joined, because you (the table designer) have already defined that and it's built into the tables
neat, eh?
oh, and of course it does enforce RI too, including the ON UPDATE CASCADE that i alluded to earlier
(see my article Relational Integrity (http://r937.com/relationalintegrity.html) for other types of RI)
fast forward to the day you want to do the same in sql server
RI is declarative, so you set up your primary and foreign keys properly using CREATEs, and you get the same benefits (i.e. relational integrity, your tables will never be out of sync with each other)
but does this help you when building queries? nup
you still have to know the relationships if you want to write queries against the database
access is such a great database system
i love it!!
:cool:|||scott, the examples of relational constraints you gave are merely the defaults
don't forget you can also define ones like "if you change the value of a primary key, the database automatically takes care of updating all related foreign keys"
We all know access, I use it quite a bit to build the erd and work out issues with queries.
But why should i mention cascading updates or deletes?
his question was [What is the benefit to setting up relationships in SQL, if any? I figure the required protection of the enities is much more important than cascades. So, I wouldnt say the benefit of relations is to cascade their changes. however, in the spirit of fairplay, i am willing to meet you halfway on this, so....I do use cascade , and it doesnt leave spots on my glasses. :eek:
"Thats my story and i'm stickin' to it.." Franz Kafka
-PatP|||i assume that you are referring to foriegn key / primary key relationships.
if this is the case, the hands down winner is referential integrity.
this type of integrity from the trinity( domain entity referential) is in many ways the star of relational databases.
it prohibits the modification of a 'PARENT' key value if there are 'CHILD' values present in the referring column.
It also Restricts the entry of 'CHILD' values in a foriegn key column if an appropriate value does not already exist in the 'PARENT' Table.
check out UNDERSTANDING RELATIONAL DATABASES by fabian pascal.
if you can get through the vendor attacks, it's a good book built on sound concepts. (although pat may disagree. he and fabian dont see eye to neck)
also database design for the mere mortal will help you with the process of becoming normal|||scott, the examples of relational constraints you gave are merely the defaults
don't forget you can also define ones like "if you change the value of a primary key, the database automatically takes care of updating all related foreign keys"
;)
let me take a guess at what CreativeLeaf was asking
in access, there's a menu option, Relationships, which, um, creates relationships between access tables
what happens when you do this is that this relationship information will be used not only to enforce RI but also when you build queries
when you drag and drop tables into the workspace in Query Design View, access automatically generates the JOIN syntax for you!
in other words, you (the person building a query) don't have to know a thing about how the tables could or should be joined, because you (the table designer) have already defined that and it's built into the tables
neat, eh?
oh, and of course it does enforce RI too, including the ON UPDATE CASCADE that i alluded to earlier
(see my article Relational Integrity (http://r937.com/relationalintegrity.html) for other types of RI)
fast forward to the day you want to do the same in sql server
RI is declarative, so you set up your primary and foreign keys properly using CREATEs, and you get the same benefits (i.e. relational integrity, your tables will never be out of sync with each other)
but does this help you when building queries? nup
you still have to know the relationships if you want to write queries against the database
access is such a great database system
i love it!!
:cool:|||scott, the examples of relational constraints you gave are merely the defaults
don't forget you can also define ones like "if you change the value of a primary key, the database automatically takes care of updating all related foreign keys"
We all know access, I use it quite a bit to build the erd and work out issues with queries.
But why should i mention cascading updates or deletes?
his question was [What is the benefit to setting up relationships in SQL, if any? I figure the required protection of the enities is much more important than cascades. So, I wouldnt say the benefit of relations is to cascade their changes. however, in the spirit of fairplay, i am willing to meet you halfway on this, so....I do use cascade , and it doesnt leave spots on my glasses. :eek:
"Thats my story and i'm stickin' to it.." Franz Kafka
Labels:
access,
database,
experience,
inside,
installed,
microsoft,
mylittleadmin,
mysql,
necessary,
oracle,
relationships,
server,
servers,
sql
Subscribe to:
Posts (Atom)