Yep, it's definitely coming soon. I went over the entire roadmap in this video: What's Next?

I can't promise exactly what lesson it's gonna be, but I'm going to follow closely with what I did in the Access Series. I'll go through all the topics, and the stuff that's relevant for SQL Server will go into this course too, including relationships and referential integrity.

Plus, we'll cover the new stuff you can't do in Access, like stored procedures, additional security, and a lot more. I'm working on it now.

Setting up relationships (referential integrity, cascading, etc.) has to be done on SQL Server's end, via the UI or T-SQL statements.  I believe SQL Server Management Studio has a relationship diagram setup similar to the one in Access, but I haven't used that.

Yep. Once the tables live in SQL Server, SQL Server should enforce the relationships, referential integrity, and any cascade rules. Access can still display the linked tables and let you work with them, but it shouldn't be the authority for enforcing those rules anymore.

SQL Server Management Studio does have database diagrams, although I tend to prefer defining relationships with T-SQL once you understand what is happening behind the scenes. Either way, the end result is a foreign key constraint on the SQL Server side.

And yes, I'll be covering this as the SQL Server series continues.

Thanks, I'm excited for more SQL Server classes as I am now looking at ConCat in a query which seems tricky