> ## Documentation Index > Fetch the complete documentation index at: https://support.entegrata.com/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Understand resources and how they represent collectible data within connections ## Overview Resources are the individual tables, views, API endpoints, or files within a connection that Entegrata collects. Each resource represents a specific dataset you want to synchronize to your data lakehouse. ## Key Concepts ### What is a Resource? A **Resource** is a collectible data entity discovered within a connection: The resource identifier (table name, view name, API endpoint path, or file name) The kind of resource: * **Table** - Database table with data rows * **View** - Database view (virtual table) * **Endpoint** - API endpoint providing data * **File** - Data file or spreadsheet Collection state: * **Active** - Resource is collecting data * **Inactive** - Resource is not collecting Columns or properties within the resource (e.g., customer\_id, name, email) ## Resource Lifecycle Resources are automatically discovered when you create a connection or when discovery runs (every 3 hours) Enable resources and configure collection settings (schedule, load type, filters) Enabled resources collect data according to their configured schedules Track collection jobs, performance, and data quality Update settings, handle schema changes, or disable resources as needed ## Resource Types ### Tables Database tables containing rows of structured data: * Most common resource type * Have defined schemas with columns and data types * Support full and incremental loads * May have primary keys defined by the database ### Views Database views (virtual tables based on queries): * Derived from one or more tables * Schema defined by the view query * Typically use full load (incremental may not be supported) * Primary keys must be user-defined ### Endpoints API endpoints providing structured data: * REST API paths or GraphQL queries * Schema discovered from API responses * Support pagination and filtering * May have rate limits ### Files Files containing structured data: * Excel spreadsheets, CSV files, JSON documents * Schema inferred from file structure * May contain multiple sheets or sections * Typically use full load ## Resource vs. Connection Understanding the relationship: | Aspect | Connection | Resource | | ------------------ | ------------------------- | ------------------------------- | | **Scope** | Entire data source | Single table/view/endpoint | | **Discovery** | Discovers all resources | Discovered within connection | | **Schedule** | Default for all resources | Can override connection default | | **Enable/Disable** | Affects all resources | Affects only this resource | | **Authentication** | Stores credentials | Inherits from connection | | **Collection** | May trigger all resources | Triggers single resource | ## Collection Settings Each resource can be configured with: ### supp ## Resource Status Indicators Resources display status information: ### Active Resource Active resource with toggle on * Toggle is ON (green) * Collects according to schedule * Jobs appear in collection history ### Inactive Resource Inactive resource with toggle off * Toggle is OFF (gray) * Does not collect data * No jobs created ## Load Type Indicators Resources show their configured load type: Load type badges * **Full** - Full load every collection * **Incremental** - Incremental load with change tracking Click the badge to quickly open collection settings. ## Getting Started with Resources Browse and search discovered resources Turn on data collection for specific resources Configure schedules, load types, and filters Manually start collection jobs ## Common Workflows ### Initial Setup After Creating Connection Allow automatic discovery to complete (1-5 minutes) Browse the discovered resources in the Resources table Toggle on the specific tables/endpoints you need Set load types, unique keys, and filters for each resource Save changes and watch the first collection jobs ### Ongoing Maintenance * **Monitor collection jobs** - Check for failures or performance issues * **Handle schema changes** - Respond to discovery alerts about schema modifications * **Adjust schedules** - Optimize timing based on data freshness needs * **Update filters** - Refine data selection criteria ## Best Practices Enable a few resources first, verify they work, then add more Incremental loads are faster and more efficient for large tables Always define unique keys to ensure proper deduplication Filter at the source to reduce data transfer and storage Watch initial jobs to catch configuration issues early Keep notes on why certain resources are enabled/disabled ## Next Steps Learn how to browse and search resources Understand how resources are discovered Track collection execution and performance