28 March 2010

Database Architecture with SQL Server 2008 - Part 3, File Groups, Files & Partitions

In our last post we discussed the different storage options we have and which is best in what situation. I also said in that article that most of the stuff being discussed there is out of the area of databases itself as storage is mainly handled by the operating system and database literally don't care if it is a physical drive or a network drive as long as it can read and write on it. but saying that, Database's main work is to store and retrieve the data, and in this article we will discuss how SQL Server does that.

SQL Server stores its data in its files, there are two types of these files.
  1. Data File -- Where the actual data is stored. (.mdf, .ndf file extension)
  2. Log File -- Where the transaction log is maintained. (.ldf file extension)
SQL Server organizes its data into a data structure called "Data Pages", each data page is of 8 kilo bytes. A Data file consists of series of such data pages, the actual data is spread across these data pages, if the data in a table row is more that 8K, its spread against multiple data pages, otherwise same data page can be used for multiple rows of data, For Large columns such as varchar(max) or BLOB the data is not stored in the same data page with the rest of data for that row but an address pointer is stored instead which addresses to the data page in which the actual data for that column-row is stored.

SQL Server gives you the flexibility to configure the storage location of these files, which is pretty obvious and its behavior which is not very clear. To understand this first let me explain you what a File Group is

File Group

A file group is a collection of data files that serves as a logical storage unit for database, so when you define the database objects that are physically stored such as Tables & Indexes you specify the File group you are using for the object, There can be multiple files groups associated with a database instance and each file group can have multiple files in it. So the big question is what do we achieve by doing so?

In my previous posts I have already explained that the storage is finite, small files perform better than large files, distributed information is faster to access than information consolidated in one single file. so making all this presumptions basis of our argument its fair to say that if a database has multiple data files, located on different physical drives it will perform better and will have a better capacity planning than a single data file database.

One thing to note here is the Log file does not belong the a file group and normally there is one log file per database. Log file as the name implies, stores the log of all the changes (inserts, updates, deletes) you made in your database, its used by the DBAs to track the changes and rollback if required. Log files are also utilized in certain backups.

How File Groups & Files works

Now as we have understood what File groups and files are, let us focus on how they work. When you define a File group there are two important properties you configure.

  1. Read-Only -- This specifies the data in objects built on this file group cannot change. Normally this is set later on and not at the time of database creation. It is used in the cases of Lookup tables or historical data table where you want to ensure that there is no modifications for such tables.
  2. Default -- There can be only one default File group. At the time of object creation if you do not specify any file group the default one will be utilized. The default file group also contains some meta data about the database which the other file groups does not have.




In the example above I have created two File groups, PRIMARY & SECONDARY. Now once the File groups are defined we will now create files under it.



As you can see there are four files here, 3 of them are data file with file type "Rows Data", while one is a log file. I have associated two files to the PRIMARY file group while the other to the SECONDARY file group. The four important configurations for files are
  1. File Group -- Which file group this file belongs to
  2. Initial Size -- When the database is created what should be the file size by default.
  3. Auto Growth -- How the file grows when the data in the file reaches the file size.
  4. Path -- Where the file will be stored.
In the example we specified the initial size to be 2 MB for the data files and 1 MB for log file. so in the image below you can see the files created with these sizes.


Now once this is defined we are ready to create our tables and other objects. As you can see below that when we are creating an object we can select which file group this object will be created on.

SQL Server handles how the data will be distributed across the files in a file groups and it follows an intelligent round robin method by taking into account the file size and auto growth parameters.

Partitions

Now everything is good here, but what if one of your table has or it could have massive amount of data and this results in performance issues or storage capacity problems. What we have learned that the objects are created on file groups now how can we divide the storage of an object across multiple file groups to resolve the performance issues. This is where Partitions are used. Partition divides a Table across multiple file groups using a systematic scheme.

Partitioning is achieved by three steps.

  1. Partition Function -- This is a function that defines how we will distribute the data into partitions.
  2. Partition Scheme -- Here we tell which file group will be used for each partition created by the partition funciton
  3. Table Partition -- Once we define the above two we create the table on the partition scheme and the rest is taken care by the SQL Server itself.
So now lets take this example, We have a product table which we want to partition, we are dividing the table into two partitions based on its primary key ProductId, We want all the records with primary key less than 50000 to go in PRIMARY File group while the rest should go in the SECONDARY file group. So here how we will do this.

First we will define our Partition function.

Now based on this function we will create the partition scheme

And than assign this partition scheme to our table.

and finally tell the SQL Server that use the ProductId column for partitioning through Partition Column List.

21 March 2010

Database Architecture with SQL Server 2008 - Part 2, Storage

Storage means a device or set of devices that will digitally store the data which can be retrieved later, Storage can be permanent such as Hard Disks, CD/DVD, USB flash drives or temporary like RAM. In this article we will refer to storage as permanent storage devices.
Databases simply cannot exists without a storage, in fact database is a layer between the end user(application) and the physically stored data. So how you setup your storage defines how good your database design is. When a database storage or as a matter of fact any storage is designed, following points must be considered
  • Performance -- How fast is my storage
  • Reliability -- Will I lose data if my storage fails
  • Scalability -- What if I need more storage space
  • Ease of Management -- Can I manage my storage
  • And everyone's favorite "Cost" -- Will the cost of my storage fit my wallet.
Obviously you cannot have everything in one solution, hence you pick the things based on your preferences and compromise on the others. Normally Storage is designed before you setup your database and Storage setup is independent of Database and storage management is done by Operating systems or Storage management softwares and for Databases its pretty much hidden.

Before going into the Enterprise storage solutions let us first look into the difference between a single storage device vs RAID.

Single Device vs RAID

What we use in our daily lives is a single device, such as a hard disk. It can be internal or external. but that's one single device, you can attach another hard disk in your computer but that will be another single device. Both of these hard disks will work independently to each other and for good reasons don't even know the other exists or not and in your operating system they will show up as separate devices. Obviously you can have partitions on it but that's a different story. So whats wrong with these single devices and why do we need anything else, the answer for this you have already read, if not go back to the beginning of my article where I talked about the different things you should be looking in your storage i.e. Performance, Reliability. Scalability, Ease of Management and Cost. We will rule out the ease of management and cost here as single devices offer the best in this, but lets focus on the other important factors.

Performance - Single devices have single controllers hence they can write only one bit of information at a time or in other words multiple write operations cannot run in parallel. and one write operation will start when the other finishes. This means the single devices are not high performing.

Reliability - Single devices have definite single point of failure, if this device crashes, burns or destroyed you lose all your data with it. which is quite frankly very scary.

Scalability - Single devices are not scalable and your data is ever growing, so if you need more storage space, you either replace it with a bigger disk and go through the pain of transferring all your data or attach another one but obviously that will exist as a separate device and you could only have a few devices connected to your machine. So sooner or later you might be replacing your disk.

so here comes RAID (Redundant Array of Independent Disks) to the rescue, RAID is collection of two or more disks that are connected to the machine as one logical disk. RAID has different schemes which offers performance, reliability, scalability or all of them. We will talk about the most frequent schemes here for the rest you can refer to our favorite site Wikipedia. All different RAID schemes offers scalability so if you need more space just add another disk in the RAID and Eureka, Infact many RAID devices has hot swappable feature which makes it possible to Add or remove disk without disconnecting or switching of the RAID.

RAID 0: RAID 0 provides data stripping, which means the data is divided on the disks in the RAID, this scheme provides performance as the read/write operations are performed simultaneously on all the disks, the drawback with this scheme is that it provides no redundancy and a single disk failure results in full RAID failure.

RAID 1: This schemes provides data mirroring, which means that the same set of information is written across all the disks hence providing data redundancy. This model does not offer any considerable performance gains, but it provides fault tolerance so in case of a disk failure the other disk will provide the same data and there is no data loss.
RAID 1+0 or RAID 1E: This schemes combines the advantages of both model by providing data stripping and mirroring. This scheme works with atleast 3 disks in RAID by distributing the data on multiple disks to gain performance but maintaining the copy of each block on a other disk to achieve redundancy, so in case of a disk failure the rest of the disks can still provide all the data.
RAID 5 : RAID 1E looks like a perfect solution but as you know there is always a room for improvement, The problem with RAID 1E or RAID 1 is that we are dedicating a large portion of the disks for a redundant data which we might never use, and disks are not that cheap. So if we can find a way to have fault tolerance but at the same time reduce the space the redundant blocks of data are taking than it would be much better. So this is where RAID 5 is the savior. RAID 5 provides performance by data stripping across multiple disk but instead of storing a redundant block it stores the Parity information. and in case of failure it reconstructs the information by combining the parity information with the data on the other disks. RAID 3 and 4 also works on this parity model but the location of this parity block is dedicated while in case of RAID 5 parity is also distributed.
Now as we have understood the difference between single storage devices and RAID, we will now look into how these storage devices are used in an enterprise.

