Your data, in focus.
A clear view of the Zaintel reporting workspace and the reports ready for their next step.
Schema snapshot
44 tables organized across four imported schemas.
Data gaps to resolve
These gaps currently prevent reports from running as designed.
Explore report library
Customer accounts, at a glance.
Search customer contact details and see account IDs, descriptions, and service indicators where the database supports a verified link.
Sign in to search contact details. This page loads customer records only over the secured connection and after authentication.
Search the directory
| CUSTOMER | TELEPHONE & EMAIL | ADDRESS | ACCOUNT & SERVICE INDICATORS | STATUS | |
|---|---|---|---|---|---|
Sign in to securely load customersSearch partial customer names, phone numbers, or addresses, then filter and sort linked account records. | |||||
All 7 rows in rangteldb_dbo.callforaccount join to customers by (ComCode, CustId), and all 7 have the Home Phone account flag. Account numbers, descriptions, and line numbers are shown for those rows. The invoice ServiceId values do not match homephone.phoneservice, and account ProductCode values do not match homephone.product; the report shows verified service flags and raw product codes, not guessed service names. Customers without a linked account are marked accordingly.
Find the right report.
45 legacy Crystal Reports, organized by business area and checked against the imported data.
Know what’s connected.
A transparent view of the imported database and the gaps between it and the legacy reports.
Snapshot is healthy.
Report coverage needs work.
The SQL dump imported successfully into an isolated MySQL 8.4 instance. Its 44 tables and 295,828 rows are verified. Legacy report dependencies still need to be mapped before a report can run.
Imported source tables
Before reports can run
Every one of the 45 report definitions references it.
Sales, purchasing, reseller invoices, tickets, and SQL views are among the gaps.
Columns, joins, filters, formulas, and subreports need a Crystal Reports export.
HPInvoice exists in two schemas; SQL Server names differ from MySQL schemas.
Table previews require sign-in, use a read-only database account, exclude sensitive columns, and return at most 100 rows per request.
Query your data.
Write a SELECT statement, preview the first 100 rows, or export the full result.
Select a table
Edit or replace the SQL with any single read-only SELECT. Database permissions block writes and protected columns.
Columns
Select a table to view its available columns.
Use joins, filters, grouping, ordering, and subqueries as needed. One SELECT statement only; no comments or writes. Preview shows 100 rows. CSV exports all matching rows. Query execution is limited to 30 seconds.
Understand the connections.
See which table relationships are enforced and which still need confirmation.
Customer data connections
These key matches were checked against the imported rows. No foreign-key constraints exist, so they remain data-verified candidates rather than enforced database relationships.
All 7 account rows map to a customer. Each has the Home Phone account indicator. This supplies account number, account description, line number, product code, and account status for the customer report. The account table contains only 7 rows in this snapshot.
The invoice rows match 763 distinct customer keys. `aniinvoice.AccountNo` does not match the account numbers in `callforaccount` in this snapshot, so the invoice account should not be treated as the current account master.
All 10 sales rows match 6 distinct customers on the composite customer key. The imported schema does not enforce this relationship.
One service row has a phone match, but its meaning is unclear. It is not shown as a customer subscription.