PHPMem v2.0.1
Version
1.6.45
Uptime
7 days 14 hours 50 minutes 12 seconds
Memory
Total
512MB
Used
13,14MB (2.57%)
Free
498,86MB
Keys
Current
10 026
Total (since start)
11 096
Evictions
0
Reclaimed
196
Expired Unfetched
0
Evicted Unfetched
0
Connections
Current
3 / 1 024 max
Total
70 085
Rejected
0
llm:12a8453deb725ab75022c76a65515598553eecf60f4bafb525590e1a0564fc1c
Edit
This dataset delivers 8,948 rows of B2B sales pipeline intelligence concentrated almost entirely in a single 8,800-row funnel table, supported by four small reference tables (accounts, sales teams, products, and a data dictionary) that together account for only 148 rows. Completeness stands at 93%, but the architecture reveals a critical structural gap: **no foreign key relationships exist between the pipeline and its supporting dimensions**, meaning the system cannot enforce referential integrity between deal records and the accounts, teams, or products they reference. The 100% referential integrity score is vacuously true—there are no constraints to violate—leaving the door open to orphaned records, inconsistent identifiers, and silent data quality erosion that profiling alone cannot detect.
The dataset excels at **single-table funnel analysis**—tracking deal progression, stage conversion, velocity, and value distribution within the pipeline itself—and any descriptive work that does not require joining to account attributes, team assignments, or product hierarchies. It is not suitable for multi-dimensional segmentation (account firmographics, team performance benchmarking, product mix analysis) without manual, error-prone identifier matching, nor can it support reliable drill-through reporting where pipeline metrics must tie cleanly to master data. Decision-makers should treat this as a strong foundation for pipeline health monitoring and stage-level diagnostics, but plan immediate investment in establishing and enforcing relational constraints if cross-dimensional insight or governed reporting is a priority.