Re: critical section in tsql
From: Roger Wolter[MSFT] (rwolter_at_online.microsoft.com)
Date: 08/31/04
- Next message: Graeme Malcolm: "Re: referential integrity and INSERT (specially for mr. Malcolm)"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 30 Aug 2004 22:51:37 -0700
Look at Application Locks in BOL.
-- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "Daniel" <softwareengineer98037@yahoo.com> wrote in message news:uF%23XalwjEHA.2692@TK2MSFTNGP12.phx.gbl... >I have two stored proecedures that i wish to have NEVER run at the same >time > to avoid loosing all my data: sp_archive and sp_restore if they called > together at the same exact time there is a possible race condition that > would result in the entire db being whiped out. e.g. archive and restore > both clear their targets at the smae time then try to copy. is there some > good way to do this in sql server I could do it int he c# clients w/ > lock(){} but would feel safer if i could do it in the sql server 2000. > >
- Next message: Graeme Malcolm: "Re: referential integrity and INSERT (specially for mr. Malcolm)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
