Beatrix has given a good explanation of how to use these files. Here's an attempt at explaining what these files are.

MDF stands for Master Data File, and LDF...

I've extracted AdventureWorksDW2008 from the Microsoft SQL Server Product Samples: Database archive on CodePlex to Google Drive here.

Andrew P.

Can you access the download via this link? I'm unsure if this is behind a paid Visual Studio subscription.

It's interesting to note that those spam posts are not specific to SSC. Here are the Google search queries for a couple of the QQ codes in those spam posts...

To identify the version of SQL Server you are running, try the below statement. Near the end of the output look for "<Developer> Edition (64-bit) on Windows..."

[code...

Database schemas sound like a good solution, these allow you to assign permissions to a group of objects within the database. A downside is the objects need to be created...

In my experience, redeployment shouldn't make subscriptions disappear, the subscriptions should still be there. You redeployed the SSRS reports from version control after the upgrade, what was the reason for...

A couple of things I would check are whether you see any activity in SQL Profiler when ran against the SQL server while the legacy application is attempting to start,...

Here's how I might do this. I suspect the first day of the week could be identified simpler than I have here.
DECLARE @RUNDATE DATETIME = GETDATE()

You need to partition the ROW_NUMBER function by your SUPPLIER_ID. The PARTITION BY statement is the group separator in a windowing function.

Here's your code with ORD modified to...

If I understand correctly, for each Product, you have one or more Document records, but only the latest document should be considered active. I'm assuming you're trying to join these...

When you add a new column to a table with existing records, as you're trying to do here, SQL will use a default value of "NULL" for the column value...

I believe that upgrade path is still active, and your MCSA in SQL 2012 was automatically upgraded to MCSA SQL 2012/2014.

The MCSA: SQL 2016 certification page...

I've restarted the SQL Server service, which resolved the issue.

I'd love to hear any suggestions on what I could have done differently to diagnose why the kill command...