It looks like my site has been hacked. I’ve reinstalled the blog from scratch to remove it. I appologize for any problems caused to anyone.
Bugfix 1.2-20110729 increases a timeout when estimating the size of a differential backup. Previous releases could fail with a timeout error if the database was large.
WebSockets is a new feature that appears to be a great way to send messages from the server to the browser, however today there isn’t much support, both in browsers and on the server in IIS and ASP.Net.
Today you can use a Comet technique (in particular, Ajax with long polling) which is available in all browsers. Using this concept, the browser makes a standard AJAX call to the server that waits until it receives a message. Asynchronous Pages and Asynchronous Controller allow you to have long running HTTP requests without using precious ASP.Net threads.
I’ve just released version 1.2-20091123 of SQL Server Compressed Backup which can be downloaded here.
SQL Server Compressed Backup will back up SQL Server databases using either gzip, zip or bzip2 compression.
The new features are:
SSAS cube processing can kill running queries. That’s right, it may kill queries in order to commit changes to the cube.
Here is what happens during SSAS cube processing. Continue reading
Bill Galashan, DBA of bet365 sent over the following query that lists the execution plan of the 10 most frequently executed queries.
We got into this due to different query plans coming from a VB or a web app than what was seen when running the same query from Management Studio. Eventually tracked this down to a difference in the set options predominatley whether Arithabort was on or off.
Read more to see his query. Continue reading
A number of people have fears with GWT, for instance
- (not true) GWT isn’t flexible which will lead developers down a dead-end path.
- (not true) GWT is ugly, and can’t be used to make “gucci” UIs.
This post will show that these are just myths. Continue reading
It’s so easy to set up, I can’t believe I haven’t done it before.
We, as developers, have a problem. CPUs will continue to have more cores, and each core is not going to be any faster. The only way to write faster applications is to write multithreaded code, which has two challenges:
- Multithreaded code is complex to write and think about.
- Multithreaded code is difficult to test.
From what I’ve seen, people are pursuing 4 approaches. Continue reading
There is suddenly a lot of interest in functional languages recently. The two advantages are
- Writing a DSL (Domain Specific Language)
- Writing concurrent code
The languages that seem to come up are:
I’m not particularly interested in DSL (despite my last post on code generators), however as CPUs contain more and more cores, we’ll need a way to safely write multithreaded code.
The Clojure project has an interesting post on its approach on simplifying multithreaded code.
Erlang handles concurrency by only having local variables and providing a way to send messages to and from other threads.
Lastly, MPI is a .Net library for distributed processing where the same program executes multiple times and each instance communicates with each other using message passing which sounds very Erlang-like.