Steve Jones - SSC Editor (6/7/2016)

---

If you're mirroring storage at the SAN level, why the AG then? That seems redundant, unless I'm looking at this wrong. The idea with the...

run sp_whoisactive to see how much work it has been doing, if blocking is happening, what it is waiting on (my guess is cxpacket or some form of IO), use...

tomd-982312 (6/7/2016)

---

I am fairly new to T-SQL and have some experience in Oracle PL/SQL.

Here is the case:

I have to read records sequentially from some table in MSSQL database and (on...

Wonderful work and article Alan!

I didn't read all this thread, and I'm not going to start now. 😉 But it is REALLY hard to think of a scenario in which this WHERE clause is...

I called that!! 😀

Glad you have completed the one-time update and can move forward!

Your sample data, while nicely laid out, doesn't help us one bit in writing a query that hits a table and produces the desired output. Please convert your request to...

I'm thinking this sounds like a classic rank/count per-partition scenario, in which case I would think it could be done with a fairly straight-forward windowing function since you are on...

Luis Cazares (6/2/2016)

---

TheSQLGuru (6/2/2016)

---

Luis Cazares (6/2/2016)

---

I prefer to use QUOTENAME which will escape quotes and brackets correctly, as well as handle weird names.

DECLARE

@dbname sysname,

...

And you though my "flawless" word was too...

Luis Cazares (6/2/2016)

---

I prefer to use QUOTENAME which will escape quotes and brackets correctly, as well as handle weird names.

DECLARE

@dbname sysname,

...

Leonard Rutkowski (6/1/2016)

---

There are lots of solutions, but other than the SAN replication, we haven't really found a better solution.

We use log shipping for a couple of databases for...

Sounds like you are well ahead of most entities I have encountered over the years Leonard! Yes, "flawless" was a loose word choice there, at least for any entity of...

Lynn Pettis (6/1/2016)

---

I have also seen the Missing Index DMVs and DTA recommend a nonclustered index that if implemented duplicated the entire table in the index between indexed and included...

Since you are on SQL 2012 I would look into Extended Events to capture stuff affecting this table.