Jeffrey Williams 3188 (7/5/2012)

---

GSquared (7/5/2012)

---

Whenever I have to modify data in production, I start with "begin transaction" and end with "rollback", run the script, use OUTPUT to check the results,...

Jeff Moden (7/5/2012)

---

Not all "unused" indexes are actually unused. Some may be UNIQUE indexes or enforce other constraints and the optimizer can make certain optimizations just knowing that there...

Sean Lange (7/5/2012)

---

SQLRNNR (7/5/2012)

---

You can detach and attach. I would not proceed down that path without having a good backup though. I like to proceed cautiously and make...

Brandie Tarvin (7/5/2012)

---

Shhhhh. You're not supposed to...

It is possible that the removal of those indexes caused your slowdown.

Do you have the indexes scripted so you can re-create them just in case?

Here is another script that I...

Thanks Brandie. I even like that you posted the script using dbcc timewarp. Notice the publish date is July 24, 2012.:-D

You can detach and attach. I would not proceed down that path without having a good backup though. I like to proceed cautiously and make sure I have...

Run this code and replace 'YourDBNameHere' with the name of the database you are working with

DECLARE @DBName varchar(128)

SET @DBName = 'YourDBNameHere'

Select a.database_name,a.backup_start_date

,BackupPath = b.physical_device_name

,BackupSizeMB = a.backup_size/1024/1024

,CompressedBackMB = a.compressed_backup_size/1024/1024

From msdb.dbo.backupset...

Both scripts provided should do what you are...

I should have. That would be the better choice imho.:cool:

Steve Cullen (7/5/2012)

---

Correct answers = 1 ???

This must be one of those Monty Python type questions:

Q: What is your name?

A: Steve Cullen

Q: What is your quest?

A: I seek knowledge and...

crookj (7/5/2012)

---

Ray K (7/5/2012)

---

Monday (at least it feels like it -- I hate when holidays fall on Wednesdays!)

(For the benefit of those outside the USA, that was our Fourth of...

I would log in as that user from a different location such as your machine. I suspect the user may have a filter being applied in SSMS.

Congrats