Spreadsheet software is widely used by people in every industry with
flexibility for data computing and analysis. But due to inherent drawbacks,
common business spreadsheet software can't conduct relational query like SQL.
The spreadsheet can implement the visualized calculation to some extent, and
the nontechnical people can perform some rather complex calculations without
having to learn the SQL. However, as the core of SQL, the relational query is
unable to be implemented through common business spreadsheet software, which
adds complexity to the apparently simple problems of multi-table join.
For example, the Finance department needs to calculate the salary, and the
relevant data is stored in ”standard sheet”, ” Absence sheet”, and
” performance sheet”, as shown in the below figure:
If these three sheets can be joined, then you can compute it easily via the
Recently, I read "Why Big Data Projects Fail" by Stephen Brobst. I can’t
agree more with his opinions which exposed the problem I’ve been worried
about. In this article, I am going to further discuss this topic to remind
the enterprises to beware of falling into such pitfall of failure.
Let’s have a look on a positive example. As a successful enterprise in
leveraging big data, how does Google make use of the big data?
1. Collect the row data, capture the contents of each website, e-mail, or
Cookie, and extract the key information.
2. Create the complex syndetic index for this inf... (more)
In Java development, the typical data computation problems are characterized
Long computation procedure requiring a great deal of debugging Data may from
database, or Excel/Txt Data may from multiple databases, instead of just one.
Some computation goals are complex, such as relative position computation,
and set-related computation
Just suppose a sales department needs to make statistics on the top 3
outstanding salesmen ranking by their monthly sales in every month from Jan
to the previous month, based on the order data.
Java alone is difficult to handle such computations... (more)
What is IOE? I=IBM, O=Oracle, and E=EMC. They represent the typical high-end
database and data warehouse architecture. The high-end servers include HP,
IBM, and Fujitsu, the high-end database software includes Teradata, Oracle,
Greenplum; the high-end storages include EMC, Violin, and Fusion-io.
In the past, such typical high performance database architecture is the
preference of large and middle sized organizations. They can run stably with
superior performance, and became popular when the informatization degree was
not so high and the enterprise application was simple. With the ... (more)
As we know, the stored procedure is designed to handle computations
involving complex business logics.
In the past, the data structure and business logics were so simple that one
SQL statement was enough to achieve user's computational goal. With the rapid
growing of information industry, users frequently find that they need to
achieve the increasingly complex computational goals to out-perform their
competitors. To address such computations, SQL alone is far from
enough. Database programmers have the additional demands regarding the judge
and loop statements, branches at multip... (more)