Print labels straight from Microsoft SQL Server

Who this is for

Manufacturing, warehouse and distribution teams running an ERP or WMS on SQL Server that produces label data no exporter covers.

How it works

1. Install the LabelInn Windows app and your Microsoft SQL Server client driver on the machine that will run the job.
2. Add the Microsoft SQL Server connection: host, port 1433, database and a database user that can read the tables you need.
3. Write the Microsoft T-SQL query that returns exactly the rows you want to label, one row per label.
4. Map each result column onto a label field — text, barcode, QR or RFID — then preview a few rows.
5. Print the result set, or save the query so the next run is one click.

Write ordinary T-SQL. Use SELECT TOP n while you are testing so a preview never pulls the whole table.

What you can do

• Result columns bind to any label field, so barcode and QR content comes straight out of Microsoft SQL Server.
• Re-run the saved query whenever you need the current rows — no export, no copy-paste, no stale file.
• Mix database columns with static text, counters, dates and serial numbers on one label.
• Printed rows are recorded in the print history, so a reprint or an audit can find the exact job later.
• Queries can be parameterised, so an operator supplies a work order or batch number instead of editing SQL.

Questions

Does label data leave my network when I print from Microsoft SQL Server?

The query runs from the machine you installed LabelInn on, against your own Microsoft SQL Server server. Credentials stay local. What leaves the machine is what you choose to sync — the label design and the print record.

Which Microsoft T-SQL do I write?

Ordinary Microsoft T-SQL. LabelInn does not rewrite your SQL; it runs the statement you saved and maps the result columns onto label fields. Use `SELECT TOP n …` while testing.

Can I print to a Zebra or TSC printer from Microsoft SQL Server without a driver?

For models LabelInn drives natively over ZPL, TSPL or TPCL, yes — the command stream is generated and sent directly. That is independent of the database driver, which is only used to read your rows.