SEARCH

Found 3628 related files. Current in page 1

membuat database dengan microsoft excel 2007

zv_line_2010_09 - Zentralverwaltung - Universität Augsburg

September 2010 1. Statistik der Online-Bewerbung für das WS 10/11 Die Online Bewerbung für Studierende war auch in der bisherigen Bewerbungsphase für das WS 10/11 ein voller Erfolg. Über 15.000 Bewerber haben Ihre Daten eingetragen und sich erfolgreich beworben. Welche Tage sind besonders frequentiert? Das erfahren Sie im folgendem Artikel. An welchen Tagen der Woche bewerben sich die potentiellen Studierenden an der Universität Augsburg? In der unten stehenden Grafik ist ersichtlich, dass sich die Kontakte über die gesamte Woche verteilen. Besonders beliebt ist der Montag (21%, 3077 Bewerbungen) und der Dienstag (19%, 2884 Bewerbungen) zu sein. Im Laufe der Woche nehmen die Aktivitäten immer weiter bis zum Samstag (8%, 1158 Bewerbungen) ab, bis dann am Sonntag (11%, 1710) wieder die Aktivitäten zum Montag hin steigen. Abb. Verteilung der Bewerbungen auf die einzelnen Tage Soweit die aktuellen Zahlen aus der Statistik der Bewerbung zum WS 10/11. Im nächsten Jahr werden zum SS 11 und vor allem zum WS 11/12 weit höhere Zahlen zu erwarten sein. In diesem Jahr steht nämlich der doppelte Abiturjahrgang (G9 und G8) in Bayern für ein Studium in den Startlöchern. Die EDV Technik des DV Referates wird auch diese Bewerberzahlen sicher und zuverlässig online durch das System führen. 2. Bereit für Office 2010? Seit ein paar Monaten gibt es die neueste Microsoft Office-Version auf dem Markt: Office 2010. Abb. Verteilung der Bewerbungen auf die Wochentage Zu welchen Phasen der am 10.05.2010 gestarteten Bewerbung, sind die meisten Aktivitäten zu erkennen? Deutlich ist in der folgenden Grafik zu sehen, dass bis zum 28.06.2010 durchschnittliche Bewerbungszahlen zu verzeichnen sind. Ab diesem Zeitpunkt ist ein deutlicher Anstieg zu sehen, der mit den ausgehändigten bayerischen Abiturzeugnissen in Zusammenhang steht. Danach gibt es eine erhöhte Aktivität bis zum 15.07.2010, dem Ende der Bewerbung für die NC Fächer, zu verzeichnen.

europäische kulturhauptstadt 2020 – legt freiburg seine bewerbung ...

M Die Idee zu einer Bewerbung hatte bereits im Oktober 2007 KultStadtrat Atai Keller. Die offiziellen Reaktionen vom Kulturbürgermeister, einzelnen Fraktionen und Kulturschaffenden waren positiv. Hinter vorgehaltender Hand aber heißt es aus Rathauskreisen auch: „Dass das kleine Freiburg Europas Kulturhauptstadt wird, ist so wahrscheinlich wie dass der Sportclub Deutscher Fußballmeister wird.“ In diese Minimalchance viel Geld zu investieren, könnte der Kultur sogar schaden: Denn wo soll das Geld für eine erfolgreiche Bewerbung denn herkommen, wenn es nicht an anderer Stelle gespart wird. Der Ministerrat der Europäischen Union hatte 1985 auf Initiative der griechischen Kulturministerin Melina Mercouri das Projekt „Europäische Kulturhauptstadt“ mit dem Ziel beschlossen, einen Beitrag zur Annäherung der europäischen Völker zu leisten. Der begehrte Titel der Europäischen Kulturhauptstadt geht vermutlich 2020 – in jenem Jahr feiert Freiburg seinen 900. Geburtstag – oder 2021 wieder nach Deutschland. Bisher durften sich hierzulande Berlin 1988, Weimar 1999 und im kommenden Jahr Essen samt Ruhrgebiet über die Auszeichnung freuen. Im Kern einer erfolgreichen Bewerbung steht nicht etwa die Frage, was der Titel, was Europa Freiburg bringen könnten, sondern genau die gegenteilige: Was kann Freiburg Europa bringen? So fragt denn auch eines der Kriterien für eine Ernennung explizit nach dem Beitrag der Stadt zur europäischen Kunst- und Die Stadtspitze hat mittlerweile eine 32-köpfige „Konzeptgruppe Kulturhauptstadt“ gebildet, die sich am 27. Juli im Ratssaal wieder treffen wird, und in der neben von Kirchbach und einer Handvoll städtischer Amtsleiter auch Musikhochschulen-Rektor Rüdiger Nolte, Theater-Intendantin Barbara Mundel, Solararchitekt Rolf Disch, Fabrik-Vordenker Martin Wiedemann, der Theater im MarienbadVorsitzende Hubertus Fehrenbacher, Wirtschaftsförderer Bernd Dallmann und Vertreter der Universität und des Architekturforums sitzen.