DAS (Direct attached storage)

Direct Attached Storage is a storage device (Single Device) or a collection of storage devices (RAID) that is connected the the Server directly, It can be internal or external and are connected to the server/machine using interfaces such as SATA, SCSI, USB or Firewire. These storage devices does not work independently and is managed by the machine its connected to. These devices can be shared over the network, but the request passes through its connected server machine.

NAS (Network Attached Storage)

NAS is a file server, NAS is similar to DAS the difference is that instead of it being connected to a server machine, its directly connected to the network, it has its own IP address/Host name and the NAS Device has its own OS which only provides File System level operations. Like DAS, NAS can also be in Single device or RAID model. NAS is used for centralized storage model, like backups etc.


SAN (Storage Area Network)

While NAS works fine in a network it has its own shortcomings, first it uses Ethernet protocol for communication which does not provide very high data transfer speeds and this ethernet is in most cases not dedicated for storage therefore you have other network traffic on it which further reduces the performance, secondly NAS does not distribute its storage among servers, it is one device with lots of storage space but all the machines accessing it has access to the same storage, except for if you put some security permissions. Now here is the beauty of SAN, SAN is a network of storage devices, so all the storage devices/servers you add in the SAN adds up into the total storage space of SAN, SAN has its own network that works over FibreChannel instead of ethernet that offers much much more faster data transfer speeds and only the servers that are required this storage are connected to this network using special NIC called Host Bus Adapter (HBA). SAN Storage shows up as physical drives instead of network shares in the servers. But the most prominent feature of SAN is its storage allocation, let us take an example. Say you have three servers you have connected to the SAN, and the total storage capacity of your SAN is 5 Tera bytes. so if you want to give Server 1 & 2 around 1 Tera byte each and the other rest of the storage space you could configure this in SAN Manager and each server will have drives with the required storage and at any point of time this storage division can be changed without affecting the servers. This gives the companies much more flexibility in terms of how to use your storage intelligently. SAN is almost the perfect technology but because of its obvious benefits and advanced technology the cost of implementing and maintaining a SAN is much more higher than the other schemes.



13 March 2010

Database Architecture with SQL Server 2008 - Part 1, Connectivity

In this series of articles I will focus on different aspects of SQL Server 2008 Database, A normal tendency in IT systems is to give too much emphasis on the Data model and not that much on other important aspects of a Database server, The objective of this series is to take you through all the different components of a database server and how can you design a Database architecture with, Performance, scalability, reliability and security.

Connectivity

In every Server/Client model the first and foremost thing is the communication protocol through which the server and client talks to each other. Microsoft SQL Server offers different protocols for connectivity, In this article I will try to explain each protocol to make easier for you to choose the protocol that is right for you. I will also focus on how the connectivity mechanism works in various protocol scenario. What we will not be looking into this article is the security mechanism during connectivity which I will cover in my later posts.

Following are the network protocols commonly used in SQL Server, Other protocols include, VIA, HTTP, DAC which are used in special circumstances.

1. Shared Memory

Shared memory is the fastest connectivity protocol available as its name explains the client and server communicates through memory, and it works in a single server scenario only, which means the client and the server must exists on the same machine to use this protocol. Unfortunately this option in not applicable in most of the production scenarios as Database server and application server resides on different machines.

2. Named Pipes

SQL Server also offers connectivity through Named pipes which is a queuing mechanism, Named pipes are system persistent pipes which works in FIFO mode, Named pipes works in single server or Local area network scenarios.

3. TCP/IP

TCP/IP is an industry wide network communication protocol used in LAN, WAN and internet scenarios. TCP/IP is the most widely used protocol for connectivity between database server & clients as it works in all different infrastructure topologies.

These protocols are installed as part of the Operating System installation and are not installed during SQL Server installation. If any protocol needs to be added it has to be first installed in the operating system. By default the above mentioned protocol comes with the Windows Operating system.

How the connectivity works.

Like in all Server Client models, there is a server application and multiple client application instances, in our case the Server application is the SQL Server Database engine. While the client application is called SQL Server Native Client (SQLCLI) Library, SQL Server Native Client (SQLNCLI10) is a data access technology that is new to Microsoft SQL Server, and it is a stand-alone data access Application Programming Interface (API) that is used for both OLE DB and ODBC. All other applications that connect to SQL Server Data engine internally uses the SQL Server Native client library. Previously MDAC or DB Library used to fill this role. It is mandatory for a successful connectivity that both server and client are working on a common protocol.

