I don't understand your question, but the DMV to use is sys.dm_db_index_usage_stats. If you are trying to figure out what indexes might be missing I have a procedure for you....

I am happy to help. I have gotten a lot of good help from this site over the years. I have all maintenance tasks in my environments configured with custom...

If the commands in the exe that must run in the other server can be broken out into T-SQL then you will have a solution. If they cannot then you...

I am willing to bet that the procedure will compile in under one second in all cases. Given that you are creating a temp table, stuffing it, and then joining...

Combine all the steps into one job. If the steps that run stuff on the other server don't always run those steps then have a step in the middle that...

You don't have to use SQLCMD to perform backups on the other servers. You can use linked server, openrowset, or Multi-Server jobs to manage all of your SQL Servers from...

The simple answer is DBCC showfilestats. However, you will likely want this information to be in a more consumable format. I have tables and a procedure to help with that...

What does Object Oriented Programming have to do with DTS, the SQL Agent service, jobs, running multiple jobs, calling other jobs, SSIS, or anything SQL Server related at all for...

Even though A is empty string versus Null the answer is still obvious given that it is multiple choice. In other words it was obvious that the author had just...

It's the double hop issue that always prevents me from using the

Trusted_Connection=yes

However, if the account that runs your SQL Server instance has the ability to register its own SPN...

Another possibility is to use a while statement and delete/insert a smaller amount of records on each iteration so that the optimizer will decide to use a lower level of...

I think it's funny that such a basic posting got so much discussion activity. It's seems like a reasonable enough posting for beginners to me. Anyway, I just have one...

I knew the data would be with the clustered index, but I wasn't sure whether the inner reference or outer reference would win, or whether an error would be thrown....

If you are still seeing this then just refer to the exact index numbers which in your case is likely 1,2, and 3 when you call the sys.dm_db_index_physical_stats DMV.

This is why I just run the following when setting up a new SQL Server instance (2005/08). Then I restart the agent, and run the job at the end:

use msdb

EXEC...