The Scenario
You're a database administrator. Your company is consolidating a dozen legacy applications onto a new infrastructure stack, and someone has collected 20 JDBC connection URLs from various old systems into a Google Sheet. Each URL is a compact string — host, port, database name, username, and sometimes a schema, all crammed together. You need them broken apart into separate columns so the migration checklist can be reviewed by the team without anyone having to mentally parse a JDBC string at 9 AM.
The bad version:
- Open the first URL in column A: 'jdbc:postgresql://prod-db-01.internal:5432/orders_db?user=svc_app'.
- Manually extract host, port, database, and user — type each into columns B through E.
- Move to the next row, repeat the parsing.
- Do this 20 times, then check your work because you're not confident you caught the port on row 7, which was formatted differently from the others.
Migration checklists exist to catch errors. They shouldn't be the source of them.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the URLs from your column and through its NocoDB integration can pass each one through NocoDB's URL parser, writing the extracted components into separate columns — structured and ready to review.
Column A has JDBC connection URLs — parse each one using NocoDB's URL converter and write host, port, database, and user into columns B through E
What You Get
- Column B contains the host extracted from each URL.
- Column C contains the port number.
- Column D contains the database name.
- Column E contains the user or service account name.
- Any URL that doesn't parse cleanly (missing port, non-standard format) is flagged rather than silently dropping values.
What If the Data Is Not Quite Ready
Some URLs use different JDBC drivers and have non-standard formats
Column A has JDBC URLs from multiple drivers — parse each one and write host in B, port in C, database in D, user in E — for any URL where parsing is ambiguous or incomplete, write 'PARSE ERROR' in column F with the raw URL
You also need a clean connection string reconstructed in a standard format for the new system
Column A has JDBC URLs — parse each into host (B), port (C), database (D), user (E) — then in column F reconstruct a clean 'host:port/database' string from the extracted components
Some rows have multiple URLs from the same application listed in separate columns
Columns A and B each have JDBC URLs from the same legacy app — parse both and write the extracted components for column A into columns D through G, and for column B into columns H through K
Full kill-chain: parse all URLs, flag format inconsistencies, add a standardized output column, and count errors
Column A has JDBC URLs — parse each into host (B), port (C), database (D), user (E) — in column F, write a standardized 'host:port/database' string — in column G, write 'OK' if all four fields parsed cleanly or 'INCOMPLETE' if any are missing — write the count of incomplete rows into cell I1
One prompt parses, reconstructs, validates, and counts — the migration checklist gets built in a single run.
Try It
Get the 7-day free trial of SheetXAI and open the sheet with your JDBC URLs before the next migration planning session, then ask it to break every connection string into structured columns. Also useful: Pull a NocoDB Table Schema Into a Google Sheet for Documentation and the NocoDB integration overview.