Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

What Is the Hardest Feature to Learn About SQL Server? Expand / Collapse
Author
Message
Posted Thursday, July 17, 2014 8:11 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Monday, September 15, 2014 9:16 AM
Points: 6,784, Visits: 1,895
Comments posted to this topic are about the item What Is the Hardest Feature to Learn About SQL Server?

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #1593890
Posted Friday, July 18, 2014 2:39 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 5:59 AM
Points: 299, Visits: 3,362
Off the top of my head, probably recursive CTE.
Recursive processes in POSH, .Net or VBS - say to explore a directory structure - clear as a bell. But for some reason recursive SQL doesn't sit terribly well with me, I can do it, but if asked to pen an example in an interview I'd leave that one 'till last


I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
Post #1593946
Posted Friday, July 18, 2014 6:51 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Friday, September 19, 2014 8:20 AM
Points: 663, Visits: 1,675
I think the hardest thing for me is that I don't spend enough time using SQL Server at my current job. Sometimes I don't touch it for weeks, other times I'm forced to dive in and solve immediate problems. Normally I'm a jack of all trades,(admin, analyst, developer, project manager, trainer), but next week I'm supposed to be ETL master of the universe and design SSIS packages in my spare time. (Any one want to help port VFP .dbf files to SQL Server 2008R2?)

Post #1594023
Posted Friday, July 18, 2014 8:36 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Friday, September 19, 2014 2:13 PM
Points: 1,889, Visits: 2,036
Service Broker is a bit awkward to comprehend at first, even once you get it working. But I think the hardest feature to learn is Analysis Services. It's a completely different language and paradigm to describe the data. I get the basics, you're defining relationships between your fact and dimension tables, metrics, attributes, hierarchies within the data, etc. But there's a lot less visibility inside the workings of it (DMVs and such), MDX and DMX instead of standard SQL, and data mining algorithms that boggle the mind.

While I'm here,
chrisn-585491 (7/18/2014)
next week I'm supposed to be ETL master of the universe and design SSIS packages in my spare time. (Any one want to help port VFP .dbf files to SQL Server 2008R2?)

I'd recommend you use the OLE DB provider for Visual FoxPro
http://www.microsoft.com/en-us/download/details.aspx?id=14839
and in your "OLE DB Source" properties set
AlwaysUseDefaultCodePage=True

I've had better results with that then trying to use the JET or ACE OLE DB providers with DBF files.

Post #1594090
Posted Friday, July 18, 2014 10:03 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: 2 days ago @ 2:04 PM
Points: 3,572, Visits: 8,008
I'd say that the hardest feature to learn, is the one that you don't care about. I can learn many things as a developer, but don't ask me for HA options.
When you have real interest, you'll learn faster and better.



Luis C.
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1594139
Posted Friday, July 18, 2014 10:35 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 9:11 PM
Points: 17,601, Visits: 15,465
For me, the hardest thing seems to be high performing xml queries.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1594151
Posted Friday, July 18, 2014 1:12 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 19, 2014 1:41 PM
Points: 8, Visits: 151
I've heard others say Service Broker as well. I think this is because Microsoft, most bloggers, tutorials, etc try to present way too much SB content without a quick and dirty example. For instance, message types and contracts give noobs problems. But, like foreign key constraints, they aren't even needed. Just avoid them for the first few demos then demo how these things help you avoid errors.

Also, people not familiar with MSMQ or JMS, etc, get hung up on the concept of the "dialog" pattern and don't understand how a sender can do something asynchronously, yet still need to end the convo later. Huh? This is because most people (IMHO) really want to use Service Broker as fire-and-forget. There are safe ways to implement this pattern that are far less confusing for people.



Post #1594210
Posted Monday, July 21, 2014 7:49 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:55 AM
Points: 5,431, Visits: 3,169
andrew gothard (7/18/2014)
Off the top of my head, probably recursive CTE.
Recursive processes in POSH, .Net or VBS - say to explore a directory structure - clear as a bell. But for some reason recursive SQL doesn't sit terribly well with me, I can do it, but if asked to pen an example in an interview I'd leave that one 'till last


+1 on CTEs. Recursion I get. CTEs? Not yet.

I clearly haven't given it enough time as I get it then when I come back to thinking about it it certainly isn't there to any reasonable level of understanding.


Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1594598
Posted Monday, July 21, 2014 8:52 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 1:47 PM
Points: 35,215, Visits: 31,667
andrew gothard (7/18/2014)
Off the top of my head, probably recursive CTE.
Recursive processes in POSH, .Net or VBS - say to explore a directory structure - clear as a bell. But for some reason recursive SQL doesn't sit terribly well with me, I can do it, but if asked to pen an example in an interview I'd leave that one 'till last


Considering that they're a form of RBAR that is frequently (my experience is "usually") worse for performance and resource usage than a WHILE Loop or Firehose Cursor, I'm glad that most people have a difficult time with them. I usually recommend that they be avoided even where recursion is absolutely necessary.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1594633
Posted Monday, July 21, 2014 8:58 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 1:47 PM
Points: 35,215, Visits: 31,667
I think that the hardest thing (a hidden feature, for sure) for people in general to learn about SQL Server is the paradigm shift necessary to produce high performance code. Like it says in my signature line, you have to train yourself to stop thinking in rows and start thinking in columns. Once you've actually made that paradigm shift, then you can easily grasp such "advanced" topics such as the use of the naturally occurring "pseudo-cursors" built into every SELECT, INSERT, UPDATE, and DELETE and index usage, etc.

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1594636
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse