February 22, 2011 at 10:37 am
Lynn Pettis (2/21/2011)
MaricopaJoe (2/21/2011)
I agree the questions are more basic. But this is due to the business side thinking that 'anyone' that has computer can be a dba.Case in point. I have friend who has co-worker dba that uses nothing but google to learn how to do his job.
Blame the IT software industry for making everything so 'user friendly'. If we where all on command line syntax then there where be less basic questions.
Dumbing of IT using the graphical interface.
I tend to use the GUI to do quite a bit of my job, makes it easier. The difference comes down to also knowing how to do what the GUI is doing. Most people that rely on the GUI to do everything may not understand what is actually happening behind the scenes. If a problem occurs, how are they going to be able to figure out what is wrong, and what needs to be done to correct the problem.
That is what makes the difference between a Junior DBA and Senior DBA in my opinion.
I can agree with you so far (although I don't think it's necessary to know all the gory low level details of everything - there are some things that can be looked up when you need them).
Yes, I agree that the development of GUI interfaces can lead to the dumbing down of IT professionals, if we don't take the extra effort to learn what is going on under the covers.
The people who are dumbed down by it are not professionals, it's an abuse of the work "professional" to call them that. Everyone who thinks he's a DBA (whether the A is for Administrator or Architect) or a DB developer needs to have a clear picture of what's going on under the covers and know where to get the details if ever they need them. (They don't need all the gory details until they have to do something that requires them, but they absolutely must have a clear picture of how the GUI achieves its task and where to find the details when they do need them.)
So is the industry dumbing down professionals by providing GUIs? No, it's providing the opportunity for people without the mindset to be a professional DBA to undertake a lot or the grunt work and free up the real professonals to do other things (including taking over when the GUI fails to do what it should, or doesn't cover what is needed).
Tom
February 22, 2011 at 11:09 am
Well said Tom. (as always)
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
February 22, 2011 at 11:13 am
SQLkiwi (2/22/2011)
Brandie Tarvin (2/22/2011)
Paul, are you out there? Are you all right? I vaguely remember that you said you were from ChristChurch, NZ, is that correct? My condolences for anyone reading this thread who has family or friends in ChristChuch. I hope they are all well after the earthquake.Fine, thank you, but I live 50km north of Wellington, on the North Island, so I am 350km away. A very sad day.
Paul, if you have recommendations of organizations that are doing a good job supporting the recovery from your perspective, please let us know so we can lend support where it is doing the most good.
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
February 22, 2011 at 11:39 am
Jeff Moden (2/21/2011)
...I dun no... DE-troit boy goin ta ohia mur dan wonce in da sames yer mite git da kin folk resluss en tha lak.
Here's my ESL approach:
Detroit boy going to Ohio more than once in the same year might get the kind folk restless on the lake.
As a side note: I didn't have to slow dow even a tiny bit to read it - since I have to look up each and every written word anyway 😀
February 22, 2011 at 11:51 am
Tom.Thomson (2/22/2011)
So is the industry dumbing down professionals by providing GUIs? No, it's providing the opportunity for people without the mindset to be a professional DBA to undertake a lot or the grunt work and free up the real professonals to do other things (including taking over when the GUI fails to do what it should, or doesn't cover what is needed).
I like your positive attitude, Tom. It is the way the world works anyhow. I know how to fill up my tank in the car, or how to swap a brake light, but when it comes to reconditioning an engine, I leave it to the pros. Problem of course is that in our field some people do think they are the pros, and then the customer ends up with a stuffed engine instead of a blown bulb :w00t:
February 22, 2011 at 12:02 pm
On a similar debating note, does anyone know of code in SQL Server that's worth protecting with CLR, obfuscation, or any hassles of encrypting? Not data, but code?
February 22, 2011 at 12:27 pm
Steve Jones - SSC Editor (2/22/2011)
On a similar debating note, does anyone know of code in SQL Server that's worth protecting with CLR, obfuscation, or any hassles of encrypting? Not data, but code?
In my limited experience, the only time I have seen attempts at obfuscation have been to hide the poor quality of the code. Seriously.
February 22, 2011 at 12:35 pm
Steve Jones - SSC Editor (2/22/2011)
On a similar debating note, does anyone know of code in SQL Server that's worth protecting with CLR, obfuscation, or any hassles of encrypting? Not data, but code?
Once, but it's not for commercial software. It was part of a DoD app. (EDIT: I forgot to mention I wasn't on the project, I merely had a buddy tap me on the shoulder for ideas on going about it.)
The other side of things are when you're a very small company and you can't afford the lawsuits to deal with code theft/resale/international code go bye-bye. Had that happen to me as a startup in an Access database. You'll find an inventory system still making the rounds on occassion via pirate sites for small businesses.
My biggest problem was I deployed to multiple customers and was still new, so I didn't force a canary trap into the code in different places. Since I couldn't nail down which specific one was the culprit, I ended up getting tossed into legal limbo.
Good or bad code, it helped to destroy my business, as well as my opinion of humanity in general. It wasn't the only cause of that business failing, I made any number of mistakes as well, but it was the final straw. There are good reasons to want to protect your work, and there are times I actually feel bad for the RIAA, even if they are monolothic enough to not need to care as much.
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
February 22, 2011 at 1:03 pm
Steve Jones - SSC Editor (2/22/2011)
On a similar debating note, does anyone know of code in SQL Server that's worth protecting with CLR, obfuscation, or any hassles of encrypting? Not data, but code?
I have not. My opinion is that if you need to protect the code, and if it is really proprietary, it belongs in the business layer, not the database.
Seeing Craig's answer means I don't consider Access as database, at least not purely.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 22, 2011 at 1:06 pm
Jack Corbett (2/22/2011)
...I have not. My opinion is that if you need to protect the code, and if it is really proprietary, it belongs in the business layer, not the database.
...
Do you see a chance to protect code in the business layer? What programming language would that require? (AFAIK it's rather easy to reverse-engineer any .NET app ...)
February 22, 2011 at 1:07 pm
Steve Jones - SSC Editor (2/22/2011)
On a similar debating note, does anyone know of code in SQL Server that's worth protecting with CLR, obfuscation, or any hassles of encrypting? Not data, but code?
Any code that represents an investment of capital and which potentially gives the company a competitive edge is worth protecting. Not sure what you mean by "protecting with CLR", unless you mean "hiding it in a DLL and hoping nobody gets the dev files". If it's worth protecting, it's worth actually protecting, which means source control with security.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 22, 2011 at 1:13 pm
Steve Jones - SSC Editor (2/22/2011)
On a similar debating note, does anyone know of code in SQL Server that's worth protecting with CLR, obfuscation, or any hassles of encrypting? Not data, but code?
I've only ever seen one case of that. As I mentioned over on the 'thiefs' thread
"A logistics company had implemented their entire supply chain/warehouse location optimisation code in SQL. It was some of the most complex SQL code I have ever seen, and it was the product of years of research and investigation. The code alone would have been worthless, the code combined with the weightings in the tables was their entire business."
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
February 22, 2011 at 1:16 pm
GSquared (2/22/2011)
Not sure what you mean by "protecting with CLR", unless you mean "hiding it in a DLL and hoping nobody gets the dev files".
Protecting as in 'preventing clients who have bought the software from being able to reverse engineer and steal the code'
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
February 22, 2011 at 1:50 pm
Jack Corbett (2/22/2011)
Steve Jones - SSC Editor (2/22/2011)
On a similar debating note, does anyone know of code in SQL Server that's worth protecting with CLR, obfuscation, or any hassles of encrypting? Not data, but code?I have not. My opinion is that if you need to protect the code, and if it is really proprietary, it belongs in the business layer, not the database.
Seeing Craig's answer means I don't consider Access as database, at least not purely.
Not purely, no, though it can be used that way. Part of the problem with Access is it allows the business layer and user interface to all be developed within Access. If you just use Access as a database and develop the front end and business layer in C#, VB.Net, ASP then it can act as just a database.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
February 22, 2011 at 2:38 pm
GilaMonster (2/22/2011)
GSquared (2/22/2011)
Not sure what you mean by "protecting with CLR", unless you mean "hiding it in a DLL and hoping nobody gets the dev files".Protecting as in 'preventing clients who have bought the software from being able to reverse engineer and steal the code'
Which is pointless if they get a reverse-compiler. They'll likely end up with junky looking code, but it'll show the process, if not the optimizations.
What I was asking was: Did Steve mean the question to be about legitimately protecting code, or did he mean to ask about people actually using completely ineffective means of protecting things? Two very different takes on the same question.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 15 posts - 24,241 through 24,255 (of 66,738 total)
You must be logged in to reply to this topic. Login to reply