Skip to main content

IND VS IRD

Today is very tuff day for indian cricket team in world cup 2011. but they play the match against those team who is highest run chaser in world cup 2011 against that team where the game cricket born [ENGLAND]. The cricket expert called ireland "the joint killer".
Indian batting line up is very-2 strong,they are capable to score highest total, but indian bowling line up is very-2 weak.
if ireland win that game then it is definitely big surprise.
but i am indian and always favour the indian cricket.
I SEND WARM AND GREAT WISHES TO INDIAN CRICKET, I STRONGLY BELIEVE THAT INDIAN TEAM WON THE WORLD CUP 2011.

Comments

  1. Anurag RanaMarch 6, 2011 at 4:30 PM

    sorry little bit typing mistake....

    ReplyDelete
  2. UnknownMarch 8, 2011 at 4:06 PM

    but at last indian tiger took victory over joint killer,,,,,,,,,,,,

    ReplyDelete
  3. UnknownMarch 14, 2011 at 1:12 PM

    Dhoni fu--u.............................
    Bahar nikalo sale ko

    ReplyDelete

Post a Comment

Popular posts from this blog

Standard and Formatted Input / Output in C++

The C++ standard libraries provide an extensive set of input/output capabilities which we will see in subsequent chapters. This chapter will discuss very basic and most common I/O operations required for C++ programming. C++ I/O occurs in streams, which are sequences of bytes. If bytes flow from a device like a keyboard, a disk drive, or a network connection etc. to main memory, this is called   input operation   and if bytes flow from main memory to a device like a display screen, a printer, a disk drive, or a network connection, etc., this is called   output operation . Standard Input and Output in C++ is done through the use of  streams . Streams are generic places to send or receive data. In C++, I/O is done through classes and objects defined in the header file  <iostream> .  iostream  stands for standard input-output stream. This header file contains definitions to objects like  cin ,  cout , etc. /O Library Header Files There are...
Post a Comment
Read more

locking

DBMS Locking Part I (DBMS only) TECHNICAL ARTICLES -> PERFORMANCE ARTICLES [  Back  ] [  Next  ] DBMS is often criticized for excessive locking – resulting in poor database performance when sharing data among multiple concurrent processes. Is this criticism justified, or is DBMS being unfairly blamed for application design and implementation shortfalls? To evaluate this question, we need to understand more about DBMS locking protocols. In this article, we examine how, why, what and when DBMS locks and unlocks database resources. Future articles will address how to minimize the impact of database locking. THE NEED FOR LOCKING In an ideal concurrent environment, many processes can simultaneously access data in a DBMS database, each having the appearance that they have exclusive access to the database. In practice, this environment is closely approximated by careful use of locking protocols. Locking is necessary in a concurrent environment to as...
Post a Comment
Read more

DATA WAREHOUSE VERSUS DATA MART: THE GREAT DEBATE

DATA WAREHOUSE VERSUS DATA MART: THE GREAT DEBATE Customers exploring the field of business intelligence for the first time often lead with: What is the difference between a data warehouse and a data mart? The next question follows as predictably as night follows day: which one does my company need? Let me start by saying that the two terms are often confused. Indeed, some people in the industry use them virtually interchangeably, which is unfortunate, because they do reflect a valuable hierarchical difference. The Data Warehouse A "data warehouse" will typically contain the full range of business intelligence available to a company from all sources. That data consists of transaction-processing records, corporate and marketing data, and other business operations information; for example, a bank might include loans, credit card statements, and demand deposits data, along with basic customer information. This internal data is frequently combined with statistica...
2 comments
Read more