Re: attempts to attach db are locking up the server...

From: Rick (rmemmer_at_carolina.rr.com)
Date: 08/17/04 

Date: Tue, 17 Aug 2004 03:47:13 -0700

Hi,

Thanks for your reply. Actually, I had two different
timing out issues. One was happening due to an update
that needed an index in order to update millions of
rows. It would time out and just sit there racking up
memory resources, but after I put the index on the join
field... it worked just fine. The same thing was
happening to the database I was trying to attach, but it
looks as though there was no way this was ever going to
work. It needed to be repaired first, but I had not
found anything that would work (prior to my post).
Anyway, I found this article that you might be interested
in for future reference:

Search "experts exchange Q_21020424" in Google to get
this article... the link won't bring you directly in, so
that's why you need to search on it. I was able to run a
few procedures and then repair the database (which took
about 40 minutes for a very large file), and after that I
was ready to go.

So, I'm all fine now. Of course, I'm still not sure what
to do in order to kill a process that seemingly doesn't
want to be killed. It would be nice to find that out for
future reference, so that the memory doesn't climb to the
point where you have to shut it down.

Thanks for your help!

Rick

>-----Original Message-----
>Hi,
>
>What do you meant by Locking while attach? Are you
getting any errors while
>attaching ? See the SQL server error log for any errors.
>
>Thanks
>Hari
>MCDBA
>
>"Rick" <rmemmer@carolina.rr.com> wrote in message
>news:783701c48423$2fd35f80$a601280a@phx.gbl...
>> Hi,
>>
>> I had a similar post before, and got some good
>> suggestions on this, but so far I'm still unable to
>> retrieve my database. Unfortunately, I made the
mistake
>> of not detaching my database when I was having some
>> problems, and it got physically moved instead. I have
>> tried several different options to get it back, but
they
>> either don't work or end up locking the system.
>>
>> What would cause something to lock up like that? I've
>> tried to kill everything, so I don't see anything going
>> on there.
>>
>> Any ideas on how I could get this db back, and why it
>> might be locking up when I try to attach it?
>>
>> Thanks!
>>
>>
>> Rick
>
>
>.
>

Relevant Pages

  • Re: attempts to attach db are locking up the server...
    ... What do you meant by Locking while attach? ... See the SQL server error log for any errors. ... > of not detaching my database when I was having some ...
    (microsoft.public.sqlserver.connect)
  • attempts to attach db are locking up the server...
    ... retrieve my database. ... of not detaching my database when I was having some ... either don't work or end up locking the system. ... Rick ...
    (microsoft.public.sqlserver.connect)
  • Re: Multiuser Problem
    ... Pessimistic locking - in todays modern languages this is not really the ... requires that you have a database transaction locking the row of the record ... Allow the user to edit the row but before you write the data back to ...
    (microsoft.public.dotnet.languages.vb)
  • RE: 2nd form with recordset of 1st
    ... processes using this table using optimistic locking? ... If this is a split database, is there a persistent connection to the back ... Every directory traversed requires Windows to ... > record source to be the 1st forms recordset? ...
    (microsoft.public.access.formscoding)
  • Re: Can I password a query or table in an Access db?
    ... The other user may edit other ... If you want all other users to stay out of the database while you are using ... The default record locking option will allow you to set the record ... The optimistic locking is the least restrictive and doesn't lock ...
    (microsoft.public.access.security)