Database Management Systems

In Salesforce master-detail relationships, the detail side of the relationship MUST be a custom object - standard objects cannot be the detail in a master-detail relationship. A standard object can be the master of a custom object, and standard objects can have lookup relationships to each other, but a standard object cannot serve as the detail side when the master is a custom object.

Data-centric applications focus primarily on data storage and management (like Time Card apps for tracking hours and Inventory management for stock data), while process-centric applications focus on business processes and workflows (like Online Auction Management which handles the bidding process). Word Processor is neither - it's a document creation tool, not characterized by data storage or business process management.

PMON (Process Monitor) determines the number of concurrent users to the database. PMON monitors and manages user processes and connections, controlling database access and resource allocation.

In MVS (Multiple Virtual Storage) systems, datasets are organized collections of data. Within a dataset, data is organized into smaller units called records. A record is a single, complete unit of related information (like one row in a file). This is the fundamental hierarchical structure: dataset contains records, records contain fields/bytes.

In Informatica PowerCenter, Integration Service is the runtime engine that moves data from source to target systems. Repository Service manages metadata, Application Services handle application-specific tasks, and Metadata Services provide metadata access.

Sequences are database objects specifically designed to generate unique sequential numbers, often used for auto-incrementing primary keys. Clusters are for physical storage organization, synonyms are alternative names for objects, and views are virtual tables - none generate unique numbers.

Normalization is the database design process of organizing data to reduce redundancy and dependency. Views are virtual tables, aliases are alternative names, and sequences generate unique numbers - only normalization specifically addresses redundancy reduction.

Memory Analysis in JProbe helps identify Java garbage collection issues (objects not being collected, memory leaks) and object cycling problems (objects being created and destroyed excessively). It's not for finding bottlenecks/deadlocks (that's Performance Analysis), identifying unexecuted code (that's Code Coverage), or is irrelevant.

The correct workflow in JProbe is to first create or edit the analysis settings to configure what you want to measure, then attach to the application session to start profiling, and finally load snapshots to view the collected data. Loading snapshots before attaching would mean there's no data to view yet. This logical sequence ensures the profiler is configured before data collection begins.

The 'Set Recording Level' option in JProbe allows you to control the granularity and amount of data collected during profiling. You can choose from different recording levels based on your needs - from detailed method-level tracking to high-level overviews. This helps manage the trade-off between comprehensive data collection and runtime overhead. Trigger, Configure Pool, and Leak Doctor are other JProbe features with different purposes.

SQL Azure (now called Azure SQL Database) is essentially SQL Server hosted as a service on the Windows Azure platform. It's not MySQL, and Windows Azure is not part of SQL Server - rather, SQL Server is part of the Azure platform.

Team Foundation Server 2010 uses Microsoft SQL Server as its backend data store for all version control, work item tracking, build data, and other metadata. It does not use MS Access or a file system for the backend.

Microsoft has reported over 30,000 SAP deployments running on SQL Server, reflecting strong enterprise adoption of the database platform for mission-critical ERP workloads.

WorkPool in PEGA is a logical grouping mechanism that collects similar Work Objects together based on shared characteristics or criteria. This organization helps in managing and tracking related work items efficiently. WorkGroups and ClassGroups are different organizational structures in PEGA.

BusinessObjects supports various file formats as data providers. Option D includes all common formats: .asc, .prn, .txt, .csv, .xls, .xml, and .dbf. These are all valid data source formats that can be imported into BusinessObjects universes or reports.