???

Probably something like

IF @Parameter=1

SELECT...

but that's guessing without seeing the code.

Um...

How many times do I have to say...

Why do you say it's never truncated? What recovery model, what backups are scheduled?

As I specified it. (MasterID, ID)

ii) Developers should use exactly the same sequence in where...

Rich Mechaber (12/2/2015)

---

GilaMonster (12/1/2015)

---

Awesome Gail, thank you: that is hand's down the best version of the aphorism "never time to do it right, always time to do it twice" I've...

Check the Stairways here (stairways link in the left-hand side menu) and read the stairway to indexes

Which I have answered. Twice.

GilaMonster (11/26/2015)

---

you probably want an index on (MasterID,...

Neither do I, though I fix that any time I notice the mistake. I don't however start statements with terminators.

Let me guess

You created the database, set the recovery model and then started to test?

Until a database has had a full backup, it runs in pseudo-simple recovery because there's nothing...

xsevensinzx (12/2/2015)

---

I'm saying the one statement where not having a properly terminated statement above it could cause the code to error as a bug, could benefit from always ensuring it...

One of the first things you need to do is determine whether adding complexity is necessary. Thousands of transactions a minute isn't that high all things considered

When you want to make the database unavailable after the backup completes.

xsevensinzx (12/2/2015)

---

But, you're really splitting hairs here. You're confusing badly written code with human error. Not correctly terminating a statement can happen to anyone just as it does in all...

Oh, and also...

MERGE must be terminated with a ;

THROW requires that the previous statement be terminated with a ; (although there's no error in most cases if you don't, try...