Do you have indexes to support the frequently run queries? Can the queries use those indexes?

2 million rows isn't that much. SQL can handle that with ease. If you're having...

Sumanta Roy (8/30/2009)

---

As you said that if I have 8 processor and I have 8 tempdb datafiles, then each processor will use one file. I just want to know, do...

What's the reasoning behind the...

Take the query from your first post and just remove the where clause. That will give you the fragmentation levels of all indexes in the entire server, regardless of page...

Edit: Nevermind. Did like Jeff and commented before reading and read protect as in backup up, not protect as in secure.

Smaller indexes tend not to defragment well, there'll often be fragmentation after the rebuild. Also, fragmentation's only an issue when doing large range scans of an index from disk. Small...

Why not?

Is there no way to make the script to work for all databases other...

So it doesn't matter in the slightest which row you get back from the child table?

I must admit, that's a little odd.... Why is it that any one will do?

Yes. The job history window reads from the MSDB database. There's only one place the logs are stored. Hence you'll get the same results from the query as from the...

Define 'first'. There's no order within a table in SQL so there has to be something that determines which row it is that you want. If you can explain that...

espanolanthony (8/30/2009)

---

select b.name, run_date, run_time , message from msdb..sysjobhistory a, msdb..sysjobs b

where a.job_id = b.job_id

and b.name like 'JOB NAME'

order by run_date desc , run_time desc

(no modifications were made to the...

None whatsoever, providing ClientID is the leading column in the index.

http://sqlinthewild.co.za/index.php/2009/01/19/index-columns-selectivity-and-equality-predicates/

Those are the actual logs. MSDB is where SQL Agent writes all job-related logs. If there's nothing in the table, it means that either somone's deleted them or SQL Agent...

PaulB (8/30/2009)

---

If your client insists and having into consideration an Employee table shouldn't have heavy inserting after initial load I would suggest to pack the "insert client" logic into a...

It's not going to be trivial to change that to run over all databases. dm_db_index_physical_stats can easily report on all the indexes on the entire server, but the second part,...