Instead of setting Cancellation, how about AppointmentStatus. Then it's a series of things it could be, tentative, open, closed, cancelled.. other stuff. And it doesn't have to be null... but...

Hmmm.... I lean pretty heavily towards that proc being altered. Not arguing with you or your DBA, but that behavior is not something I've run into with sp_recompile. But, one...

Break it down this way, most of the NoSQL solutions are awesome at collecting data, not so good at reporting from it. So, if your main focus is collection, NoSQL...

In terms of straight data collection, many of the NoSQL options are wonderful. HADOOP would be perfect for this in terms of collecting the data. But, when it comes time...

Interesting question.

At first blush, I think I'd probably put the cancellation reason right in the appointment database. The reason being, why put it in a related table? It's always going...

Logs can absolutely become the bottleneck for data modification operations, yes.

Information written to the log is both more complex and simpler than the T-SQL. It's not a straight copy of...

No, truncating the logs is not the way to go. What you need to determine is what amount of data you can afford to lose. This will drive you towards...

In theory, you're more likely going to see use of the first index in most situations and no use on the second, depending. Because they both have the same leading...

Yeah, that's what Microsoft says will happen. Again, I haven't tested this type of load myself (our production systems right now are tiny). I think it's worth a shot on...

You can do things locally with the disks that you just can't do on Azure VMs. So it's not like you get more spindles and controllers by adding more files...

Oops. Log. I missed that. Sorry.

No, there's no more benefit there. But I wouldn't panic until you see log latch waits indicating that you're actually seeing a log write bottleneck....

Jampandu (3/18/2014)

---

It seems snapshot isolation should be on database level not on session scope (unlike other isolation levels).

Going with snapshot isolation require lot of changes in other procedures as I...

You'd have to modify the WHERE clause, the name is right there in the query:

ind.[name] IndexName,

I don't have personal hard tests to validate this, but yes, that's Microsoft's recommendations. However, the document I had for reference has been taken offline by Microsoft. It was here,...

If the user you're referencing in EXECUTE AS doesn't exist in the database, and have the permissions you're anticipating, combined with the user making the call not being a system...