you should use Cluster Administrator to stop/start all clustered applications !!!

Clustermanager loose connectivity info an try to failover ...  it the stop/start is taking more than a "isalive"-poll-interval.

- How about the connection-pools ? Did they reach the timeouts ?

- Did the users stop and start their applications ? or just tried executing some stuff with the ongoing...

did you restart the services using CLUSTER MANAGER ?

If not, that will be your problem.

And probably INTEGER would be mutch faster   and preferable because you have precision 0.

I was probably updating my previous reply whilst you replied to it

It does not need to be in single user mode, but may...

you can modify the LOGICAL filename.

If you want to alter the physical filename , you're stuck with detatch / rename-file (e.g. with explorer) / attatch

from BOL :

btw precedence has been changed with sql2000 sp4

Let's hope they don't do that again

add this one to "10 things i wish my developers knew about sql"

Make sure you use the datatype of your columns ! because you avoid your dbms to translate it...

you can query inter-collation !

but you have to convert to the same collation in the query :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=4&messageid=95954

can you run sp_updatestats and dbcc updateusage , just to make sure the statistics are OK ?

afaik this is set with the connection !

Connection Pooling in .NET Applications

conn.ConnectionString = "...;Min Pool Size=50";

perfmon can show you the counters.

you may want to...

just my 2ct

- I use this step in a job:

  execute @ReturnCode = msdb.dbo.sp_add_jobstep @job_id = @JobID , @step_id = 9, @cmdexec_success_code = 0, @on_success_action = 1, @on_success_step_id = 0,...

- how many files are in the filegroup ?

- how many columns compose your clustring index key ?

can you provide some config info ?

    SQLServer version and sp

    Server OS and sp

    Memory

If you can reproduce this or know the interval this recurs, start profiler to capture...

just to add to David's reply :

When you are logged in as member of the sysadmin fixed server role, internaly the user is switched to "sa" which defaults to schema...