Thanks Ian. You are correct, I needed only full backups. I have included that in my query.

http://support.microsoft.com/kb/271509

http://www.databasejournal.com/features/mssql/article.php/3422471/Monitor-Blocking-in-SQL-Server-2000---Part-1.htm

http://www.sqlservercentral.com/articles/Performance+Tuning/67134/

Any error do you get when you try to connect?

Do you have this problem in query analyzer?

I if understood your problem correctly its limitation in output display only.

You might want to change the default setting in

tools> options>results>maximum characters...

select * from sysperfinfo where counter_name like '%page life expectancy%'

A generalization is that if it is above 300, it is unlikely that you have memory pressure

Edit: use master

if apply David Burrows's suggestion in the Dave's code it would be

select * from #t1 where ','+ValueStr+',' like '%,2,%'

no?

Thanks Grant. I got the point. I was asked how to place files for a new project and I actually did suggest that the safest bet was three different drives...

Grant Fritchey (8/19/2009)

---

Is that two drives in addition to the operating system and server files location? If not, I'd put the OS on drive 1 and everything else on drive...

Of course we are getting professional help in this matter, meanwhile I was trying to gather some information. I could not find much over the internet. Anyways thanx.

Adam,

I have three instances in active / passive cluster setup.

The current version is as follows

...

Thank you all.

@ Adam : Yes the I was refering to sql service when i said active/ passive. Now all instances in one node is patched and the second is...

Mayur,

Don't know whether there is a table for this. However you can get this info using trace. Please see the below blog

Where do you check the version?

Did you upgrade all components? Database Engine, Tools etc

in Query window if you type select @@version, what is the output

Seems you have corruption on your index. id 0 suggests that you might loose some data if you repair. Did you try running checkDb?

Sorry I did not notice that it was 2000

Please check whether the following link helps you

http://www.gerixsoft.com/blog/mssql/recovering-mssql-suspect-mode-emergency-mode-error-1813