Packaging design as a Marketing tool and Desire to ... - Theseus

Ksenia Polyakova Packaging design as a Marketing tool and Desire to purchase, 72 pages, 2 appendices Saimaa University of Applied Science Faculty of Business Administration, Lappeenranta Degree Programme in International Business Bachelor’s Thesis 2013 Instructor: Mr. Riku Hytönen Senior Lecturer, Saimaa University of Applied Sciences The purpose of the study was to examine the consumer perception on different design elements of a milk package and to provide essential information for the companies about the consumer attraction and importance of design attributes from the consumer point of view. The theoretical framework was based on the secondary data (articles and books) and included core concepts of packaging, packaging design, consumer behavior, consumer perception, and consumer attraction. The mixed method was selected for acquiring and analyzing the research results. Quantitative data was collected from 30 questionnaire responses and was analyzed with the computer program Excel. Qualitative data was obtained from two interviews conducted with the companies, Valio Ltd and Tetra Pak Ltd. The results of the study revealed the importance of packaging design in consumer buying behavior. By examining the consumer perception, it was found out that packaging design elements such as graphics, color, and product information play a key role in decision making and ensure consumer’s attention. Based on the findings, it was defined that successful milk packaging design could be created by the cooperation between the consumer and the company. Further research could investigate other product packages’ design elements.

Scalable SQL and NoSQL Data Stores - Rick Cattell Home Page

In this paper, we examine a number of SQL and socalled “NoSQL” data stores designed to scale simple OLTP-style application loads over many servers. Originally motivated by Web 2.0 applications, these systems are designed to scale to thousands or millions of users doing updates as well as reads, in contrast to traditional DBMSs and data warehouses. We contrast the new systems on their data model, consistency mechanisms, storage mechanisms, durability guarantees, availability, query support, and other dimensions. These systems typically sacrifice some of these dimensions, e.g. database-wide transaction consistency, in order to achieve others, e.g. higher availability and scalability. Note: Bibliographic references for systems are not listed, but URLs for more information can be found in the System References table at the end of this paper. Caveat: Statements in this paper are based on sources and documentation that may not be reliable, and the systems described are “moving targets,” so some statements may be incorrect. Verify through other sources before depending on information here. Nevertheless, we hope this comprehensive survey is useful! Check for future corrections on the author’s web site cattell.net/datastores. Disclosure: The author is on the technical advisory board of Schooner Technologies and has a consulting business advising on scalable databases.

MongoDB - Oracle
by geeh_ya 0 Comments favorite 1 Viewed Download 0 Times

Oracle NoSQL Database and MongoDB server are both licensed under AGPL while MongoDB has certain client drivers under the Apache 2.0 license.  Oracle NoSQL Database is in many respects, as a NoSQL Database implementation leveraging BerkeleyDB in its storage layer, a commercialization of the early NoSQL implementations which lead to the adoption of this category of technology. Several of the earliest NoSQL solutions were based on BerkeleyDB and some are still to this day e.g. LinkedIn’s Voldemort. The Oracle NoSQL Database is a Java based key-value store implementation that supports a value abstraction layer currently implementing Binary and JSON types. Its key structure is designed in such a way as to facilitate large scale distribution and storage locality with range based search and retrieval. The implementation uniquely supports built in cluster load balancing and a full range of transaction semantics from ACID to relaxed eventually consistent. In addition, the technology is integrated with important open source technologies like Hadoop / MapReduce, an increasing number of Oracle software solutions and tools and can be found on Oracle Engineered Systems.

From Only-SQL to NoSQL to YeSQL - GigaSpaces

It has now been a good couple of years since the various anti-SQL proponents have gained enough momentum to come together under the wide umbrella of the term NoSQL. And it is clear that we can never go back: the typical relational database architecture is clearly insufficient for today’s dataintensive applications, and the move to distributed architectures. But is the problem in the architecture or the query language? The two are not interchangeable, though frequently confused. Some answers can be found in the following articles, which represent a progression of ideas on this very relevant topic, based on various articles published in Nati Shalom’s blog: http://natishalom.typepad.com Should Web Apps "Just Say No" to SQL? Pros and Cons of Non-SQL Patterns This paper briefly reviews what is driving the trend of adopting alternatives to the traditional SQL DB, survey alternative approaches, and discuss not only their benefits but also the risks and caveats for real-life web applications.

Ultra-High Performance NoSQL Benchmarking - Aerospike

