Skippr Docs

Appearance

How MSSQL Defines the Raw Data Contract ​

July 2026

For MSSQL, raw data means the rows exposed by the SQL Server database objects the login can read, not a generic promise about every system behind the server.

Short Answer ​

The raw data contract for MSSQL is the row shape exposed by the SQL Server tables or views the configured login can read. Skippr connects with one ADO.NET connection string, so the raw layer comes directly from that database surface and keeps database, schema, and table names visible through the mssql.{database}.{schema}.{table} namespace.

That makes the contract easy to state in concrete terms. If the login reads sales.Orders and sales.Customers, raw data is those rowsets with their SQL Server column names and types. If the team chooses a reporting view instead of a base table, the view output is the contract, because that is the actual row shape the connector is extracting.

Why Teams Struggle with This ​

MSSQL becomes confusing when teams treat one connection string as permission to ingest everything behind it. The useful raw contract is always narrower than that: a specific database, a specific schema surface, and a specific set of rows the downstream team can name.

  • The database embedded in the connection string decides which SQL Server surface Skippr is actually reading.
  • A readable view can be a better raw contract than a volatile base table, but only if the team means to publish that view output.
  • TLS settings and certificate choices affect connectivity, not the data shape that the raw layer promises.
  • If the login can only reach a test database, the raw contract is wrong before any data lands downstream.

How Skippr Handles It ​

Skippr keeps SQL Server practical by not hiding the transport details that matter. The connection string defines the server, database, login, and encryption posture, while the namespace keeps the resulting table lineage obvious to downstream engineers.

That makes MSSQL a good raw source when the relational tables are already the contract. You can preserve the existing row model without inventing a separate export file format or event feed just to move the data.

  • Connects through a standard ADO.NET connection string.
  • Works with SQL Server and Azure SQL endpoints using the same connector surface.
  • Preserves raw lineage with the namespace mssql.{database}.{schema}.{table}.
  • Fits table or view extraction when the SQL Server row model is already the source contract.

What the First Useful Version Looks Like ​

The first useful version is one connection string, one database, and one or two tables or views that the business already trusts. That proves the SQL Server surface is a real raw contract rather than just a convenient place to start.

If the team uses Azure SQL, keep the fully qualified server name and the chosen database explicit in the rollout notes. In SQL Server work, pointing at the right database is often the difference between a durable contract and a misleading one.