A Content Center library is contained within the Microsoft SQL Server (MSDE) database and is stored using a pair of files with the extensions MDF and LDF. These files together comprise one library and need to be maintained together.
Go to the installation path of the Microsoft SQL Server, by default, C:\Program Files [(x86)]\Microsoft SQL Server\MSSQL$AUTODESKVAULT\Data, and verify the pair of files for each library database. By default, Content Center provides varied standard libraries such as Inventor ANSI, Inventor DIN, Inventor ISO, Inventor JIS & GB, Inventor Parker, and Inventor Other. These libraries contain conduit parts and fittings used to define tube and pipe styles, populate routes and runs. These conduit parts and fittings can also be placed into tube and pipe assemblies using AutoDrop.
In addition to standard parts, you can also author and publish custom tube and pipe iParts or normal parts to the appropriate category and family in the Content Center. Normal parts, however, can only be authored and published as fittings. You cannot author or publish them as conduits such as tube, pipe, or hose.
How does file naming schema of tube and pipe library part families work?
Conduit parts hold a custom length so each conduit part corresponds to one file in your workspace, for instance, each pipe segment relates to a file even if pipe segments have the same length and other manufacturing information. Fittings are standard library parts in the Content Center so all occurrences in the same library standard refer to a single local file.
When conduit parts are placed into a tube and pipe assembly from the Content Center using AutoDrop, they are stored in the corresponding pipe run folder and the Content Center file name schema will be used. When conduit parts are used to populate routes, the Tube & Pipe specific naming convention of .<13-digit number> (where <13-digit number> is automatically assigned based on the current time of your computer) is used. The naming also indicates pipe, tube sweeping, or hose.
When fittings are placed from the Content Center using AutoDrop or used to populate routes with tube and pipe styles, they are always stored in the Content Center Files location in your work space and the Content Center file name schema is respected. By default, Content Center naming is <nominal_size>.ipt. Use the File 
Open dialog box to verify the fitting file location:
- In the Open dialog box, click Projects. On the Project pane, expand Folder Options and verify the Content Center Files location. To see the default location, pause the cursor over the item.
- In the Open dialog box, click Open. On the Locations pane, expand Content Center Files and double-click Content Center Files to navigate through the part family folders.
How are library fittings and conduit parts used in tube and pipe design?
Tube and pipe styles define the type of conduit part, coupling, and elbows used to populate routes and runs. They are automatically generated from the Content Center. Other fitting types can be manually placed into the tube and pipe assembly using AutoDrop. Tube and pipe library parts may respect the Content Center file naming schema or use Tube & Pipe specific file naming convention, depending on how they are introduced into an assembly.
What can I do with tube and pipe library parts using the Content Center?
To modify library parts, ensure you have edit and publish permission to the Content Center. Using the Content Center, you can:
- Use library parts to define tube and pipe styles and populate routes and runs.
- Place library parts into a tube and pipe runs assembly using AutoDrop.
- Replace one or all occurrences of a fitting in the active pipe run with a standard or published fitting.
- Customize the file naming schema of conduit parts and fittings.
- Edit and republish custom library parts from within the Content Center.
How can I locate branch fittings?
By default, standard branch fittings are stored in the Inventor Other library. To place them using AutoDrop, ensure that the library is attached to the Content Center. As with normal tube and pipe fittings, you can also author and publish custom branch fittings into a read/write library.