Essential resources for business and IT professionals tasked with designing an effective enterprise-wide business applications strategy – covering issues on cloud vs. on-premises apps, purchasing tips, implementation and upgrade best practices and...
Download Now!Oracle DBA tools, Backup and recovery, Database design, Export, import and migration, Installation, upgrades and patches, Error messages, Oracle performance problems and tuning, Oracle security, Availability, Real Application Clusters (RAC), Cloud infrastructure, MySQL database
BPEL in Oracle, SQL, PL/SQL, Stored procedures, Java / J2EE, XML, Open Source
Enterprise and business performance management, E-Business Suite, Implementing and upgrading Oracle apps, Fusion applications, JD Edwards (JDE), PeopleSoft, Hyperion, Siebel and Oracle CRM
Oracle Web 2.0, Oracle strategy and product roadmap, Oracle support services, Oracle vs. SAP, Regulatory compliance, Market analysis, Oracle acquisitions, Oracle on demand and SaaS, Outsourcing, Business process management, Small businesses, DBA jobs training and certification
Oracle and BEA, Application Server, SOA (service-oriented architecture), Data and application integration
BI (business intelligence), Metadata, Data quality, Data warehousing
Cloud computing infrastructure, Exadata and Exalogic, Virtual machine, Operating system, Oracle hardware decisions, Oracle on Linux, Grid computing
The "analyze table" is obsolete (from Oracle 7), and Oracle recommends that you always use dbms_stats. Your can save and re-use statistics with the dbms_stats.export_schema_stats procedure. If statistics are in place, Oracle will use them unless you have optimizer_mode=rule. This was first published in October 2004
Join the conversationComment
Share
Comments
Results
Contribute to the conversation