No... you can query the SysObjects table directly although Microsoft recommends against doing that because they may change the table name (I believe they did in 2005).

Make your code refer to a "linked server" and use a 4 part naming convention everywhere in your code.  Then, you can just repoint the linked server at whatever box...

Sometimes, as in your case, you have to ask "Why" someone can't use the answer provided because they haven't explained themselves correctly... I imagine you get that alot

If you don't know how many rows will be deleted, you can do something like this...

    SET ROWCOUNT 5000 
 SELECT 1 --"Primes" the rowcount so the loop works
  WHILE @@ROWCOUNT...

Shoot... I'm a little outside my league on this one... I'll tell you this, though... if you run this from a command prompt...

OSQL -L

... and it doesn't list the server...

Hadn't thought about that... if the DB was NOT properly detached, the procedure for recovery is quite long.  It's do-able, but ya gotta hold your mouth just right while you're...

I've found that "UPDATE x WITH (ROWLOCK)" does very little in containing SQL Server's escalation of locks to rows instead of pages or extents.  It sure doesn't hurt to have...

Yep... knew that about the conversion and SN... like others, I normally avoid float because of it's binary limitations on accuracy.  Because I avoid it, I didn't even think that...

Why?  What's the problem with that method?  The "other user should not come to know"...

Does the MDF or LDF have the "Read Only" attribute set?

Without having to first script the table creation, this would work... very well, very fast, and without any interference...

SELECT *
  INTO newtablename
  FROM oldtablename WITH (NOLOCK)

The only thing it...

Paul,

I haven't seen your connection string and you might want to take the time to post it (without a login name or password, of course!) but, if the name of the...

I think the reason for this may be very simple... try this...

 SELECT *
   FROM MyTable
  WHERE In_Qty  = '<Null>'
     OR Out_Qty = '<Null>'

The literal '<Null>' is not a real...

The first thing is to figure out what is deadlocking what... my recommendation would be to lookup [Deadlocks,troubleshooting] and select [Troubleshooting Deadlocks] in Books Online to start... there, you will...

Very interesting... never had to do such a thing before but how simple can you get?  Thanks, Peter.