This document discusses scheduling updates in streaming data warehouses. It proposes a scheduling framework to handle complications from streaming data, including view hierarchies, data consistency, inability to preempt updates, and transient overload. Key aspects of the proposed system include defining a scheduling metric based on data staleness rather than job properties, and developing two modes (push and pull) for auditing logs to provide data accountability. The goal is to propagate new data across relevant tables and views as quickly as possible to allow real-time decision making.

1. Targetj Solutions
 REAL TIME PROJECTS
 IEEE BASED PROJECTS
 EMBEDDED SYSTEMS
 PAPER PUBLICATIONS
MATLAB PROJECTS
 targetjsolutions@gmail.com
 (0)9611582234, (0)9945657526

2. Scalable
Scheduling of
Updates
in Streaming
Data
Warehouses

3. Abstract
 We then propose a scheduling framework that handles
the complications encountered by a stream warehouse:
view hierarchies and priorities, data consistency, inability
to preempt updates, heterogeneity of update jobs
caused by different interarrival times and data volumes
among different sources, and transient overload.
 A novel feature of our framework is that scheduling
decisions do not depend on properties of update jobs
(such as deadlines), but rather on the effect of update
jobs on data staleness. Finally, we present a suite of
update scheduling algorithms and extensive simulation
experiments to map out factors which affect their
performance

4. Existing System
 Recent work on streaming warehouses has focused on
speeding up the Extract-Transform-Load (ETL) process . There
has also been work on supporting various warehouse
maintenance policies, such as immediate (update views
whenever the base data change), deferred (update views only
when queried), and periodic [10].
 However, there has been a little work on choosing, of all the
tables that are now out-of-date due to the arrival of new data,
which one should be updated next

5. Disadvantages
 The problem with this approach is that new data may arrive on
multiple streams, but there is no mechanism for limiting the
number of tables that can be updated simultaneously. Running
too many parallel updates can degrade performance due to
memory and CPU-cache thrashing (multiple memoryintensive
ETL processes are likely to exhaust virtual memory), disk-arm
thrashing, context switching,

6. Proposed System
 Many metrics have been considered in the real-time scheduling
literature. In a typical hard realtime system, jobs must be completed
before their deadlines a simple metric to understand and to prove
results about.
 In a firm real-time system, jobs can miss their deadlines, and if they do,
they are discarded. The performance metric in a firm real-time system
is the fraction of jobs that meet their deadlines. However, a streaming
warehouse must load all of the data that arrive; therefore no updates
can be discarded.
 In a soft real-time system, late jobs are allowed to stay in the system,
and the performance metric is lateness (or tardiness), which is the
difference between the completion times of late jobs and their
deadlines.
 We are not concerned about properties of the update jobs. Instead,
we will define a scheduling metric in terms of data staleness, roughly
defined as the difference between the current time and the time
stamp of the most recent record in a table

7. Proposed System
 Associated with the accountability feature, we also develop two
distinct modes for auditing: push mode and pull mode. The push mode
refers to logs being periodically sent to the data owner or stakeholder
while the pull mode refers to an alternative approach whereby the user
(or another authorized party) can retrieve the logs as needed. In
summary, our main contributions are as follows: We propose a novel
automatic and enforceable logging mechanism in the cloud. To our
knowledge, this is the first time a systematic approach to data
accountability through the novel usage of JAR files is proposed. . Our
proposed architecture is platform independent and highly
decentralized, in that it does not require any dedicated authentication
or storage system in place. We go beyond traditional access control in
that we provide a certain degree of usage control for the protected
data after these are delivered to the receiver. We conduct
experiments on a real cloud testbed. The results demonstrate the
efficiency, scalability, and granularity of our approach. We also provide
a detailed security analysis and discuss the reliability and strength of our
architecture.

8. Advantages
 The goal of a streaming warehouse is to propagate new data
across all the relevant tables and views as quickly as possible.
Once new data are loaded, the applications and triggers
defined on the warehouse can take immediate action. This
allows businesses to make decisions in nearly real time, which
may lead to increased profits, improved customer satisfaction,
and prevention of serious problems that could develop if no
action was taken

9. Software Requirements
 Operating System : Windows XP Professional
 Environment : Visual Studio .NET 2010
 Language : C#.NET
Web Technology : Active Server Pages.Net
 Back end : MS-SQL-Server 2008

10. Hardware Requirements:
Processor : Pentium III / IV
Hard Disk : 40 GB
Ram : 256 MB
Monitor : 15VGA Color
Mouse : Ball / Optical
Keyboard : 102 Keys

11. Reference
 [1] B. Adelberg, H. Garcia-Molina, and B. Kao, “Applying Update
Streams in a Soft Real-Time Database System,” Proc. ACM SIGMOD
Int’l Conf. Management of Data, pp. 245-256, 1995.
 [2] B. Babcock, S. Babu, M. Datar, and R. Motwani, “Chain:
Operator Scheduling for Memory Minimization in Data Stream
Systems,” Proc. ACM SIGMOD Int’l Conf. Management of Data, pp.
253-264, 2003.
 [3] S. Babu, U. Srivastava, and J. Widom, “Exploiting K-constraints to
Reduce Memory Overhead in Continuous Queries over Data
Streams,” ACM Trans. Database Systems, vol. 29, no. 3, pp. 545- 580,
2004.
 [4] S. Baruah, “The Non-preemptive Scheduling of Periodic Tasks
upon Multiprocessors,” Real Time Systems, vol. 32, nos. 1/2, pp. 9-
20, 2006.
 [5] S. Baruah, N. Cohen, C. Plaxton, and D. Varvel, “Proportionate
Progress: A Notion of Fairness in Resource Allocation,” Algorithmica,
vol. 15, pp. 600-625, 1996.