Interesting.Will it not be more efficient to use a proc when compared to a view?

It all depends on the transactions i.e the queries that are run against the database. In simple words number of data modifications and their size in turn.

Could you be more precise with what you want to do/what is required.

Surely enterprise edition.

That works as i required. How do i implement it to within sql query. Say i have table abc with columns t1,t2 both are date fields with format :2003-04-09 00:00:00.000...

One more addition to Antares note( hope its not late to answer this question). Have a scheduled job to shrink tempdb on a daily basis. This should also help in...

if it is a enterprise edition on OS enterprise version you can define the max in the boot.ini file

though we did not have the same problem..we did have scheduler 2 hung messages and queries used to time out at certain times. The root cause is a bug with...

didn't know you could change sys procs !!!!

May be the insatllation is corrupt or some dll might not be properly installed. try to reinstall sql server. Did have this problem couple of times with new pc's.

As said by allen have the query timeout to "wait indifinitely" should make it infinite.

Had seen this error on our servers a while ago. Though stupid we bounced the server and all went fine.

What options did you select while installing? default or any specifics.

Thanks for the information. I have got the script using database roles.

i just need a script that will assign database roles db_datareader and db_writer to the db. I mean the way we do using GUI to add . its time taking...