The Significance of Google Chrome

by Joe Havelick 13. September 2008 17:28

Why would Google decide to throw it's hat in the ring of the current browser wars?  Chrome represents a win/win scenario for Google since innovations in the browser market are quickly and uniformly adopted by the few competitors.  How quickly did IE change it's interface around in IE 7 to include tabbed browsing and other new feature once Firefox became a viable threat to their market share?  Google has placed Chrome out into the world as a proof of concept for several key features of which their core business plan depends heavily on.  Particularly:

  1. Vast performance improvements on JavaScript processing
  2. Isolation of each open page within individual processes
  3. Integration with Google Gears/Application Shortcuts

Even if the major players in the browser war simply adopt some of the innovations in Chrome, Google still comes out ahead.  Google foresees the decline of the desktop OS and the shift towards cloud computing.  Having already developed a reputable suite of web-based applications, the current shortcomings include the lack of a stable platform which manifests itself in two areas. 

First, there remains a lack of a consistent and reliable connection to the internet.  The idea of a web application is not appealing if you're not going to be able to pop open a document or presentation for review and revision in an airplane without connectivity to the web.  To counter that, Google has developed the Google Gears toolkit, which allows for seamless us of web applications, regardless of current connectivity. 

Second, the lack of a reliable, fast, and stable platform (which in this case, is a browser).  Google has done a remarkable job creating applications which function smoothly and quickly using the current implementation of JavaScript.  However, it has it's limits.  It was never designed to handle full fledged applications, and is prone to both performance and stability issues when utilized as such.  V8 is a all new engine designed from the ground up with performance and stability in mind, giving Google a solid platform on which to develop their web applications.  Additionally, the isolation of applications within their own processes provides a more forgiving environment in the case (god forbid) of an application error which crashes the process.

So really, if IE, Firefox, and other browsers adopt some of these changes, which they are most likely to do in order to remain as competitive as possible, they're simply playing into the hands of Google.  For Microsoft, this represent a most interesting decision, since they are not only in the browser market with Google, but the web application framework (Silverlight), and cloud computing markets.  Smooth move by Google.



Flushing local domain resolver cache.

by Joe Havelick 1. May 2008 21:12

While troubleshooting DNS related issues, it may become practical for you to flush the local cache of resolved domains.  The following command, run from the command line, will do just that.

ipconfig /flushdns


Tech Tips

Microsoft SQL 2005 Version Guide

by Joe Havelick 6. March 2008 09:17

The following is my cheatsheet for determining which version(s) of SQL are appropriate for a particular implementation. 

Microsoft SQL 2005 Version Guide
Specifications Express 2005 Workgroup 2005 Standard 2005 Enterprise 2005
Max CPUs 1 2 4 None
Max Ram 1GB 3GB OS Limit OS Limit
Max Database Size 4GB None None None
Management Studio Yes Yes Yes Yes
64-Bit Proc. Support* No No Yes Yes
Advanced Integration Svcs. No No Yes Yes
Notification Services Yes Yes Yes Yes
SQL Agent No Yes Yes Yes
Report Server Yes Yes Yes Yes
Analysis Services No No Yes Yes


Flushing Transaction Logs and Recovering Space in SQL

by Joe Havelick 4. March 2008 09:24

The following script will truncate eveything from the SQL transaction log, and shrink the file.

--Truncate the Transcation log
---Shrink the physical file with 10% reserve


Tech Tips

Deleting Records and Recovering Space in SQL Database

by Joe Havelick 27. February 2008 23:08

On the occasion that you must removed data from a table and recover the space, there is a two step process to do this in SQL.

First, you must delete the data, using TRUNCATE or DELETE.  The difference between the two has to do with how the data is removed.  The delete command allows for a WHERE clause, and the deletions will be processed into the transaction logs.  TRUNCATE, on the other hand, is a method for the bulk deletion of an entire table, and it not processed into the transaction logs.

Second, in order to reclaim the disk space previously consumed by data, you must ask the database files to resize themselves accordingly.  The following script exemplifies how to truncate a database table, then resize the database (leaving a 10% reserve for future growth).


/* --Remove All Records from TableName */

/* --Shrink the database files with 10% reserve */


Tech Tips

Determining SQL Table Sizes

by Joe Havelick 11. February 2008 22:45

When you need to understand where which tables are consuming the most space in your database, the following script will come in handy.More...


Tech Tips

About Me

Joe Havelick is a reasonable facsimile of this photo.

profile for Joe on Stack Exchange, a network of free, community-driven Q&A sites