Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec

Thanks Mark, yes...

This gives statement level snapshop...

ALTER DATABASE Concurrency SET READ_COMMITTED_SNAPSHOT ON

and/or

This gives transaction level snapshop...

ALTER DATABASE Concurrency SET ALLOW_SNAPSHOT_ISOLATION ON

The later is the transaction versioning that Oracle offers; the former just gives the last committed value and doesn't block the writer; both can be in force if necessary.

-- 
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials


"Mark Townsend" <markbtownsend_at_comcast.net> wrote in message 
news:43EF9623.3040300_at_comcast.net...


> Tony Rogerson wrote:

>> Just for fun I will comment...

>>

>>

>>>Enough said. Sqlserver will *never* be a scalabale product as all

>>>versions of Windows are non-scalable O/S-es

>>>And when will Sqlserver stop having readers block writers?

>>

>>

>> In the current release you can have all the standard transaction 

>> isolations and that includes writers blocking readers - funnily enough I 

>> did a webcast demonstrating and explaining the feature 2 weeks ago.

>

> Typo perhaps - don't you mean "and that includes writers _not_ blocking 

> readers" (aka read_committed_snapshot ?).