Make sure you pre-allocate enough log space to handle any logging required.  If the log file has to grow dynamically, that will be very slow.

Make sure the new data files...

Maybe a permissions issue?  I don't see why drives wouldn't show up for that query.

That code is extremely inefficient though, since it pulls drive info once for every file, instead...

Ultimately any part of a disk drive file can be corrupted (or attacked?).  A bad controller, etc., can cause unexpected corruption.

Again, it's my understanding that there is no way to...

It's very difficult for many people to split the logical and physical design.  But, it's critical to a good design that you keep the two separate.  Getting a developer involved...

As I understand it, if you lose the certificate, you can't read the data, period.  Back up that certificate and make sure you can restore it!

IIRC, from the one time long ago I looked at SQL Diagrams, it is only a physical design, there is no separation of logical and physical.  If you don't distinguish...

I would think you could summarize the data just once, for all BSP ranges and WIN/LOSS combos, then join to that, if needed, to get the final result.  I can...

You simply do your best. If you are not...

The referencing_id would always be the current db, I would think.

You should check the referenced_server_name as well as the db name.  It's possible that local db1 could point to the...

It's the insert and update that are locking the table.

You can ignore these locks by using the nolock hint:

select count(*) 
  from mytable with...

Yes, that is common but horrible, but at least it would not affect the logical design, which could still be forward engineered to proper physical form.  Just keeping accurate logical...

Sure, you could do a design with only pencil and paper, just as you can eventually get across town by walking.  But for anything but the most trivial design, you...

I suspect you many not need individual dates in the result at all.  I also adjusted the range to 7 days rather than 8, as a week seems like a...

SQL's Query Cost Governor is all that I'm aware of toward that end.  This is a before-execution, based-on-estimates governor, so it's not 100% accurate.  But hopefully it would prevent anything...

The single most important thing to understand, though, is that data modeling is a logical process, not a physical one.

Physical things -- identities, files, etc. -- do not exist in...