was successfully added to your cart.

SQL Databases: From Start to Finish

Go From No Clue to a No Problem SQL DBA

Have you ever tried to use a SQL database only to get really confused? Or maybe you couldn’t even figure out how to install a SQL server in the first place. Whether you are just starting out or are trying to make sure you have a good foundation, this course is for you. You will learn how to:

  • Create a database
  • Create tables, views, and stored procedures
  • View, add, update, and delete data
  • Optimize your tables and lookups
  • Backup and restore databases
  • Script everything – don’t worry, we also use forms to fill in information as well

Expand the lessons to see all of the topics covered.

Take this Course

Join the discussion 9 Comments

  • awethor says:

    Very fine job, Tim. I got a lot out of this course because you covered most important basics in a logical order and with clarity. I was disappointed at the omission of a couple of things, namely functions, indexes, and triggers, which I deem very important (this course, for me, is a review of SQL fundamentals as well as an introduction to SQL Server – I’ve always used Oracle or MySql – I’m not a total beginner, although I’m “rusty”.) Accordingly, I find the description you give of your targeted outcome, which includes “no problem DBA” to be optimistic if not audacious. BUT…I do feel I got my money’s worth, it was a great intro for me to using SQL Server and a good review of some basics, and I thank you!

    • Tim Corey says:

      Thanks for your feedback. I really appreciate it. I had to make a few decisions on this course on what it should cover and what it should leave out. I decided to leave out functions and triggers because they are widely abused. People really love the power they provide but in a production database, they should be used sparingly, if at all. There are usually better options to consider first before going down that path. So, I tried to build solid fundamentals first and the amount of time you spend building triggers and functions should be low enough as to be a very minor portion of your job. This course is designed to cover the 80% you need to know with 20% of the effort needed to become a database developer. As for indexes, I really went back and forth on that one. Indexes are a huge part of SQL. However, they aren’t really a part of a database developer’s job. In fact, a database developer probably should not create any indexes other than the primary key (I’m making the distinction here between database developer and DBA – a developer builds the database, an administrator maintains the database). Indexes are highly personal and based upon actual usage. You can guess at what will be important but it all depends on how your database is used. Applying “logical” indexes (indexes you think just make sense to apply) slows down your database (every index does) but may not give a speed boost on the other end. For example, you might add three or four indexes on a big table but if that table is only queried once a month, the cost of those indexes won’t be paid back in faster querying.

      I appreciate your thoughts.

  • jiudellio says:

    This is a very good job, Tim. Thanks for the effort, the classes are help me a lot. I’d like just to give a tip for other users. For some reason my instance didn’t started automacally after the instalation was finished (maybe this is a SQL Server 2017 issue), so i was unable to connect to SSMS. To fix this i went to run, typed: services.msc and then I looked for the instance I had created during the instalation. Right click on it and press run. The instance will start and with this process i was able to connect using Windows authentication login or SQL server authentication.

  • kenedy says:

    Tim I am a university student in the department of ICT but i always refer to your works more than any of my derpartment teacher.what experience that i get from your ! Thanks keep up.

  • Hey Tim, Cheers for the content. It was really valuable 🙂 Totally worth it.

  • sullisme says:

    Hi Tim, I always use your videos as my first point of reference for things that I am working on. Recently I’ve been working on a database for an app and wanted to include a modification log feature. In this course I believe you used GetDate() as the default value for both the ‘Date Created’ as well as ‘Date Modified’ fields. It appears that GetDate() fires once and then doesn’t fire again…even when fields of a row have been updated. Is there a way to get GetDate() to update upon field modification? As always…thanks for taking your time to make these videos.

    • Tim Corey says:

      There are two main ways to do this. One would be to update that field every time you insert a record. The second would be to create a trigger that updates the DateModified field every time an update happens.

  • oBrun says:

    Hey Tim, this course is nicely done, it’s pretty straight forward!

    Despite this, I’ll tell you what i’d have love to see during this course :

    For me, it needs more homework!
    Especially for the making of a database, like an exercise with the requirements needed, and then your version of this database, to see how a senior sql administrator would have done it!

    Anyway i’d recommend this course to anybody that begins using database. Thanks for you work.

Leave a Reply