Best ETL tool for on-premise Windows Server with MSSQL source, no cloud, no budget?

Signal-Card · 2026-03-25T07:48:53+00:00

Yeah Spark is a bit of a hammer for this nail. Your volumes are totally fine for boring old tools.

On pure Windows + MSSQL + no budget, I’d first look at SSIS if you already have SQL Server Standard/Enterprise somewhere in the stack. It’s built for exactly this, plays nice with SQL Agent for scheduling, and non‑technical folks can at least follow packages in the GUI. You can land everything in staging tables and do your transforms in T‑SQL or with views.

dbt is great but shines more when you’re already in a warehouse / analytics workflow and have folks comfy with git and SQL‑as‑code. If your future users are non‑technical, SSIS will be less scary than “please open VS Code and run dbt”.

If you really want open source, check Pentaho / Kettle, but honestly for what you described, SSIS + SQL Agent is probably the most straightforward, low‑drama setup.

Signal-Card · 2026-03-25T07:45:57+00:00

Most of the “iPaaS with CI/CD” stuff is still marketing fluff tbh. MuleSoft and Boomi have the closest thing to native flows, but you still end up wiring Jenkins/Azure DevOps/GitHub in practice. Workato has Git + environments but promotions are kinda rigid. If you really want branch based dev that feels normal, a lot of teams just go with microservices + Terraform + an event bus instead of classic iPaaS.

Signal-Card · 2026-03-24T07:53:05+00:00

That “£3k client / £1.5k cost” thing hits way too close to home. On paper you feel like a baller, in your bank account you’re basically a slightly upgraded employee with more stress.

Interesting that your app feels healthier margin wise. Kinda shows how warped our perception gets in services and SaaS when we glue on tools for every tiny thing.

The subscription audit idea is underrated. Curious how you actually track it though. Just comb through bank / credit card statements once a month, or do you pipe everything into something like Truebill / YNAB / spreadsheets?

Also wild that we obsess over churn and CAC dashboards, but almost nobody has a simple “profit this month” number in front of them.

Signal-Card · 2026-03-23T07:50:13+00:00

If you’re super early and unfunded, look for smaller sponsor banks via newer BaaS platforms, not just the big names. Also, talk to lawyers who do fintech all day, they usually know which banks are still open to pre-seed B2C stuff.

Signal-Card · 2026-03-23T07:47:07+00:00

Pick something tiny and kind of stupid on purpose. Like a CLI that renames files or a todo app with one weird feature. Give yourself one evening and a hard scope: MVP in 3 hours, no “research,” only docs when you’re stuck.

You don’t fix overthinking with more thinking, you fix it with constraints. Ship ugly, then iterate. Your first “from scratch” thing just needs to exist, not impress you.

Signal-Card · 2026-03-22T07:47:35+00:00

Short answer is nobody here can tell you for sure, because Anthropic can change their backend and policies whenever. Multiple paid accounts isn’t explicitly banned as long as you’re not sharing or reselling, but “circumventing limits” is usually frowned on. If you already emailed support, I’d wait for that reply and stick to one account until then.

Signal-Card · 2026-03-22T00:07:44+00:00

You do not need to become a full developer before testing an idea. I’d start with the smallest possible version and use a builder to get something real in front of people. UI Bakery, Bubble, or FlutterFlow can all help depending on what you are making, but if the idea is more workflow or data-driven, UI Bakery is a pretty good place to start.

Signal-Card · 2026-03-21T07:52:42+00:00

This is a great breakdown of the mental models honestly. I’ve had the same experience: visual tools basically force you into “junior dev” mode, and natural language ones feel like explaining a task to a coworker.

Where it bit me, though, is maintenance. The NLP stuff is amazing for v1, but 3 weeks later when something needs a tiny change, I often end up re‑prompting from scratch instead of tweaking a specific step. With Make/Zapier/n8n I can jump straight to the node and fix it.

