Make sure all the columns in the joins are indexed and you should be fine.

How long does this query take to run VS how long you think it should take?

Retartd it compared to what???

Depending on the indexing and where conditions, the query can still be very fast.

Can you show it to us?

Ya that's quite a few .

Good point... I used the profiler to find out what sql enterprise manager was generating to disable the job. But using the jobname is certainly much simpler.

exec msdb..sp_update_job @job_id = 0xC0923E436928064EA33B46B2A47BFF61 , @enabled = 0

Can you provide more information on what you need to do.  I for one can't figure out what you need!!

Got the same message today. I guess that while the database restore is running that other regular tasks can't be performed hence the bypass. But I guess this...

What error are you getting?

How much data in the base table before the insert?

How wide is the clustered index?

Store as int or tinyint. Then convert client side when displaying the data.

Other forum or this forum??

I'd suggest you start a new thread for this question so that more persons read it.

Also performance wise, I can assure you that if access can handle it then sql...

Also your first query is fine. The application should be the one doing the work to display the data correctly (especially in pivot queries like this one). There...

I think you can include everyone else on the planet on that one David .

Cool 1 M a year sounds nice !

Maybe not, but I'd sure like to take a look at the job .