Just in terms of generic storage and retrieval, not talking about any particular query or structure, the best place to put a clustered index is on a monotonically increasing, as...

It's also a good idea to use roles within the database to assign permissions through the role rather than to individual AD groups. This makes it easier to mix and...

Yes

The issue is a combination of bandwidth and data size. There's no "fast" way to delete some of the data from a table. If it can use the primary keys...

With no details on what the job does, the best thing would be to capture the wait statistics before and after the job runs. You can then compare the two...

Not enough to go on. What do the wait statistics look like? What is causing the server to run slow. Is it slower than another server? What are the differences...

It has to be through a hybrid environment, but yes. It's in preview right now[/url].

Isn't the official time 3AM when it changes, but yeah, you'll lose an hour.

I don't know of a sure way to speed that up. We used to do the same thing in this order:

1. Restore production backup to a staging server

2. Clean the...

If you are moving towards a hybrid system with AD inside of Azure, I would pursue that. If all the access is directly from Azure, then you get a choice...

A good practice to get into is setting all the server dates and times to UTC and then working with data offsets from there. You'll get much more consistent behavior...

Performance gains on a clustered index are mostly going to come when that index is used to retrieve the data. While the approach of putting a cluster on the primary...

Ha! Right. Like SQL...

There is absolutely no hard and fast rule "Do this and you'll be fine." Picking and choosing indexes is extremely dependent on the workload in question. Foreign keys are good...

Jeff Moden (3/7/2016)

Heh... I strongly agree... to disagree. 😛 Maybe it's just the bad taste in my...