Snapshot isolation is a SQL Server 2005+ feature. So you are out of luck on a SQL Server 2000.

Regards,
Anders

SELECT name, is_read_committed_snapshot_on FROM sys.databases

What are you trying to achieve? My ‘patch’ is just a registry key that adds the Danish wordbreaker only – for the default instance (You need to restart SQL Server for the change to take effect).
Which wordbreaker do you need?

Homemade frameworks are often highly specialized for the organizations who build the framework – therefore they have merit.

An organization should not undertake the task of building generalized frameworks like unit testing and O/RM frameworks – only after carefully considering the business value, which in most cases will not justify the cost.

You are right. In Read committed snapshot isolation one writer will block another writer. With snapshot isolation none will block, but the later write transaction will fail if the underlying data has changed ~ automatic optimistic concurrency control.

Thanks. I have amended the article.

Lucene er fedt. I vil ikke fortryde det

Glad that I can help. Believe me – I’ve struggled with these settings too

Thanks for the info on this. It’s quite important to know the default values of these settings. You saved me quite some time.

I’m enthusiastic about freetext search and especially Lucene. Feel free to write to me if you want to know more…

Unfortunately I was misinformed about the session length – I had more content that showed some of the neat features.

I’m not going (sadly enough). But you can by me a beer anyways…

Red Gate SQL Compare generally produces better scripts, though I’ve not yet compared against a blank database to create a complete database script!

This one kept restarting multiple times during the flight at random seats!

I can’t think of a good way of implementing an asynchronous handcrafted client proxy.

Add Service Reference and the SvcUtil creates a modified service contract with BeginXXX and EndXXX methods. For the developer this is nice, as the asynchronous method invocation functionality is explicated state and follows the Asynchronous Design Pattern.

I would just use delegates with the handcraftet WCF client, like so:

var proxy = new HelloWorldClient();

Func<string> del = proxy.HelloWorld;

del.BeginInvoke(callback =>
Console.WriteLine(del.EndInvoke(callback)), null);

Can you thing of a better option that explicit states the possibility of the asynchronous method invocation?

Read my blog post “Handcrafting the WCF client” which discuss the different possibilities for WCF-based service clients.

“Handcrafting the WCF client” – http://www.lybecker.com/blog/2009/03/05/handcrafting-the-wcf-client/

What is the similar step for consuming this WCF Webservice ? Please help. Thank you very much in advance.

You must use the standard way of defining generic types in configuration file if you want to use a service contract like IBasicContract

It is written in the configuration file like this: IBasicContract`2[TRequest,TResponse]

I also posted this reply on stackoverflow in case you do not see this.

Anders Lybecker

Anyway, the way I think of read committed snapshot is that writers don’t block readers, but writers still block writers. You’re saying one of the writers will throw an error. I just tried this scenario on a DB where I have is_read_committed_snapshot_on set to on, and the second update blocked until I committed, as I expected.

I think you’re thinking of the conflict detection bit in snapshot isolation level. The article you reference says this: “Unlike Snapshot, it always returns latest consistence version and no conflict detection.”

– ENABLE ALL INDEXES
exec sp_MSforeachtable ‘ALTER INDEX ALL ON ? REBUILD’