Metro is the interface used by the Windows Phone, Windows 8 (the next version of Windows, currently in the preview phase), and the Xbox 360 (pictured below). Microsoft said at last week’s Consumer Electronics Show that Windows 8 will be released on various devices throughout the year. The Windows 8 public beta is due out for the computer in February and it is speculated that the final release will be in October (three years after the release of Windows 7). Microsoft gives five guiding principles of metro design. These principles govern not only Microsoft’s own Metro apps, but should govern applications that independent developers create as well.
Several weeks ago, Microsoft released a developer preview of Windows 8. They provide three versions – a 64-bit version with Visual Studio, as well as 64-bit and 32-bit versions without Visual Studio. As of right now, Windows 8 does not function on any version of Windows Virtual PC. (It will work on Hyper-V servers.) We’re going to briefly explore the Windows 8 interface and some of its features. The initial screen is the “Metro” interface, which was shown in Microsoft’s preview over the summer. This interface is designed with touch screen users in mind. (As of right now, touch screen monitors start at around $300, but presumably they will drop in price once they become more popular.)
One of the database design practices that I have seen more and more frequently in recent years is the use of GUIDs for primary keys. Unless you are implementing merge replication, this is rarely useful and can be both a minor annoyance and a drag on database performance. (Even if you are using replication, a GUID primary key is still an annoyance, but something of a necessary one.) In the off chance that you don’t know what a primary key is and you’re still reading, a primary key is a piece of data that uniquely defines a particular row in a table. Typically, primary keys are either an auto-generated number, a combination of a series number and a foreign key (e.g. page 15 of document 1234), or a piece of meaningful data that is guaranteed to be unique (e.g. social security number). In database theory, “primary key” and “unique constraint” mean the same thing, though most of the popular databases treat them differently. In SQL Server, for instance, the primary key will be used to create a clustered index if you don’t select something else. It’s not especially uncommon to have both a primary key and a unique constraint – for example, a web contact system might use email addresses to uniquely identify customers (a unique constraint), but have a separate customer ID as the primary key.
Can you imagine being paid to do something
illegal out of the ordinary? That’s exactly what Google wants hackers to do. Google is interested in finding out about its security flaws in its Google Chrome browser, so they are willing to pay $1 million to anyone who can expose flaws in the browser. There are several security categories that Google is interested in.
In relational databases, a clustered index is an index that determines the organization of records in a table. This is as opposed to non-clustered indexes, which exist separate from the table data and contain a reference to the row of data corresponding to each node in the index. Internally in SQL Server, data rows for tables without clustered indexes are stored as a heap. A heap (not to be confused with the heap tree structure) is simply an unorganized list of rows. If you insert five rows into a new table, they are added in order. If you delete row three, its space is not reclaimed. If you then add another row, it will try to jam it into row three’s former home if space is available and otherwise it will put it at the end.
Windows 8 Metro News Reader