g.britton (6/9/2015)

---

Grant Fritchey (6/9/2015)

---

Differences in parameter values or WHERE clause criteria? Use of hard coded values or parameters (either of which is sniffed) vs. local variables (which are not, except...

Steve Jones - SSC Editor (6/9/2015)

---

I tend to agree with Gail here. The data is stored in the mdf/ldf/ndf files. If someone stops the SQL Service, they can restore those...

Differences in parameter values or WHERE clause criteria? Use of hard coded values or parameters (either of which is sniffed) vs. local variables (which are not, except during a recompile)?...

Since the other query is loading a table and you're just running a SELECT statement, the problem could be in the table load. Contention on the disk, resource contention somewhere...

Greg Edwards-268690 (6/9/2015)

---

Grant Fritchey (6/9/2015)

---

One thing you don't mention in the article is whether or not the Columnstore index processed in row or batch mode. Just a guess, but it...

Cool. Thanks.

1. Can you? Yes. Should you? Probably not. sp_updatestats is extremely undisciplined in which statistics it updates. Remember, when stats get updated, not only are you adding the load to...

One thing you don't mention in the article is whether or not the Columnstore index processed in row or batch mode. Just a guess, but it probably was in row...

ericpap (6/8/2015)

---

SQLBill (6/8/2015)

---

Could be someone "doing something they shouldn't". We caught someone on a dev server dropping logins and other things because "they didn't think they were needed anymore"....

In addition to the Stairway, always remember to reference the Books Online.

Steve Jones - SSC Editor (6/8/2015)

---

there isn't a restore that has taken place, so either there's some storage change (possibly a restore of some sort) or a machine level change...

The log is just showing a start up. That's not really terribly helpful.

It sounds like someone restored a database, or possibly the VM as was suggested. The fact that your...

Not seeing your specific issues, it doesn't quite sound like a hardware issue. A series of DBCC commands must be coming from somewhere. That's not something that a failing disk...

To determine connections, and just that, I'd probably use extended events. There's a login event that will tell you that. Now, understand, if people login to one database and then...

Assuming we're talking about an identical database, indexes and statistics and exactly the same parameters being passed so that you can guarantee that you ought to be seeing identical execution...