From MSDN: “When the SQL Server Database Engine communicates with an application, it formats the communication in a Microsoft communication format called a tabular data stream (TDS) packet. The network SQL Server Network Interface (SNI) protocol layer, encapsulates the TDS packet inside a standard communication protocol, such as TCP/IP or named pipes. The SNI protocol layer is common to both the Database Engine and SQL Server Native Client. The SNI protocol layer is not directly configured. Instead, the server and SQL Server Native Client are configured to use a network protocol. Then, the Database Engine and SQL Server Native Client automatically use the appropriate protocol settings. The server creates a SQL Server object called a TDS endpoint for each network protocol. On the server, the TDS endpoints are installed by SQL Server during SQL Server installation. For the named pipes and shared memory protocols, there can only be one endpoint per instance. There are no configurable endpoints for these protocol types. For TCP/IP and VIA, there is a default endpoint, but additional endpoints can be created.”

When a connection to the Database engine is initiated by the SQL Server Native Client, the network protocol is selected based on the order defined in the SQL Client Configuration. And an attempt to establish a connection to the that protocols TDS endpoint is tried, if the connection fails then the next network protocol in the list is attempted.



SQL Server Browser Service

When an instance of SQL Server starts, if the TCP/IP or VIA protocols are enabled for SQL Server, the server is assigned a TCP/IP port. If the named pipes protocol is enabled, SQL Server listens on a specific named pipe. This port, or "pipe," is used by that specific instance to exchange data with client applications. Because only one instance of SQL Server can use a port or pipe, different port numbers and pipe names are assigned for named instances. By default, when enabled, both named instances and SQL Server Express are configured to use dynamic ports, that is, an available port is assigned when SQL Server starts. If you want, a specific port can be assigned to an instance of SQL Server. When connecting, clients can specify a specific port; but if the port is dynamically assigned, the port number can change anytime SQL Server is restarted, so the correct port number is unknown to the client.

A SQL Server Browser services addresses this problem by assisting the client to locate the full address of the database engine, Upon startup, SQL Server Browser starts and claims UDP port 1434. SQL Server Browser reads the registry, identifies all instances of SQL Server on the computer, and notes the ports and named pipes that they use. When a server has two or more network cards, SQL Server Browser returns the first enabled port it encounters for SQL Server.

When SQL Server clients request SQL Server resources, the client network library sends a UDP message to the server using port 1434. SQL Server Browser responds with the TCP/IP port or named pipe of the requested instance. The network library on the client application then completes the connection by sending a request to the server using the port or named pipe of the desired instance.

If the SQL Server browser service is disabled, the client must provide the complete address of the database engine including the port number or pipe name in order to establish a connection, This only applies in the case of remote connections.

Alias

Another alternate to Full address problem is to create alias, you can define a friendly named alias for a database instance in the client configuration by specifying the protocol and the required details such as Server name or IP, and port or pipe address. And then using this alias in your client applications to address the database instance. Alias also gives you the flexibility of changing the Database instance’s address details without a need to change anything in the client applications, the only change would be to update the new address in the alias settings.

08 March 2010

Hardware Virtualization Models

Virtualization refers to the abstraction of computer resources, which means creating a a logical or virtual computer resource which does not exists physically. Virtualization can be done at many levels or in other words any computer resource can be virtualized, but the most common practice is called Hardware or Platform virtualization.

Our hardware is theoretically built to run a single operating system. Therefore a single machine is configured to run one OS on it. In case of server machines with high specifications this results in a severe under usage of its computing capabilities, e.g. A machine built just for the purpose of Directory services. This resulted in the concept of hardware virtualization, which creates several standalone "virtual" machines on a single physical machine, The software installed on these Virtual Machines cannot distinguish whether its installed on a physical machine or a virtual one. hence making it possible to share its hardware resources with multiple virtual machines which are working in isolation and this process is called Hardware or Platform Virtualization

May be you still wondering what the hell I am talking about, OK lets take an everyday example, You work in an office and your job responsibilities include keeping record of Accounts, HR and Sales. One way is to have a record book for each. Now your miserly accountant is complaining about you spending too much money on these books and also points to the fact that you hardly use you HR book. To keep his mouth shut you decide to a buy a bigger book with dividers in it. So now you have one single book but by using dividers you have created section for all the different types of records you keep. so actually you have virtualized your record book and created 3 Virtual books out of one actual book. One more thing to notice out of this analogy is that the size of the virtual books is changeable based on your needs and it is also dependent on the actual size of the actual book. Similarly when you create virtual machines the resources assigned to a virtual machine is dependent on the physical machine resources, Hence the more powerful physical machine you have, the more powerful Virtual machines there may be.

