Database

Chris Meech wrote:

they want the term batch processing brought back.

Roger Wright wrote:

I would suggest doing this a lot, as it seems to me that it would cause a performance hit

Roger Wright wrote:

Would it help to set the Isolation Level for the transaction to Serializable?

UPDATE table SET status = 'processing' WHERE status = 'pending' AND PrimaryKey = @value;
if row count > 0
   -- Do the processing 
else
   -- Some other client is processing...
end if 

Statements cannot read data that has been modified but not yet committed by other transactions.

No other transactions can modify data that has been read by the current transaction until the current transaction completes.

Other transactions cannot insert new rows with key values that would fall in the range of keys read by any statements in the current transaction until the current transaction completes.

use databasename

Msg 207, Level 16, State 1, Line 1<br />
Invalid column name 'databasename'.

use master

use master

xp_cmdshell

declare 
	@cmdpath nvarchar(60)
	, @Location nvarchar(100)
	, @message nvarchar(max)
set @Location = N'C:\NewFolder'
set @cmdpath = 'MD '+ @Location

create table #result(result nvarchar(255))
insert into #result (result) exec master.dbo.xp_cmdshell @cmdpath
select @message = ISNULL(@message + ' - ','') + result from #result where result is not null
if(@message is not null)
begin
EXEC xp_cmdshell 'RENAME C:\NewFolder RenamedFolder'
end
select @message
drop table #result

select replace(CONVERT(varchar(10),getdate(),111),'/','-') dt

select replace(CONVERT(varchar(10),getdate(),102),'.','-') dt

dt
2009-12-18

select replace(CONVERT(varchar(10),eTime,111),'/','-') eTime  from Table1

select replace(CONVERT(varchar(10),eTime,102),'.','-') eTime  from Table1