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...

For more info on all the date and time functions check out the documentation at Microsoft.

Breaking in is very difficult. There are very few junior DBA positions out there that will take you from knowing little and grow you into knowing a lot. The best...

If you observe the wait statistics through sys.dm_os_wait_stats, you'll be able to tell where the waits are occurring. If you see log latch and IO waits, then you're experiencing slower...

It's a pretty manual task because there's almost no way to determine precisely, programmatically, where to put the silly things. So I've always done what the others do. Put them...

Modifying data structures by creating a new table, moving the data, rename the old table, drop all the old constraints, recreating all constraints and indexes, rename the new table, drop...

The optimizer will know that an index is unique and may use that as part of it's decision process when putting together the execution plan.

The command you're looking for in T-SQL is called MERGE. Here's the Books Online entry on it.