Hardware virtualization has many advantages such as Scalability, Ease of deployment, Sandboxing, etc more on this can be found on the internet, but the focus of this article on the two High level virtualization models and its pros and cons.

1. Application based Hardware Virtualization


In an application based hardware virtualization a base operating system is installed on the hardware and a virtualization application is installed on the base operating system, along with other applications (Optional). This virtualization application which in the figure above we have called Virtual Machine Manage is responsible of creating and managing Virtual machines. This model is commonly used more in Development, testing or research scenarios in which you use your machine for some dedicated virtual machines along with your normal usage. and where the performance of the virtual machine is not that critical.



The biggest advantage of this model is its ease of deployment and cost as most of the Virtual Machine managers are available freely, secondly your machine is not solely dedicated for your virtual machines and you can use it as a normal PC, if and when you want. Thirdly you directly interact with your host PC without the requirement of any intermediate machine to connect to your host machine.

The biggest disadvantage of this model is its performance overhead, as the host machine is running a base operating system, this OS has its own processing/memory footprint, as this OS is made not only to run the Virtual machine manager but also other applications and services, so this ends up in consuming a good chunk of processing and memory from the host machine. This brings us to the second virtualization model.

2. OS based Hardware Virtualization


This model is frequently used in live production scenarios, where there are dedicated servers for virtualization and the sole purpose of these machines is to have multiple virtual machines running on it, In this case the Base OS is a very basic Hypervisor Operating system which has a very low Processing/Memory footprint as it offers only the virtualization related services and nothing else. This ensures the major chunk of the processing and memory goes to the hosted virtual machines and the OS consumes as little as possible.



The biggest advantage is the performance of the virtual machines. The drawback of this approach is the host OS does not provide any other services, but this can be overcome by creating a virtual machine for your needs, another drawback is in most cases these server machines are connected or managed through remote services as the Host OS does not provide comprehensive interface for its management, so this might result in additional hardware or terminal to access the Virtual machines, This model is best used in data center scenarios.

Lots of products and technologies are available for both the models which you can easily search for. Virtualization has lots of potential and if intelligently used can save you some serious money.

05 March 2010

Noble Ubuntu

Atlast the machine is now working fine, the issue was with the graphics card and it was replaced. But I am still not sure with which Operating System should I go with. One thing I am sure is that in some capacity I will be using Vitualization to host different Virtual machines on my Computer, but there are many options and architectures I could adopt such as using the basic Virtualization model of Microsoft Virtual PC or VMWare Player based Virtual Machines on a Windows 7 Host platform or go for a more advanced Hypervisor based model of Microsoft Hyper-V Server or VMWare ESX technology. I will post more about virtualizaton in my coming posts. Well until I make up my mind about it I thought to have a go at Ubuntu which my friend told me about few months back.


Ubuntu is a Linux(Debian) based operating system created with a very noble moto "Free software for everyone" derived from its literal meaning "Humaity to Others" from an African languauge. Its a full fledge GUI based Operating system, the setup (ISO file) is a mere 650 MB which is downloadble from its site. Download this file and burn it on the CD, boot the machine using this CD and the setup will start, The OS installation is very simple and with a few clicks the OS is ready for use. One thing I ll like to add here is Ubuntu is based on Linux File System which is inheritied from UNIX. Its a very powerful File system quite different from the ones in Microsoft Operating Systems (FAT, NTFS). The best part of it is that the file system hides the underlying storage devices & partitions from the OS and the applications. The root of the file structure is "/" unlike in Windows where there is no top node in file strucuture, And different hard drives, partitions and CD Drives or even remote storages goes under this Root Node e.g. /cdrom is the path for CD Drive, This makes it very easy for the OS and applications to traverse through the file system. and also makes it possible to change the underlying storage of a particular folder without affecting the related applications

I was really impressed with the range of Software packages that comes with the default installation. such as OpenOffice which is a complete Office Suite, Mozilla Firefox browser, GIMP an Image editor with feature set similar to Adobe Photoshop, Music Player, Email Client, Instant Messanger client, DVD burner, Movie player. The UI was very simple and was to some extent similar to Windows. I had few problems with Graphics resoultion & WIFI but in the end it all worked fine. There are loads of other software packages available through a Ubuntu Software Center application.

