SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Core T-SQL


Core T-SQL

Author
Message
Greg Edwards-268690
Greg Edwards-268690
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1610 Visits: 8496
ChrisM@Work (12/3/2013)
Steve Jones - SSC Editor (12/2/2013)
L' Eomot Inversé (11/24/2013)
I think the idea of "Core TSQL" isn't unreasonable, but no set of knowlege which is just about T-SQL and not about the bigger picture will ever make a competent database developer.


I tend to agree. I was just focusing on T-SQL here. There are other skills, but we can easily get to a large list that's hard to discuss/debate.


I'm also inclined to agree with Tom, however, converting "the bigger picture" into a set of bullet points isn't straightforward. "Know your data", for instance. How you acquire that knowledge, with or without a usable ERD, is driven by numerous factors. Just thinking about it - and I'm in the middle of the process right now, two weeks into a new gig - it seems like a different method every time.


Relationships in the data - they only tell a small part of the story, especially in a data warehouse. Many times there will be a Business Logic layer, and this can be a key part in really 'understanding' the data.
I fall into the same thought pattern as Tom. If it is just the technical skills that they have, it's very possible that they are only a good order taker. The best work is usually the result of good back and forth conversation with the business, especially when a developer can map out some of the what if scenarios.

In light of how quickly the list can grow and vary in different environments, it is hard to focus on just T-SQL.
Desire to learn and master the unknown as it comes up (business changes over time), is something hard to quantify. But I see as important to success, and might be used to cover some of the scope creep.
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)

Group: General Forum Members
Points: 89417 Visits: 41144
@ChrisM,

I noticed that you've not written an article on this subject yet and thought I'd give you a nudge. I think the list you came up with is outstanding and I'd love to see it take to the wing in the form of an article. I think you'd do an awesome job at it.

--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.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
ChrisM@Work
ChrisM@Work
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16864 Visits: 19557
Jeff Moden (3/11/2014)
@ChrisM,

I noticed that you've not written an article on this subject yet and thought I'd give you a nudge. I think the list you came up with is outstanding and I'd love to see it take to the wing in the form of an article. I think you'd do an awesome job at it.


Jeff, I haven't stopped thinking about it since you mentioned it last and I've added a couple of sections since - transactions, ACID and locking and blocking. However, I'm extremely busy both at work and at home and it could be a while before I can tackle it. Here's the thing though - an article of this style is right up your street - Dwain's too, I know you've seen his "Make it Pretty" blog post. If I can't get near it in the next fortnight, it's all yours ol' friend.

“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
Exploring Recursive CTEs by Example Dwain Camps
Greg Edwards-268690
Greg Edwards-268690
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1610 Visits: 8496
I see nothing wrong with a 3 author article.
Or at least send it to a couple of others for comments / feedback at this point.
ChrisM@Work
ChrisM@Work
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16864 Visits: 19557
Neither do I Greg and that’s an excellent point you’ve made.
An article claiming to list the required skill set for a general-purpose TSQL developer, published here on ssc, absolutely has to be first-rate.

“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
Exploring Recursive CTEs by Example Dwain Camps
Greg Edwards-268690
Greg Edwards-268690
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1610 Visits: 8496
Although I will admit - Core skills, and 'Nice to Have - you will need these skills' - will drive a lot of debate at times.

Kind of like building a data warehouse. You may never be done, as technology and user requirements are ever changing.
And if you wait until you can do the whole thing, chances are you will never get to implementation.
I could easily see several articles, not just 1 huge one which could be quite large.

Some of the 'why you should know this' might be important, especially to a newbie.
Gary Varga
Gary Varga
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16825 Visits: 6534
Greg Edwards-268690 (3/12/2014)
...
Some of the 'why you should know this' might be important, especially to a newbie.


Perhaps "under what circumstances you would need to know this" might be a good indicator to many too.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
ChrisM@Work
ChrisM@Work
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16864 Visits: 19557
Greg Edwards-268690 (3/12/2014)
Although I will admit - Core skills, and 'Nice to Have - you will need these skills' - will drive a lot of debate at times.

Kind of like building a data warehouse. You may never be done, as technology and user requirements are ever changing.
And if you wait until you can do the whole thing, chances are you will never get to implementation.
I could easily see several articles, not just 1 huge one which could be quite large.

Some of the 'why you should know this' might be important, especially to a newbie.


The last point you make is roughly how I see it panning out, a paragraph or two per point with good references for those wishing to dig deeper rather than a single humungous article. A digestible article with concise and compelling reasons for each key point. Many developers won't know all of the stuff listed and this format - which encourages cherry-picking - would be more attractive initially and less of a time-thief in the longer term.

“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
Exploring Recursive CTEs by Example Dwain Camps
peter-757102
peter-757102
SSC Eights!
SSC Eights! (865 reputation)SSC Eights! (865 reputation)SSC Eights! (865 reputation)SSC Eights! (865 reputation)SSC Eights! (865 reputation)SSC Eights! (865 reputation)SSC Eights! (865 reputation)SSC Eights! (865 reputation)

Group: General Forum Members
Points: 865 Visits: 2559
Maybe it helps to agree on certain roles first and work out an appropriate list per role?

For example, I would see at least these distinctions as useful in writing about required SQL (and by extension) SQL Server knowledge.


Level: Introduction / getting started

* Understanding the basic relational model
* Basic querying (select, order by, group by, joins and sub queries)


Level: Data manipulation / Limited programming

* Point out some modeling features (how to create proper tables, indexes)
* Views
* Procedures
* Updates / Deletes
* Basic understanding of locking and transactions


Level: Programming / Limited administrating

* Most modelling and referential integrity features
* Triggers
* Schema's
* Security / Linked servers
* Advanced SQL constructs (outer clause, CTEs, functions)
* Bulk imports


Level: Advanced programming, Administrating

* Add remaining full modelling and referential integrity
* CLR Integration
* Data warehouse features
* Other enterprise specific features
* Isolation models
* Clustering

There is quite a bit more no doubt, i do not claim to know it all. By designating levels/roles and what it is good for, people can quickly get an impression on what they need to grasp and might be missing out on. It could be the best that can be achieved as few will ever get to work with everything and know it all.
rlortega
rlortega
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 29
I guess a differentiation must be made in skills required for administration and skills required for development. We have 15 DBA's and twice that many developers. We are DBA's but we do not develop. We tune at the instance and server level but query tuning is done by the developers, with our assistance.

Of course, we have hundreds of databases on many servers.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search