DBLIB or SVNDBLIB ?

In a DBLIB Library you can have multiple footprints stored in the file or a single footprint. The model name in the file can be anything as long as it is a unique name within the library file.

Filename = SOP50P490X110-10NC.PcbLib
Footprint Ref = any unique name.

DBLIB:

Pros:

• Simpler to implement and use than SVNDBLIB.
• Supports multiple and single part Library files.
• Good Choice for Single and Multiple Users

Cons:

• NO Version Control for Symbols and Footprints
• NO Right Click and Edit Symbols and Footprints from Library Panel.

Note: DBlib libraries support single or multiple part files, however, it is recommended that you create library files with one symbol or footprint per file. This will reduce locked file conflicts in multiple user environments.

SVNDBLIB:

In a SVNDBLIB you can have only one footprint per *.PCBLIB file. And the model name in the file must be exactly the same as the file name.

Filename = SOP50P490X110-10NC.PcbLib
Footprint Ref = SOP50P490X110-10NC

Note that the Footprint Ref (model name) matches the Filename for SVNDBLIB.

This also applies to symbols *.SchLib files.

Pros:

• Version Control for Symbols and Footprints
• Right Click and Edit Symbols and Footprints from Library Panel
• Good Choice for Single and Multiple Users

Cons:

• Occasional Corrupted SVNCaches.
• Performance, slower than DBLIB.
• Setup is more complicated than DBLib, may require technical support.

SVNDBLIB's slower performance is due to the SVNCaches which include a working folder and a system cache of footprints and symbols that are checked out from the SVN repository.

Choices:

Both DBLib and the SVNDBLIB are the good choices for library maintenance. 

When deciding which choice is best for your situation, you need to consider number of users and librarians that will be using the database.  

You should consider you team's experience with SVN when choosing SVNDBLIB.

Suggestion:

Start out with a DBLib, then convert to a SVNDBLIB if you need better version control (accountability for changes). 

Transitioning from DBlib to SVNDBlib will be easy if you have one model per file which is required for SVNDBlib.  

The sample symbols and footprints included in the 'Parts' download are one model per file.

Using a well designed Parts Frontend application can greatly simplify Altium CAD library maintenance.

That's It !