Showing posts with label Database Libraries. Show all posts
Showing posts with label Database Libraries. Show all posts

Friday, October 27, 2017

GitHub - issus/altium-library: Open source Altium Database Library with tens of thousands of high quality parts and 3d models.

GitHub - issus/altium-library: Open source Altium Database Library with tens of thousands of high quality parts and 3d models.

"Celestial Altium Library An exceptional, open source database library for Altium, currently supporting MSSQL and SQL Azure as the backend for easy use within teams, and no data corruption unlike MS Access. Current part count in live database: 28,635 in almost 600 packages. This library has been built for high quality data, with high quality footprints and high quality 3D models."

'via Blog this'

Wednesday, January 11, 2017

Parts DBLib Library - FREE

The FREE Parts DBLib contains everything you need to get an Altium DBLib library up and running in less than 5 minutes.

Did you know ?


You do NOT need to have Access installed to use a DBLIB library in Altium.


Using Altium's DBLib interface you can edit and add parts to an Access database.


Take the challenge and see for yourself that you really can have your own fully functional DBLib library in 5 minutes or less.


Here are the steps to quickly setup and use the Parts DBLib library:


Download Parts DBLib.


Install the Parts DBLib Library in Altium. See Getting Started.


Use Altium's DBlib to edit or add parts to the database.

You are done, you should have a fully functional Altium DBLib library.

If you are looking for a more efficient way to edit and add parts to the database give the Parts Frontend a test drive. 

The Parts DBlib download includes a demo version of the Parts Frontend.  A Frontend application is not required to use an Altium DBLib or SVNDBLIB library.

When using a well designed database Frontend you will spend significantly less time designing library parts, leaving you with more time to design boards.


What Makes Parts Different ?


That's It !

Thursday, November 10, 2016

Database Libraries for DBLib and SVNDBLib

Here are some good tips for anyone planning to create a database for Altium DBLib or SVNDBLib libraries. Speed Up Your Access Database - PerformanceTips - Microsoft

Parts is a free turn key working Access database for DBLib and SVNDBLib libraries.

The Parts download includes an optional (not required) Frontend application that greatly simplifies creating parts and library maintenance.  Parts can support 20 to 50 users.

You can purchase keys for the Parts Frontend or create your own Frontend for the database. 

Get on the fast track with Parts.

If you are looking for a database with a web browser interface, take a look at ADLib.

ADLib - Libraries Built to Last - Nine Dots Connect

That's It !

Sunday, April 7, 2013

Database Libraries

One of Altium's best features is it's scalable Database Library (DBLiB).

A well designed database library application  can support multiple users and simplify library maintenance.

Database libraries can be created to support remote and on premise design teams.

















Parts Presentation on You Tube 

The Parts database library can support multiple concurrent users.  

Parts can be used to clean up existing libraries before migrating to Altium 365 managed components.

The Parts DBLib download contains everything you need to get an Altium DBLib library up and running in less than 5 minutes.


For creating and maintaining database libraries Altium has several options to chose from, which can be as simple as an Access database or an ODBC compliant data source, i.e. MySQL Server.

Parts can be used with a cloud hosted MySQL database for remote collaboration. 

A very popular solution is the DBLib Library solution implemented using Microsoft Access.


Microsoft Access is an excellent choice for creating a shared database library

Inexperienced database designers often overlook the importance of splitting the database. In a split database there is a back-end (data tables) and a front-end (user interface).

Access newbies will often design a peer to peer network. They start out by designing an Access database on their computer, then share the database using a shared folder.


On a peer to peer network the database is hosted in a shared file folder on a PC within a work-group.  A peer to peer network will work for 4 or 5 users, provided the hosting computer is always online.


In a Windows peer-to-peer network NO more than 4 or 5 users will be able to connect Altium to an Access database.


For anything more than 4 or 5 users, the best solution is to use a client/server network with a dedicated server.  Clients are the front-end applications, for example one session of Altium connected through a DBLib to the database would be one client.


The physical maximum number of concurrent connections for Microsoft Access is 255 for databases that are installed on a network drive.


If a multi-user database is designed properly with a split front-end and back-end, all users have "Full control" security permissions on the network shared directory, and all users are only reading the records, then the physical limit of 255 concurrent connections could be reached. That's about 60 users because each user will consume 3 or 4 connections.


In a practical network there will be designers and engineers who for the most part will be reading records from the database library as they place parts into their designs. And there will be some librarian activity, like creating new parts and updating existing parts.


Therefore the practical number of concurrent users will be limited to the amount of network traffic and the amount of record lock contention. Record lock contention can be minimized in a well designed database.


An experienced Access database designer can create a robust multi-user database solution using Access.


Summary:

The Parts Access database solution will support ~60 users on a company LAN.