Look in the SQL Server error log, there may be additional info there.

Just in case, add another file(s) to tempdb if you can, to give it additional space.  You never...

One thing to look out for is UPDATEs that significantly expand the size of varchar columns because that can cause page splits which can be a real performance issue, both...

I do the same thing with transaction log backups... if the "log_reuse_wait_desc" in the sys.databases view contains "NOTHING" for a database, then nothing in the database has changed and...

In addition to Jonathan's excellent advice, be sure to also pre-allocate enough log space to handle the full INSERT, especially if the log growth is a small amount.  Log space...

It's terribly scary to me that this is a "class".  They're teaching people exactly the wrong things to do.

In my head, I envisioned having the database set up in such...

8<

>8

An is_active flag (someone can be inactive and still not "terminated", e.g. "suspended"), specifically, makes perfect sense to me because the specific inactive date / conditions...

8<

>8

An is_active flag (someone can be inactive and still not "terminated", e.g. "suspended"), specifically, makes perfect sense to me because the specific inactive date / conditions may be...

>>But you display only vague dates not associated with any year. I'm going to make a suggestion that you use the MySQL convention four months. It is based...

No and no, to answer your two questions.  I saw how the OP was basically ignoring design suggestions and came to the same conclusion as Scott's last statement and...

You wouldn't want to detach the db just to move a file.  Just ALTER the file location in SQL Server, take the db offline, copy the file, then bring the...

I believe you...

Nothing to do with data modeling, only development.  Data modeling must precede coding.

Just don't offer terrible modeling advice and I won't have to point it out.

The big tasks are the SSIS packages and SSRS reports.  Often they require quite a bit of rework.  I'd start checking those out as soon as you can.

The other stuff...

The current (pseudo)design is horrifically bad.  You have non-dependent columns in tables, repeating columns (address1, address2 / phone1, phone2), update/delete anomalies all over the place, and so on.

Stop rushing to...

Make sure the [Reference_Table_Obsolete_Date] is getting populated correctly on all obsoleted rows.

If that date is NULL for both rows (old and new), that will not be allowed for a unique...