As companies deal with ever larger amounts of data and increasingly demanding workloads, a new class of databases has taken hold. Dubbed “NoSQL”, these databases trade some of the features used by traditional relational databases in exchange for increased performance and/or partition tolerance. But as NoSQL solutions have proliferated and differentiated themselves (into key-value stores, document databases, graph databases, and “NewSQL”), trying to evaluate the database landscape for a particular class of problem becomes more and more difficult. In this paper we attempt to answer this question for one specific, but critical, class of functionality – applications that need the highest possible raw performance for a reliable storage engine. There have been a few attempts to provide standardized tools to measure performance or other characteristics, but these have been hobbled by the lack of a clear mandate on exactly what they’re testing, plus an inability to measure load at the highest volumes. In addition, there is an implicit tradeoff between the consistency and durability requirements of an application and the maximum throughput that can be processed. What is needed is not an attempt to quantify every NoSQL solution into one artificial bucket, but a more systemic analysis of how some of these databases can achieve under assumptions that mirror real-world application needs. We attempted to provide a comprehensive answer to one specific set of use cases for NoSQL databases -- consumer-facing applications which require extremely high throughput and low latency, and whose information can be represented using a key-value schema. In particular, we look at two common scenarios.

History Repeats Itself - EDBT
by prolato 0 Comments favorite 0 Viewed Download 0 Times

In this paper, I describe some of the recent developments in the database management area, in particular the NoSQL phenomenon and the hoopla associated with it. The goal of the paper is not to do an exhaustive survey of NoSQL systems. The aim is to do a broad brush analysis of what these developments mean - the good and the bad aspects! Based on my more than three decades of database systems work in the research and product arenas, I will outline what are many of the pitfalls to avoid since there is currently a mad rush to develop and adopt a plethora of NoSQL systems in a segment of the IT population, including the research community. In rushing to develop these systems to overcome some of the shortcomings of the relational systems, many good principles of the latter, which go beyond the relational model and the SQL language, have been left by the wayside. Now many of the features that were initially discarded as unnecessary in the NoSQL systems are being brought in, but unfortunately in ad hoc ways. Hopefully, the lessons learnt over three decades with relational and other systems would not go to waste and we wouldn’t let history repeat itself with respect to simple minded approaches leading to enormous pain later on for developers as well as users of the NoSQL systems! Caveat: What I express in this paper are my personal opinions and they do not necessarily reflect the opinions of my employer.

Solving Data Integration Challenges with SQL and NoSQL - FOSE

Many organizations today would seemingly be content with having achieved an information architecture that features a broad-scope enterprise resource management environment feeding data in batch for reporting and analytics to a robust data warehouse environment. As a bonus, the data warehouses in this post-operational environment may consist of solid-state components and automated archival abilities. Irreversibly, the environment also has been inundated with data marts fed from original source and from the data warehouse itself. There is frequently a multidimensional database in the mix. Or a hundred. If there is any contentment with such an architecture, it will be short-lived. With information the “new gold” for companies, each shop must do everything it can to nurture, protect, make available and otherwise exploit the information asset. This will frequently mean venturing into new technology domains for the management of the asset. One may be tempted to consider the NoSQL movement as the epitome of these new technology domains. However, many possibilities have been laid on the table by the vendor community in the years prior to NoSQL. Most have merit in an enterprise today. We clearly need to get away from the winner-take-all mentality where every workload – sometimes whether it is analytical or operational – will be solved the same way as the last one. Frequently, that way was with a data integration operation with the data warehouse followed by the deployment of more reports in the business intelligence tool. Force-fitting a workload into a technology that it was not designed for creates more problems than it solves.

Will NoSQL Databases Live Up to Their Promise? - Leavitt ...

Organizations that collect large amounts of unstructured data are increasingly turning to nonrelational databases, now frequently called NoSQL databases. M any organizations collect vast amounts of customer, scientific, sales, and other data for future analysis. Traditionally, most of these organizations have stored structured data in relational databases for subsequent access and analysis. However, a growing number of developers and users have begun turning to various types of nonrelational—now frequently called NoSQL—databases. Nonrelationa l dat a ba ses— including hierarchical, graph, and object-oriented databases—have been around since the late 1960s. However, new types of NoSQL databases are being developed. And only now are they beginning to gain market traction. Different NoSQL databases take different approaches. What they have in common is that they’re not relational. Their primary advantage is that, unlike relational databases, they handle unstructured data such as word-processing files, e-mail, multimedia, and social media efficiently. They are also easier to work with for the many developers not familiar 12 r2tec.indd 12 computer with the structured query language. SQL is the programming language used for querying and updating relational databases. Some NoSQL databases can function in a distributed setting. Users could thus scale a single database by running it across additional inexpensive machines rather than by having to run it on a single more powerful and costly machine.

« previous  123456789