Ubuntu is a great noble effort by its creator to provide a complete operating system for everyone which is absolutely free. Hats off to them.

04 March 2010

Partitioning the Hard disk

Hard disk partitioning as described by wikipedia is "Disk partitioning is the act or practice of dividing the storage space of a hard disk drive into separate data areas known as partitions.". Simply put, Partition gives you multiple logical drives out of your one physical Hard drive that will make you organize the data more efficiently. Partitioning provides several benefits, and with the new huge disks now in market its a better practice to intelligently partition your hard disk, some of the advantages are ,

  • Separating the OS drive from the rest of data, hence in case of OS crash and reformatting the OS drive, you don't lose data or go in the hassle of backing it up.
  • Performance gains, as partitions are smaller in size then one full HD, the seek time is shorter
  • Having different File systems as per need for each partition.
  • Improved data organization. etc.
Its much better to partition when your hard disk is new and empty, although most of the partitioning tools makes it possible to partition later on, but you might end up losing data.

For Windows 7 the minimum requirement for Hard disk space is 16 GB for 32 bit and 20 GB for 64 bit, but its better to keep a minimum 50 GB OS partition. In some forums it is recommended that the page file should be on a different partition, but after some research I conclude that one should move page file on a separate hard disk rather then the a separate partition. so keep the page file on your OS partition in case you don't have additional hard drive.

I recommend to divide your HD into 3 partitions. and use the 20-40-40 rule , like 20% for OS , 40% for Programs, and 40% for Data. . You can tweak this based on your Hard drive space and requirements, e.g one good partition scheme for a 500 GB Hard drive could be
  1. OS -- 75 GB
  2. Programs -- 200 GB
  3. Data -- 225 GB

There are many good partitioning tools available, Windows also offers Disk Partitioning. But if you want more advanced options here are few good Disk Partition softwares in the market.
So partition your hard drives and get more out of it.

03 March 2010

The Machine has Arrived

Atlast I've got the machine!, first to blame is the Dubai weather which kept me from going to Computer market day before yesterday, anyways I went yesterday, explore a good number of 5-6 shops got the idea of the price ranges and then bought 1. Had to go with lots of permutations and combination of PC specifications to fit the bill in my budget but at the same time do not compromise that much on the machine, The machine cost totaled to 2900 AED ~ 790 USD . I'll take you through my machine specs in a while but guess what, The freaking thing is not working when I brought it home :'( . I plugged in everything and when I started it, after few seconds it beeps and there is no display. To check whether its a problem of my monitor I plugged it with my laptop and it worked like charm. It must be the CPU, anyways I ll take it back to the shop and hopefully get it resolved today. Coming back to the specifications of the machine.


  1. Processor -- Intel Core 2 Quad Q8400 2.66 GHz
  2. Motherboard -- Gigabyte EP-41 UD3L
  3. Memory -- Patriot 2GB SLS x 2
  4. Storage -- Western Digital 500 GB SATA
  5. Optical Drive -- LG 24x SATA
  6. Graphics Card -- ASUS 9500 GT 1 GB
  7. Casing -- AOpen ES55D
  8. Monitor -- LG LCD W2243s 22''
  9. Network Interface -- D-Link DWA-510
  10. Input Device -- Logitech EX1000
It turned out to be quite decent machine, hopefully I ll get the issue resolved ASAP and will then post the performance results.

01 March 2010

First Step




Hi, Big day today. I am finally going to buy a new machine. Buying a computer is not that simple, there are just too many choices :S. but I had to set my priorities. My first priority was to set a dedicated place for work away from TV and bed :), so I decided to have a desktop PC instead of a laptop, secondly in the price range I am looking for I ll get a far superior customized desktop machine than a branded laptop. I opted to go for PC rather than MACs because MACs are insanely expensive. I've put a 3k AED budget for my machine and the price quotations I took from shops I think I ll get a good deal. and incase I need to work on the MAC platform I will build a VM for it.

I will post the full specifications of the machine once I get it but basically I am going for a

The shop told me that it will take around 1 day to get the machine. so in the meantime I ll also need to get a computer table and chair and might visit Ikea for that, as they have good collection.

My wife was a little skeptical about all this as I frequently gets these rush of blood and enthusiasm that fades away rather quickly, but I need to prove her that this time I am really serious about work :D.

Wish me luck