You may also see this if the extension is different. It's one of the many reasons I prefer using scripts for restore anyway. The GUI is limiting and difficult.

sys.dm_db_index_usage_stats is also where I would think to look. Just remember that a reboot will zero out those metrics, so you may see databases that haven't been accessed, but that...

Glad to hear it's helpful. As this technology grows and changes, it all starts to resemble magic.

I think the most interesting takeaway I got from the discussion was that, essentially,...

No, they can adjust the disks, but most of the time the disks are adjusted for the most money saving setting, saving disk space, not speed. However, before you just...

You can't think about LUNs the same way you think about drives. They're not the same. Instead, the focus has to be in IOPS. What are you getting? If it's...

I'd try SELECT @@SPID as well as selecting from sys.dm_exec_requests, sys.dm_exec_connections (I think) to see what's there.

Still sounds a little odd.

I had a great conversation with Alan Hirt about this last night at the New England SQL Server User Group.

The way he put it is that, in the old days,...

I'm finishing up my fourth year at Redgate and I'm on my fourth manager....

Jeff Moden (1/9/2015)

---

Chris Wooding (1/9/2015)

---

As an antidote to Jeff's quick interview technique; the shortest one I ever had was for a contract position. My backside had barely touched the chair...

KenpoDBA (1/9/2015)

---

While Grant is right, you shouldn't use Profiler GUI directly against your servers, I think it depends on what SP 2005 is on. I think it has to...

Trace scripts should work. If you have an error you can post that would be helpful.

But really, the Profiler GUI shouldn't be connected to your servers directly. There are several...

You can see an aggregate of query performance from the queries that are still in cache by looking at sys.dm_exec_query_stats.

But, understand, it doesn't show individual calls. It shows aggregate calls....

Yep. It's a known issue and, according to Microsoft, by design. There are a few things you can use to try do deal with it at the link.

GilaMonster (1/9/2015)

---

It also won't verify that...

It's likely that someone canceled the restore. Drop the existing database and start the restore again.