Duplicate post. No replies here. Replies to http://www.sqlservercentral.com/Forums/Topic1812925-392-1.aspx

How do total and target server memory behave at the time of the dip in PLE?

You can make the secondary replica async if there's a latency concern. You won't be able to auto-failover, but you can't auto-failover with log shipping either.

Log shipping will work. Any reason you can't add the server to the cluster?

PJ_SQL (8/25/2016)

---

TABLE level scan performed.

- Pages Scanned................................: 1

- Extents Scanned..............................: 1

- Extent Switches..............................: 0

- Avg. Pages per Extent........................: 1.0

- Scan Density [Best Count:Actual Count].......: 100.00% [1:1]

- Logical Scan Fragmentation ..................:...

No. Not going to work.

Why not just use another secondary replica in the other data center. You can even make it an async one if you need.

SELECT OBJECT_NAME(object_id) AS TableName, SUM(rows) AS Rows FROM sys.partitions

WHERE index_id IN (0,1)

AND OBJECTPROPERTY(object_id, 'IsMSShipped') = 0

GROUP BY object_id

No, it shows the...

Start by identifying how many digits of precision you need.

Because, even if we had infinite precision calculations, when displaying the data back to users, we're not going to be displaying...

If the log file is full, then reducing the size of the file should be the last thing that you want to do.

Full means no free space in the file,...

Please don't post the same question in multiple places. No replies here please. Replies to http://www.sqlservercentral.com/Forums/Topic1812729-3077-1.aspx

Please don't post the same question in multiple places. No replies here please. Replies to http://www.sqlservercentral.com/Forums/Topic1812729-3077-1.aspx

Please don't post the same question in multiple places. No replies here please. Replies to http://www.sqlservercentral.com/Forums/Topic1812729-3077-1.aspx

Jeff Moden (8/26/2016)

---

Apologies for the year late response and I hate to be contrary but everywhere I've seen...

You want a try...catch block that either logs errors or returns a sensible message (or the original error message) back to the app. I'd say use THROW as well, but...