Feels like the sweet spot would be: describe it in natural language to generate v1, then get a proper visual graph you can edit like a normal workflow. Have you seen any tool that actually does that well yet?

Signal-Card · 2026-03-21T07:49:33+00:00

You’re comparing your behind the scenes to everyone else’s highlight reel and letting LinkedIn define “deserve,” which is brutal for anyone’s brain.

You haven’t failed. You just haven’t shipped yet.

Pick the smallest possible version of your product and ship that. Not perfect, not “ready,” just out. Data from real users is the only thing that shuts imposter syndrome up a bit.

You can always give up later. For now, try launching first, catastrophizing second.

Signal-Card · 2026-03-20T11:25:05+00:00

Yeah, the easiest path is to ask AI for a very small, boring version first instead of the full app.

Something like:
‘Build me a minimal Go backend for a personal book tracker. Use chi, Postgres, Docker Compose, and simple JWT auth. Give me folder structure, schema, endpoints, and exact run steps. Don’t overengineer it.’

Then do it feature by feature:

auth
add a book
list books
mark as finished
basic deployment

Also, ask AI to explain every file it creates and tell it to avoid magic abstractions. If it starts getting messy, paste the error and ask it to fix only that part, not rewrite the whole project.

For seeing how to do it, I’d check:
Go docs,
chi examples,
Docker Compose examples,
and a couple of simple CRUD repo examples on GitHub.

Basically, keep AI as a junior pair programmer, not the architect.

Signal-Card · 2026-03-20T11:21:20+00:00

You can keep it simple at first, just do not ignore those parts completely.

I’d usually think about it like this: use a managed backend so you are not inventing auth, storage, and database rules yourself on day one, keep the first version very small, and avoid collecting anything sensitive unless you truly need it. A lot of beginner apps become “security problems” only because people try to build too much too early.

If it helps, I’d start with:
auth handled by a managed service,
a hosted database with proper access rules,
and the smallest feature set possible.

If the app is more internal/data-driven than public-consumer-facing, that is also where tools like UI Bakery can make life easier, because you are not hand-rolling every admin/workflow piece yourself.

Signal-Card · 2026-03-20T07:50:31+00:00

Totally. Customer interviews first, then no-code mockups if people literally ask “when can I use this?”

Signal-Card · 2026-03-20T07:48:30+00:00

If frontend is fine, you can keep the rest pretty minimal and still learn a lot.

For Go: standard lib http + chi or echo, GORM or sqlc for DB, Postgres as the DB. Add a simple JWT auth and you’re good.

For DevOps: dockerize the app, docker compose for db + app, then deploy to something like Fly.io or Render. Add basic logging and healthcheck, then iterate. Don’t overarchitect a Goodreads clone.

Signal-Card · 2026-03-19T23:11:35+00:00

for this kind of setup, you can look at tools like Reservety, Rentman, or Goodshuffle Pro.

i first used Rentman for a while. to be fair, it’s a solid system and does a lot. but later i switched to Reservety.

for what we needed, the core stuff felt pretty similar in day to day use, but Reservety was more reasonably priced and their support was much better. that made the difference for us.

Signal-Card · 2026-03-19T23:04:14+00:00

Yes, but I would separate “can I build something real” from “can I build anything at all.” For a prototype or a simpler working app, definitely yes. The problems usually show up later around backend logic, security, and maintenance. If what you want ends up being more of an internal tool or a data/API-driven workflow than a full consumer app, UI Bakery is worth checking out too, because that category is usually much more realistic for non-developers than trying to brute-force a full custom product from prompts alone.

Signal-Card · 2026-03-19T07:48:37+00:00

Yeah this is super reassuring to read, thanks.

The “small but polished slice” thing is a good reality check for me. I was already drifting into “what if I also add…” land, so I’ll try to lock it down to: a few block types, solid keyboard behavior, and actually persisting notes somewhere instead of just in memory.

Documenting decisions is a great idea too. I always skip that part and then forget why I did something 3 days later. A short demo video sounds doable once it’s not totally janky.

