To generate all of the tables, indexes, FK's, etc, just right click on the database in the Explorer window, click on "Tasks", and then on "Generate Scripts".
This (generating scripts for everything in the database) is , in my humble opinion, one of the worst ways to teach developers about relationships and DRI. It's much easier and effective to make a simple example using two or three such tables along with the "Diagram" functionality in SQL Server. That way, they don't actually need to know much about the tables and can concentrate on learning about DRI, instead.
is pronounced ree-bar and is a Modenism for R
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.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs