Grant Fritchey (2/18/2015)

---

I would not look to replication as a DR or HA solution. It's mainly for data distribution for reporting, stuff like that.

Then, you need to break down HA...

ScottPletcher (2/4/2015)

---

The key thing for performance is the clustered index. Yes, you can instead create gazillions of nonclustered covering indexes, but that actually doesn't help overall performance much, and...

ScottPletcher (2/4/2015)

---

New Born DBA (2/4/2015)

---

FYI--When you run this SQL Statement, there are 207,716 records. 1 more thing I also have to mention is that column C1000020534 has only 1 value...

FYI--When you run this SQL Statement, there are 207,716 records. 1 more thing I also have to mention is that column C1000020534 has only 1 value "Case" and C1000020523 has...

This particular SQL Statement runs around 200,000 times a day, goes through millions of logical reads and when I look at the execution plan, it shows that creating a non-clustered...

Lowell (2/4/2015)

---

to satisfy that specific query, i think an index on the four columns involved int he WHERE clause is needed, and INCLUDE all the columns in the SELECT, right?

CREATE...

MiguelSQL (1/28/2015)

---

Yes, you need to remove TDE from the database, and don't forget to truncate the Tlog.

I had to do something similar. it was a nightmare!

1- make sure it's on...

Try this 🙂

http://blog.sql-assistance.com/index.php/rule-restart-computer-failed-when

Please see the attachment for a little update on the blocking.

GilaMonster (1/7/2015)

---

So on average each update waited 15ms for a lock. Is...

I also ran this script to find waits. Please see the attachment, result from the script.

WITH [Waits] AS

(SELECT

[wait_type],

...

Grant Fritchey (12/10/2014)

---

It depends on how your virtual environment is set up and managed. Many of them use physical storage, not virtual storage. In fact, a pretty hefty percentage are...

Gazareth (12/12/2014)

---

New Born DBA (12/12/2014)

---

Gazareth (12/12/2014)

---

Comparing the backup_size and compressed_backup_size fields in msdb.dbo.backupset table should tell you how much compression, if any, took place.

Which version & edition are you running?...

I got some information about the backup. It did compress some data, but not that much

Backup size = 17250.93

Compressed backup = 17206

No. Same size. Regular backup 16GB, backup after compression 16GB.