I found the abandonment of the Dynamic Properties task; which I used extensively as it was used to set the name of files to be downloaded, to set the date...

Well, it appears that this is a fundamental problem with SQL Server 2000 because the deadlock monitor thread cannot distinguish between the caller (my "DeadLockFree" sp) and the called sp...

[Please accept my apologies for being blunt.]

Reading through this again, it seems like you have major problems with the way you're using your database. I can only think of one scenario...

I'm trying to get a sp solution because all my production jobs run as sp's and I'm looking to replace:

exec my_sp

with:

exec DeadLockSafe 'my_sp'

which is a minimally intrusive wrapper that can...

"go" is not part of T-SQL. It is an instruction to command line tools (such as QA or osql) indicating "this batch is complete, go execute it."

However, you should code...

Well, that might help getting ADO to pick the right result set. I'll try it.

p.s. when I first posted this vbs snippet I forgot to include the "rset.movenext" call. I know that this needs to be there, that's not the problem.

Failover involves two processes: shutting down one server and starting another. Shutdown can be fast (especially if unplanned!). Starting the new instance depends on how many databases you have and...

It depends on whether you want both servers to be live or whether you can deal with one being a "hot spare" -- like a distributed MSCS cluster. For the...

MSCS does nothing to database tables. I have no idea why clustering should do that, unless you mean something other than what I do when you say "clustering". Maybe if...

That's not a fair test of failing over the SQL Server, since you're using windows explorer and the lanman server process, which have lookup latencies. You should use a simple...

I have several Dell clusters. There is an official "Dell Cluster Kit", which is a manual and a crossover ethernet cable for the heartbeat. It costs $195 so is very...

p.s. The disk needs to be in the same group as the SQL server, though. That ensures it moves from node-to-node with the server.

Hi. It's a mistake to make a database disk dependent on the sql server resource, for the following reasons:

1, the disk will always be brought on line AFTER the SQL...

I just did this very thing. The install does have to be on the "hot" node, but it doesn't matter whether that was the "original" node. For the cluster install...