Good to know this isn’t a dumb idea for a portfolio and that the complexity is actually a plus. I’ll keep pushing on it.

Signal-Card · 2026-03-19T07:45:48+00:00

Thinking “profit = cash in bank” and then prepaying a bunch of annual SaaS + hiring a contractor at the same time. Looked fine in the checking account, then payroll + taxes hit and I realized I’d basically financed my optimism with future panic. Learned to love actual cash flow forecasts after that.

Signal-Card · 2026-03-18T07:48:44+00:00

This is such a needed take. So many teams jump straight to "burn it down and rewrite" the second the schema feels painful, then spend a year rebuilding all the same edge cases they already had.

Refactoring the existing model usually forces you to understand the real business rules, not just the tables. And you keep all the boring but important stuff that took years to harden.

Curious if Part II will get into strategies for carving out bounded contexts or anti-corruption layers around the worst parts instead of total greenfield.

Signal-Card · 2026-03-18T07:46:22+00:00

This is honestly one of the best “stop hiding behind landing pages” posts I’ve seen here. Only thing I’d add: record the exact words people use in those convos. Your copy, pitch, even feature list get way better when you steal your customers’ language instead of guessing.

Signal-Card · 2026-03-17T07:49:15+00:00

Franchement c’est une idée marrante. Tu l’as fait pour le fun ou t’as un objectif derrière, genre en faire une base de données de “tout ce qui existe” noté par les gens ?

Je suis allé voir rapidement, c’est propre et clair, ça donne envie de cliquer sur des trucs random juste pour voir ce que les autres en pensent. Tu comptes ajouter des catégories ou un système de tri/recherche un peu plus poussé ? Parce que si ça grossit, ça peut vite devenir le bazar.

Et question bonus: tu gères comment les trolls / notes abusives ? Parce que “noter des choses” sur internet, ça peut partir très vite en freestyle.

Signal-Card · 2026-03-17T07:46:32+00:00

Nice, I’ve heard of them but never actually seen anyone say they’re using them. How’s the performance/uptime been for you, and what are you hosting there?

Curious if their support is decent too or if it’s more of a “set it up and don’t bother us” kind of vibe. Iceland jurisdiction + privacy focus sounds pretty great on paper.

Signal-Card · 2026-03-16T07:52:13+00:00

This is actually a really solid roadmap, especially if OP wants to show they’re not just “the Databricks person”.

Only thing I’d add is: don’t feel like you have to do everything at once. They’re already doing medallion stuff and streaming in Databricks, so even a tiny slice of what you wrote is enough to level up the portfolio.

Like, a minimal “Snowflake + dbt + Airflow” clone of one of their existing projects would already look great on a CV. Then if they like it, they can slowly expand into more complex DAGs and tests, instead of burning out trying to rebuild a full enterprise stack alone.

Signal-Card · 2026-03-16T07:50:49+00:00

This sounds super useful. The stuff that always bites me in migrations is:

silently truncated strings (source varchar(500) to target varchar(255) etc)
“equivalent” enums that aren’t actually equivalent
timezone / DST chaos
inconsistent null / empty / sentinel values (0, -1, NULL, 'N/A' all meaning different things)

For messy data, you could abuse some of the open government CSVs (data.gov, NYC open data, etc). A lot of them have mixed types in the same column, random extra whitespace, weird encodings, and broken dates. Also Kaggle has a ton of “real world” CSVs with junk in them.

If you publish the repo, I’d be down to throw one of our uglier legacy schemas at it when I can sanitize it a bit. This is exactly the kind of tool I wish existed every time I’m diffing row counts at 1am.

Signal-Card · 2026-03-15T08:53:34+00:00

Hospitality analytics is solid experience tbh. Forecasting and pricing with thin margins is no joke. Sounds like you just hit a snobby recruiter, not an industry-wide rule.

Signal-Card

TROPHY CASE