Import pipe inventory into SQL server
This article
is for IT professionals familiar with Microsoft SQL Server and related
technologies
The user assumes all responsibilities for
any data integrity issues or corruption that may occur when updating a database using anything other than a PypeServer product. It is recommended that
a backup of the PypeServerDB database be done before any bulk import.
Pipe table schema
The SQL database PypeServer has several related tables with foreign key constraints for relational data integrity. Pipe data is stored in the Pipes table located in the SQL database PypeServerDB. Most of the columns in this table are for internal use only and should not be set during import. Product updates may add, rename, or remove any of these columns.
Columns
These columns may be set when inserting new pipe inventory.
| Column and Data Type | Description |
| [BarCode] [nvarchar](max) NULL | Stock barcode |
| [Cost] [money] NULL | Stock cost |
| [Customer] [nvarchar](max) NULL | Intended customer |
| {DateCreated] [date] NULL, | Stock received date |
| [Job] [nvarchar](max) NULL | Intended job |
| [IsMetric] [bit] NOT NULL | Default is false. Set to true/1 when pipe is metric. |
| [MaterialData] [nvarchar](max) NULL | Material heat number |
| [MaterialType] [nvarchar](max) NULL | Material name |
| [NominalSize] [nvarchar](max) NULL | Stock nominal diameter, i.e 6" |
| [OuterDiameter] [decimal](18, 3) NOT NULL | Stock diameter, i.e. 6.625 |
| [PipeLength] [decimal](18, 3) NULL | Stock length |
| [PipeNotes] [nvarchar](max) NULL | Stock notes or additional pipe data |
| [TrueOuterDiameter] [decimal](18, 3) NULL | Measured stock diameter, may be different than OuterDiameter |
| [TrueWallThickness] [decimal](18, 3) NULL | Measured stock wall thickness, which may be different than WallThickness |
| [WallThickness] [decimal](18, 3) NOT NULL | Stock wall thickness, i.e. 0.28 |
Table updates
When updating the Pipes table it is recommended that SQL transactions are used when updating the the Pipes table. This can be done by adding BEGIN TRANSACTION and COMMIT statements to the update process so inventory is either committed or rolled back as one unit of work.
Inserting a new row will automatically set the primary key column PipeID [bigint] to a database unique value.
Related Articles
About SQL Server
About SQL Server Microsoft SQL Server is a relational database management system (RDBMS). PypeServer Enterprise and tools connect to a SQL Server instance or database, where all part, pipe, and other shared data is stored. The PypeServer Kiosk ...Troubleshoot MSuite parts with missing hole or saddle cuts
Issue Parts imported from an MSuite package are missing hole and saddle cuts. Background MSuite has some model and workflow requirements that must be fulfilled before all the data required to identify and create saddle and hole cuts becomes available ...About License Server
About CodeMeter The licensing system is the CodeMeter security system offered by WIBU (www.wibu.com). It consists of a set of licensees stored in a USB dongle or encrypted file at the PypeServer Kiosk. A WIBU CodeMeter License Service runs on the ...Enterprise Training - Importing
Introduction to Importing Importing files into PypeServer Using the importing system to import part designs into PypeServer v3.03 Importing Into PypeServer Document on the importing data into PypeServer Describes the activities and rules in importing ...Make a single cut on the pipe
Make a single cut on the pipe Trim the end of a pipe/Cut a pipe in half This function allows you to easily send a single straight or miter cut to the machine to make one cut (not cutting a two ended part). This functionality only appears when you are ...