Learning T-Sql

[Thor]

What is the best program to use to work with it?

Like what program do I need to execute and write the code?

For instance in HTML I use Adobe Dreamweaver.

Java I use netbeans.

 

[iblade]

Download the free SQL Express: http://www.microsoft.com/en-us/server-cloud/Products/sql-server-editions/sql-server-express.aspx

And then for SQL Server you can use Microsoft Virtual Academy (free) to do the following course : Querying Microsoft SQL Server 2012 Databases - Jump Start
http://www.microsoftvirtualacademy....icrosoft-sql-server-2012-databases-jump-start

 

[Frikkenator]

Download the free SQL Express: http://www.microsoft.com/en-us/server-cloud/Products/sql-server-editions/sql-server-express.aspx

And then for SQL Server you can use Microsoft Virtual Academy (free) to do the following course : Querying Microsoft SQL Server 2012 Databases - Jump Start
http://www.microsoftvirtualacademy....icrosoft-sql-server-2012-databases-jump-start

In addition to Sql Express, download SQL management studio express to edit and run queries (also free), download this one to get the server and management studio: http://msdn.microsoft.com/en-us/evalcenter/dn434042.aspx

 

[Thor]

Thank you so much for helping

 

[Neville]

Why do you want to learn T-SQL?
If it is for front-end development then it is probably not necessary with all the frameworks out there and ORM's available. More and more developers don't need to write T-SQL queries anymore as more and more there is a middle tier of some sort that does that for you.

 

[Thor]

It's for Microsoft MCSE Business Intelligents

 

[Neville]

Then you're on the right track with all the above advice... unfortunately you will still have to learn to write T-SQL. Good luck!

 

[Thor]

Then you're on the right track with all the above advice... unfortunately you will still have to learn to write T-SQL. Good luck!

Thank definitely need it.

 

[Thor]

Thanks*

 

[Neville]

It's not that bad dude. Get a good, basic understanding of database entities and relationships, then writing the SQL queries is just a matter of learning the syntax. SQL is not a very verbose language so not too much to learn, its more about understanding the data that you are querying - that's the trick ;-)

 

[Thor]

Mmm thanks starting with that from next week luckily I have a forum filled with willing knowledge.

 

[scudsucker]

Why do you want to learn T-SQL?
If it is for front-end development then it is probably not necessary with all the frameworks out there and ORM's available.

I think this is bad advice. Best to have a grasp of the whole process, including database design, even if you do not plan to be a DBA.

 

[DominionZA]

Why do you want to learn T-SQL?
If it is for front-end development then it is probably not necessary with all the frameworks out there and ORM's available. More and more developers don't need to write T-SQL queries anymore as more and more there is a middle tier of some sort that does that for you.

Depends on the app.
I am busy with a large app at the moment and for the most part Entity Framework Code First suffices. Then you hit SSRS which is ultimately what the end result of the software is and TSQL is king. In fact, I can't remember an app I have written in the last 20 years that did not require reporting and thus TSQL.

IMO, TSQL is as important as the primary language you are using to price the software together.

 

[Hamster]

Why do you want to learn T-SQL?
If it is for front-end development then it is probably not necessary with all the frameworks out there and ORM's available. More and more developers don't need to write T-SQL queries anymore as more and more there is a middle tier of some sort that does that for you.

It's not that bad dude. Get a good, basic understanding of database entities and relationships, then writing the SQL queries is just a matter of learning the syntax. SQL is not a very verbose language so not too much to learn, its more about understanding the data that you are querying - that's the trick ;-)

Writing queries is more than just understanding your usual one to many relationships and writing queries on them especially when dealing with different kinds of database engines and when speed becomes a real issue. For instance a query that works fast and seemingly optimal in MSSQL might lock up the table and grind the system to a halt on something like DB2.

And ORMs come with their own problems. Right now I am working on a team of relatively senior developers on a system that puts high priority on speed. They are using NHibernate and Dapper and NHibernate is causing more *** than anything else. Dapper with stored procs seems to be faster, less complicated and much more predictable (with the added "complexity" of a developer actually needing to know SQL).

So telling somebody that they don't need to know SQL - terrible advice. As far as possible, if you use a tool that automates stuff for you or wraps it all in a nice piece of "magic" it is still important for the dev to understand what the tool is doing for him (and when a tool is starting to do too much).

 

[shauntir]

I agree with Hamster. You have to learn the ins and outs of your tool and technology and know the trade offs.

TSQL is necessary in high performing applications. ORMs with graph tracking takes a bite out of performance but helps abstract a lot of the mess away.

If you learn how to optimize your queries in TSQL, you will also be a better developer when you use an ORM since you will understand what is happening behind the scenes. Then you can optimize your data access layer.