History of a greate technologies
Oracle history
2006First to enforce preventive database auditing controls to help meet compliance requirements by restricting powerful users from unauthorized access to specific information First backup product, Oracle Secure Backup, to embed backup logic directly inside a relational database engineFirst to offer content and records management solutions capable of managing the wide range of diverse data and metadata in a single databaseFirst to offer validated configurations for faster Linux deployment2005Oracle unveiled free database for developers, ISVs and students, Oracle Database 10g Express Edition Powers the world's largest commercial database, a customer data warehouse measured at 100 terabyte (TB)2004First to provide a single customer view from multiple data sources with Oracle Customer DataHub2003First to introduce Enterprise Grid Computing with Oracle 10g First database that is available in production for 64-bit Linux with IPF.2002First database to pass 15 industry standard security evaluations and first Real Application Clustering First native XML support in a relational databaseFirst fully integrated relational and multidimensional databaseFirst database with table compression on Unix, NT and LinuxFirst complete and integrated business intelligence platform2001First database to complete the 3 terabyte TPC-H world record First database to pass over 9 industry standard security evaluationsFirst database with built-in Web servicesFirst database with integrated data miningFirst database with support for real world packaged applications on a clusterFirst database with Hash, Range, Composite and List partitioningFirst database with dynamic memory managementFirst database with built-in workflowFirst database with complete online maintenance operationsFirst to support the JOLAP API
2000First to offer complete and simple software for information management including the Oracle9i Database, Oracle9i Application Server and Oracle9i Developer Suite Provide a single data model and single global instanceIndustry's first Developer Service Provider (DSP)Offers a complete applications suiteFirst to offer developers online services for application developmentFirst to release a production framework for defining Web servicesLaunches first online developers skills exchange, Oracle Technology Network (OTN) XchangeIntroduces fully integrated application server for internet computing-Oracle Internet Application Server (Oracle9iAS)Introduces first internet developer suiteFirst to offer an internet file system built for the internet, Oracle Internet File SystemLaunches Oracle Mobile, wireless applications service providerDelivers the industry's only complete e-business suite, Oracle E-Business Suite 11iLaunches E-Business Network1999First to integrate Java and XML into an application development tool Launches first industry exchange, AutoXchange, with Ford Motor CompanyLaunches complete e-business initiativeProvides applications hosting (Oracle Outsourcing)Delivers first comprehensive, internet-based CRM suiteOvertakes SAP in US manufacturingOffers the only internet platform for mobile, embedded, and information appliance computingFirst relational database management system (RDBMS) ported to LinuxFirst database with XML supportFirst to offer a full-featured internet databaseFirst to introduce capabilities to use XML and SQL in Java servletsFirst to introduce the concept of portlets as a way to integrate applications into an e-business portal
1998Launches Business Online, the first hosting service for enterprise applications designed to be run over the Web Launches comprehensive, internet-based strategic procurement solutionOffers full Web deployment of all applicationsIntegrates front office and enterprise applicationsOffers an integrated business intelligence systemOffers a full-featured flow manufacturing productOffers a complete financial consolidation engineOffers rapid, one-step planningOffers self-service applicationsOffers the first set of application modeling tools that generate 100 percent of the applicationBreaks the 100,000 TPC-C barrierFirst database with Java support1997Builds Internet-based applications Moves client/server applications to the WebSupports Very Large Memory Modules on Windows NTSupports clusters on Windows NTFirst Web database1996Breaks the 30,000 TPC-C barrier Announces an open standards-based, Web-enabled architecture1995First 64-bit relational database management system (RDBMS) Provides Web connectivity kit to the database1994Offers the first media server to support video on demand Supports fingerprint logins
1993Moves character mode applications to the client/server model1992Offers a full applications implementation methodology (AIM)1991Offers row-level locking First to introduce PL/SQL1990First symmetric multiprocessing database1988Offers row-level locking First to introduce PL/SQL1987First symmetric multiprocessing database Offers first business application - Oracle General Ledger1986Supports distributed queries First client-server database1985Offers a parallel server database1984Offers the first database with read consistency1983Offers a VAX-mode database Offers a database written entirely in C, for portability1979Offers the first commercial SQL relational database management system (RDBMS)
Java History Today, we take it for granted that we can access applications and content anywhere, anytime. Because of Java technology, we expect digital devices to be smarter, more functional, more entertaining.But in the early 90s, extending the power of network computing to the ordinary things of everyday life was a radical vision, hatched in secret by a handful of Sun scientists. Java technology was a paradigm-bomb that threatened conventional thinkers and vested interests. A technology that, but for a few twists of fate, might never have happened.The history of Java technology is one of the great adventure stories of Silicon Valley. The coffee table book, "Hello World(s): From Code to Culture, A 10 Year Celebration of Java Technology" was created in commemoration of the 10th birthday.
Linux First Message Linux is introduced by Linus Torvalds, a student in Finland. Who post to the comp.os.minix newsgroup with the words: Hello everybody out there using minix -I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones.
Micosoft asp.net History The Microsoft ASP.NET Futures July 2007 (“Futures”) release is a refresh of the Microsoft ASP.NET Futures (May 2007) release and contains an early developer preview of features providing a wide range of new functionality for both ASP.NET and Silverlight. The Futures release includes early experimental versions of features currently being considered for future versions of ASP.NET and the .NET Framework. The Futures releases assume prior knowledge of the core features of ASP.NET including the previous ASP.NET Futures (May 2007) and ASP.NET AJAX Futures January CTP releases.
SAP History In 1972, five former IBM employees -- Dietmar Hopp, Hans-Werner Hector, Hasso Plattner, Klaus Tschira, and Claus Wellenreuther -- launch a company called Systems, Applications, and Products in Data Processing in Mannheim, Germany. Their vision: to develop standard application software for real-time business processing. One year later, the first financial accounting software is complete, forming the basis for the continuous development of other software components in what later came to be known as the "R/1 system." "R" stands for real-time data processing.By the end of the decade, intensive examination of SAP's IBM database and dialog control system leads to the birth of SAP R/2.
Exchange server restore methods
If the entire Exchange server fails and cannot be booted due to a hardware failure or configuration corruption, you can either restore or reinstall the server to correct the problem. The following table describes three methods you can use to recover from a failed server.MethodDescriptionRestoring the Exchange ServerWhen you restore the Exchange server, you use existing backups to restore the operating system, Exchange, and the data to the same system. Use the following general process to restore the Exchange server:Use your latest backups to restore the entire computer. This will include the operating system and Exchange.Reapply service packs and updates.Restore the Exchange data.Rebuilding the Exchange ServerWhen you rebuild a server, you reinstall a fresh copy of the operating system and Exchange, but configure the computer as if it were the original Exchange server. To rebuild the Exchange server:Install the operating system.Restore the system state data.Reinstall operating system service packs and hotfixes.Install Exchange using Setup.exe /disasterrecovery. This option re-installs Exchange but uses configuration information in Active Directory to configure the new install exactly the same as the failed server.Install Exchange service packs and hotfixes.Restore the Exchange data.Using a Standby Recovery ServerA standby recovery server is a partially-configured server with the exact same hardware and with the operating system already installed. The process for using a standby server is similar to the process of rebuilding the server, except that the operating system is already installed. To rebuild using a standby server:Shut down the failed server and remove it from the network.Move the hard drives to the standby server. Connect the standby server to the network.Restore the system state data from the failed computer to the standby server.Reinstall operating system service packs and hotfixes.Install Exchange using Setup.exe /disasterrecovery.Install Exchange service packs and hotfixes.Restore the Exchange data.Keep in mind the following recommendations for working with failed Exchange servers.If possible, copy the Exchange data from the failed server. As the last step in the process, recopy the data to the restored or rebuilt server instead of restoring the data from backup. This gives you the latest version of the Exchange database.If restoring the Exchange server does not work (if the restored server is still unstable), try reinstalling the server. By reinstalling, you get clean installs of the operating system and Exchange.If the Exchange server is the only domain controller on your network, you will need to restore Active Directory before restoring or reinstalling Exchange. If the Exchange server is one of other domain controllers, make the server a domain controller prior to installing Exchange. Wait for Active Directory replication to replicate domain information to the restored server.If you install Exchange without the /disasterrecovery switch, information in Active Directory for that server will be deleted. Using the /disasterrecovery switch retrieves the configuration information for that server object and reapplies it to that Exchange server.
Microsoft Exchange Server uses
Exchange server Hosting Features: Using Exchange server hosting service, you get all of the benefits of Exchange Server including:
Accessing Your Inbox Anywhere - Exchange 2003 supports Outlook 2003, Outlook Web Access, Outlook Mobile Access, and ActiveSync over the Internet.
Shared Calendars - Share calendars throughout your entire organization. Invite colleagues to meeting, check availability, reserve a conference room and more.
Public Folders - Create public folders to store messages and provide a general share point or personal storage location.
Global Address Lists - Maintain a company-wide address book and email distribution lists for your entire organization.
Why are you waiting exchange to exchange server hosting.
Exchange Server Restore Methods
If the entire Exchange server fails and cannot be booted due to a hardware failure or configuration corruption, you can either restore or reinstall the server to correct the problem. The following table describes three methods you can use to recover from a failed server.
If possible, copy the Exchange data from the failed server. As the last step in the process, recopy the data to the restored or rebuilt server instead of restoring the data from backup. This gives you the latest version of the Exchange database.If restoring the Exchange server does not work (if the restored server is still unstable), try reinstalling the server. By reinstalling, you get clean installs of the operating system and Exchange.If the Exchange server is the only domain controller on your network, you will need to restore Active Directory before restoring or reinstalling Exchange. If the Exchange server is one of other domain controllers, make the server a domain controller prior to installing Exchange. Wait for Active Directory replication to replicate domain information to the restored server.If you install Exchange without the /disasterrecovery switch, information in Active Directory for that server will be deleted. Using the /disasterrecovery switch retrieves the configuration information for that server object and reapplies it to that Exchange server.
Storage Design For Exchange Server 2003
The design of your storage system allows you to optimize the system and protect your data. An effective design strategy considers file location, protection level for the files, and the necessary hardware to support it. The table below identifies one way to structure the Exchange system to ensure optimization and fault tolerance.DriveContentsRecommended ConfigurationC:\Operating SystemRAID 1 or RAID 5D:\PagefileThe pagefile should be on a different physical disk from the operating system. No special protection for the pagefile is required.E:\Transaction LogsRAID 1 or if using a SAN system RAID 0+1F:\Exchange Store DatabasesRAID 5When designing data storage, keep in mind the following recommendations:Separate the transaction logs and databases on even the smallest of systems for fault tolerance and performance.When using default logging, you can optimize your system by storing the saved log files on a disk other than the one used to store the current (E00.log) file.Place the current file on a fast disk to improve performance.Place saved log files on a large disk.If you have multiple storage groups, each group should have their own RAID 5 set.Use SAN/NAS solutions to increase performance and storage capabilities. Verify with the hardware vendor that the system is designed to work with Exchange Server 2003.Use a separate disk for the SMTP queue for increased performance.RAID 0+1 is becoming more common because it delivers better I/O performance and eliminates the need for a write-back cache.In addition to designing disk locations, you can improve manageability and availability by creating multiple stores and storage groups. The following table describes the recommendations for working with each.UnitDesign ConsiderationsStoresBy creating multiple stores, you divide the Exchange database into multiple smaller databases. You might create multiple stores for the following reasons:To establish different store policies. For example, you can create different stores for groups who have different mail retention and deletion policies.To reduce the effects of a store failure or store maintenance on other users. If a store database is lost due to disk failure or corruption, having multiple stores minimizes the effect and allows users with mailboxes in other stores to continue working. Having multiple smaller databases also decreases the time it takes to restore a single store.To make e-mail communications more efficient. Your store organization could mimic the way e-mail communications are conducted in your organization. Identify groups of users who communicate most frequently with each other and create a store for each group.To make the database structure match your organizational structure. For example, you could create different stores for different departments or sites.Storage GroupsWith Exchange Server 2003, Microsoft recommends that you create a storage group for each store until you have reached the maximum number of allowable storage groups. Doing so:Improves virtual memory management.Ensures that fewer stores share the same transaction logs. For example, if you have a single storage
