Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
C0D4633632yFor identifying issues with queries you can use the execution plan.
A good read can be found here
As for how to form your queries, find the shortest path for joining tables and plan your table structure in advance so you can have decent sets vs giant tables that should have been broken up, and only select fields you need rather then entire tables.
thoxx21902yYou should split this in two areas:
- MS SQL Server administration
For the first part, start with a local SQL Server Express installation and get familiar with the docs. Start playing around with creating databases, learn the differences between the backup types, how database space gets expanded, and so on (look at the configuration settings when you create and edit a database with SQL Studio).
Writing good queries is the T-SQL part. I would grab a copy of "T-SQL Fundamentals": https://amazon.com/T-SQL-Fundamenta...
It's worth the money.
First learn how to return correct data.
Then how to return correct data quickly.
Let the engine do the work.
Use the Actual Execution Plan, and Live Query (not in production) to understand how the engine reacts to the script.
JhonDoe31272yOk, not being a rant makes this an anti-rant? 'question' tag seems just plain
Ps: Not trying to be a jerk, just funny, sorry for writing gibberish when everyone else post serious comments
SQL performance explained by Marcus Winand