It's the msdn link in your snippet: https://msdn.microsoft.com/en-GB/library/ff878253.aspx#bkmk_CapacityPlanning

This also seems to be confirmed by Paul Randal here: http://sqlperformance.com/2015/03/sql-indexes/unexpected-fragmentation, in the section on fragmentation from readable secondaries.

He says that the 14...

Interesting...the line in that chart for the combination of Readable Secondary: Yes and Snapshot or RCSI: No in the current documentation at that link actually says

No row versions,...

This seems to be the same question as you asked here: http://www.sqlservercentral.com/Forums/Topic1692950-2799-1.aspx.

It's easier for us to help if all the contributions are on one thread instead of scattered across multiple...

What have you tried so far, exactly, and what are the errors you're encountering?

If your backup chain is just one full and one tlog, you would just be restoring...

As Alan pointed out, we'd be best able to help you if you posted DDL for the tables involved, sample data in the form of INSERTs, and desired results from...

As I mentioned on your other new thread, let's try to keep this on a single thread. It's much easier to get good help that way.

Original thread: http://www.sqlservercentral.com/Forums/Topic1693390-391-1.aspx

I understand that you would really like some help, but please try not to start multiple threads for the same request.

It's much easier for us to help you if all...

Lynn Pettis (6/10/2015)

---

Jacob Wilkins (6/10/2015)

---

It just has the QUOTENAME and ISNULL mixed up for the database name. Flip them and it will work. As is it's trying to pass DB_NAME()...

It just has the QUOTENAME and ISNULL mixed up for the database name. Flip them and it will work. As is it's trying to pass DB_NAME() as the quote character...

Scott's fix will work quite nicely.

I was already typing up a solution like Scott's, and when I saw his had posted, I didn't want the typing to go to waste,...

Enclose the IP with parentheses instead of single-quotes.

Cheers!

You could use a CTE to do that. Something like this:

WITH VeryLongCode AS 

(SELECT ID=132,Brand=115,Year=2012,Paid=10245.12,State='Yes'

UNION ALL

SELECT ID=132,Brand=115,Year=2011,Paid=8512.76,State='Yes'

UNION ALL

SELECT ID=112,Brand=113,Year=2012,Paid=1245.12,State='Yes'

UNION ALL

SELECT ID=133,Brand=115,Year=2012,Paid=2245.12,State='Yes'

UNION ALL

SELECT ID=142,Brand=115,Year=2011,Paid=8112.76,State='Yes'

UNION ALL

SELECT ID=142,Brand=113,Year=2012,Paid=11245.12,State='Yes'

)

SELECT VeryLongCode.BRAND, VeryLongCode.STATE, VeryLongCode.YEAR, VeryLongCode.ID, VeryLongCode.PAID

FROM VeryLongCode

WHERE...

A good point! There are actually a couple such points...

Ah, indeed. I told myself to double-check to make sure both were the same, and apparently failed. I picked the wrong day to stop drinking coffee :crazy:

Have you tried declaring...

It's not so much the UNION that's the problem as the second WITH. I don't think you need to specify the namespaces for each query, so just omit that for...