No need to start over, Sarah. DATETIME2(7) is valid. The 7 is the fractional-second precision, not a Default Value setting, and starting with (7) doesn't by itself prevent changing the column.

In Lesson 7, the ALTER TABLE statement changes the column. Refresh just updates what Object Explorer displays. Check that the query ran against the same database and table you're viewing, and check the Messages tab for success or an error before refreshing CustomerT. If it still shows (7), post the exact command and any error message, without connection details or passwords.

Also, see the Level 1 Addendum before making further changes. I subsequently switched the course examples to classic DATETIME for compatibility with the Access setups we're covering. That doesn't mean DATETIME2 is invalid or that an already-working application needs rebuilding. Back up and test in a copy before changing real data.

Thanks for the swift reply! I was able to refresh the column by closing and reopening SSMS. When I navigated to CustomerT and viewed the Columns, I saw that DateTime2 had updated to DateTimes(3). I'll check out the Addendum as well. As an asie, I have been looking for an SQL course like this and was really glad to see that you have started creating one. If it's as good as your other courses (how could it not be!), I know I'll get a lot out of it. Thanks again!

Glad you got it sorted out, Sarah. Yep, SSMS can occasionally be a little stubborn about refreshing its displayed metadata.

And thanks for the kind words. I'm excited about this SQL Server course too. There's a lot of useful ground to cover, especially for Access developers who want to move their back end to SQL Server without having to become full-time SQL Server DBAs.