Mar 3, 2011

Apple iPad 2 vs iPad: What different?


The iPad 2 is finally here in its full glory! But is it nearly as good as it looks like? We quickly summed up the main novelties that the new iPad offers and compared them to the main features of the original one. It all starts from the design – Apple outshines itself with an even thinner tablet. Actually, the new iPad is even thinner than the iPhone 4 and while you might not want to cut cake with it, you certainly could. One of the few rumors that Cupertino didn't fulfil was the higher resolution expected by some. But in all honesty, we're pretty happy with the tablet's current pixel density.

Feb 15, 2011

Use NOLOCK and READPAST table hints in SQL Server for speed up query

When data in a database is read or modified, the database engine uses special types of controls, called locks, to maintain integrity in the database. Locks basically work by making sure database records involved in a transaction cannot be modified by other transactions until the first transaction has committed, ensuring database consistency.

When designing database applications, you should keep in mind the different types of locks that will be issued, and the different levels of isolation your transactions will occur. Typically, the SQL Server defaults work fine for what you are trying to accomplish. However, there will be times when it is advantageous to manually make hints to how locks are issued on your tables in your SQL statements.

Feb 8, 2011

Tips to Speed up SQL Server database queries

by Tim Chapman, TechRepublic

    If you've worked with SQL Server databases for any amount of time, it's practically a given that you've run into slow running queries. Sometimes the reason for the slow response time is due to the load on the system, and other times it is because the query is not written to perform as efficiently as possible (I find this reason much more common). Learn how you may be able to improve performance by knowing what to look for in your query designs.

    Dec 25, 2010

    The Current Disadvantages of Merging a Place With a Page on Facebook

    By Josh Constine

    With the launch of Places, Facebook began allowing businesses to merge their Page with a Place they’ve claimed. While there are some advantages for businesses focusing on generating foot traffic to a single physical location, merging has important disadvantages including lost functionality (at least for now). Here we’ll take a look two of the biggest problems with merged Places/Pages: an unfamiliar interface, and the inability to set the landing tab.
    Facebook launched Places in August, allowing users to create Places for physical locations they’d like to tell their friends they’ve visited. Legitimate owners of Places can apply to claim their Place, giving them the ability to edit details, moderate comments, and advertise the Place.
    The official guide to Place for advertisers explains that users who claim Places and are also an admin of a similar Page may be prompted to merge their Place and Page. Facebook recommends merging if a business has only one physical location and only one Page. The guide says, “you’ll be able to manage your business centrally on Facebook”, and Likes, content, custom tabs, and ads directing to the Page will remain intact.
    However, Facebook fails to inform admins that merged Places Pages cannot be separated. This has angered some Page admins, and a few have formed a protest Page called “Unmerge Places & My Business Page“.
    An important reason not to merge is that users may be confused by the change in user interface: a merged Places Page does not display tabs the way a traditional Page does. (However, it’s possible will move the tabs under the profile photo like they are on the recently redesigned user profiles – though Facebook hasn’t said that.) Instead, it uses a navigation panel beneath the Page’s picture. Users won’t see a panel of friends who Like that Places Page or previews of uploaded photos and videos, plus the option to suggest the Places Page to friends is dropped to the very bottom of the left sidebar.

    Engaging with merged Places Pages is more difficult as well. The default landing tab is the Profile, which shows the Places address, a map, hours, and a description. Even if users have Liked the Places Page, they still see this tab upon visiting, and have to navigate to the Wall via the navigation panel in order to share their opinions or publish content. This is much different than traditional Pages, where those who’ve clicked Like can immediately post to the wall upon visiting. If getting users to communicate with each other and foster a sense of community is a business’ goal, the traditional Page is a better fit because those who’ve clicked Like see the Wall and publisher first.
    While this navigation format is similar to the newly redesigned user profile, users are accustomed to seeing tab applications along the top of a Page, not running down the left sidebar.
    Another serious deficiency of merged Places Pages is that admins cannot change the landing tab. Many businesses spend a lot of money or time creating custom tab applications or outsourcing this job to a Page management company. Being unable to show these apps to those who haven’t Liked your merged Places Page can hurt Page growth. Therefore, merged Places Pages miss out on much of the opportunity to condition access to tab app contests or content on a user Liking the Page.
    It’s possible that Facebook will address these issues in upcoming product updates, but that’s the way it works for now.
    Facebook says a “A solution for linking multiple Places to a single Facebook Page will become available in the future”, but it first needs to make this a more attractive option. The ability to set a landing tab promotes Page growth, which is important to Facebook as well as admins.

    Facebook Now Allows Merged Places Pages to Unmerge

    By Josh Constine


    Facebook today added an unmerge option to Pages which had been merged with Places. Facebook has allowed an admin of a similar official Page and claimed Places location page to merge these two entities since the launch of the Places location-sharing services in August, but offered no way to undo the combination.
    Merged Place Pages are unable to set a default landing tab, frustrating admins who use custom tabs but had merged without knowing the consequences. The new unmerge option restores all the functionality of the separate entities.
    We discussed a need for the option in our post on the disadvantages of merging earlier this month. Followers of the protest Page “Unmerge Places & My Business”, which has requested the option since early November, are currently rejoicing and thanking Facebook. Facebook’s move has successfully turn some outraged admins back into loyal supporters of the site.
    Admins of merged Place Pages now see an “Unmerge all merged Places” button in the bottom left of their Page. When clicked, admins are shown the following confirmation message:
    Once you confirm this request, the format of this Page will be reverted to the previous format and location information will be removed. The Places that you merged will be restored as separate claimed Places that you also still own and must continue to manage.”
    Admins of merged Places Pages which want to be able to set a landing tab or show a more familiar interface (at least until Facebook rolls out the Page redesigned that leaked last week) should take advantage of the option. Meanwhile, admins of Pages which haven’t merged, have a single physical location, and who want to focus on driving foot traffic can now experiment with merging without being stuck with the result.
    [Thanks to Kim Bui of KPCC Los Angeles for the tip]