SQL Question...

[loydb]

Yeah, as I mentioned in my post, if you're in financial, you're pretty much Oracle. I don't hate Oracle, it's just overkill most of the time.

If you know it's a 100% Microsoft workplace, SQL Server can make great sense. Hell, *Access* makes great sense in a lot of those situations

@H2
I spent one week/month in San Jose from 2004 to 2009, but they finally decided a couple of years ago that they were ok with never actually laying eyes on me, so I haven't been back in awhile. I will certainly drop you a PM if I end up back there.

[loydb]

Especialy handy if you work with a framework that doesnt generate the schema for you

While we're talking religion, I recommend the OP generate his own schemas until he finally reaches the point where he says "If I have to generate another schema I'll shoot someone." If you can't do it manually, you are at the mercy of your framework's idea of how shit should go down. At a minimum, you should generate what you think is a good schema, then compare it with the framework output.

Personally, vi and UEdit are the best tools for it IMO

[DIgiDennis]

Especialy handy if you work with a framework that doesnt generate the schema for you

While we're talking religion, I recommend the OP generate his own schemas until he finally reaches the point where he says "If I have to generate another schema I'll shoot someone." If you can't do it manually, you are at the mercy of your framework's idea of how shit should go down. At a minimum, you should generate what you think is a good schema, then compare it with the framework output.

Personally, vi and UEdit are the best tools for it IMO

Yes, i agree 100%. You still have to know the basics to take advantage of the framework, or at least the few i tried.

[H20nly]

stored procedures are inherently evil. Application logic all jumbled up with the data model... evil!

this.

the system i work with is called NextGen. it's basically a GUI for adding triggers and... if needed... stored procedures to do the things that are ultimately beyond the severe limitations of the host applications - two pieces of software with similar goals but way different methods... it's like arrange view vs. session...

agreed about learning the dirt... and getting the hands dirty, but there's a few mud pools, that i'd like to think i'm at least skilled enough to recognize, that i could be beyond. hence the question/thread... and the appreciation for the healthy banter here. i'm lovin it. definitely on point with my hopes.

...and i was dead serious about the drinks. San Jose is close... unless you try to drive that 50 miles during rush hour(s). [/plural]

[loydb]

re: SP
My dislike about SQL Server in particular is that everyone seems to want crazy-complicated T-SQL scripts for stuff that should really be done with a scripting language making DB calls instead. I don't know why this is more prevalent in SQL Server environments than others, but that's my anecdotal take on it.

Any time I invoke an SP from a Perl script, for instance, I write a *huge* documentation block about who wrote the SP and what it does. That's assuming that the business group that actually 'owns' the database will get off their ass and give me perms to see the script, instead of just calling it. Fuck stored procedures.

[H20nly]

sadly, it's more the stored procedures driving my need to learn the language than any other aspect of it. if i could write those... i could write my own check and blow this overpriced bowl of leftover soup called California for cheaper, greener grasses and less populated acreage. i saw a job posting with a description the other day for a position that could basically be my resume. the only thing i saw on it that i couldn't push my way through in an interview was writing stored procedures. the job was in Austin.

[loydb]

I lived in Austin for 45 years -- just moved to Rhode Island this summer. Let me know if you end up heading there, I will be glad to rant about things you must see/do/eat.