New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by James Vastbinder on Nov 20, 2006
The common problem situation faced by SQL Server developers is a desire to normalize their queries. The advantages of using a normalized query provides the developer with a way to track executions of a query with different parameters and over time monitor execution performance. To normalize a query is to replace the literals in the query with parameter markers like this example from Ken's blog post.
SELECT * FROM foo WHERE id=4
Here, the parameter is “4”, so, parameterized, the query would look something like this:
SELECT * FROM foo WHERE id=@p1
Often, in seeking to simplify workload, developers will fall into common pitfalls, like trimming a substring query to its bare essentials. This approach is prone to error since you cannot accurately define a substring length such that it will always normalize a query.
The best path for developers involves utilizing sp_get_query_template which takes the text of a query as a parameter and returns both the normalized text and the parameter list. There are some limitations to this approach which Ken outlines in his blog, but when seeking to tune your SQL Server database indexes and queries this method provides the richest set of performance aggregation information.
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Getting Started with Stratos - an Open Source Cloud Platform
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
No comments
Watch Thread Reply