Update: install locally without MSSQL server

Hello Mark!

Firstly, I would like to thank you for your effort to share the awesome Celestial Altium library that you have compiled manually, I think the world would be a better place if more people possessed this kind of mindset.

The problem

I was somehow able to download the big Components.sql data file off of Github using

git clone --depth 1 https://github.com/issus/altium-library.git altium-library
cd altium-library

and spent the last evening trying to deploy the database on my local machine having no prior experience with MS SQL server. I was having trouble just plain executing the 200-odd MB query using sqlcmd, as it was giving off a substantial amount of errors related to non-existent databases and columns.

The solution

After some manual tinkering, I believe I've found the culprit: the sql project is missing some statements and columns that prevent the query from executing smoothly on a fresh machine. Here's a list of things I had to do manually to be able to import the database:

1. Install MS SQL Server (I used 2016) leaving the default Windows authentication enabled

2. Add the missing fields to the DB\altium_library\Tables\Components.sql definition file:

    [SensingRange]                    NVARCHAR(50) NULL, 
    [ActuatorLevel]                   NVARCHAR(50) NULL, 
    [PartStatus]                      NVARCHAR(50) NULL, 
    [HeightAboveBoard]                NVARCHAR(50) NULL, 
    [ElectricalLife]                  VARCHAR(50) NULL, 
    [Axis]                            VARCHAR(50) NULL,
   

3. Run PowerShell or CMD and navigate to the library definitions folder

   cd "DB\altium_library"
   

4. Run sqlcmd -S localhost for an SQL prompt and create an empty database

   CREATE DATABASE altium_library
   GO
   EXIT
   

5. Recreate the database structure by executing all query files in the folder (forfiles is available since Win7 at least)

   forfiles /s /m *.sql /c "cmd /c sqlcmd -S localhost -d altium_library -i @path"
   

6. Run the big import command

   cd ..
   sqlcmd -S localhost -d altium_library -i "Components.sql" -o "output.log"
   

7. Check for any errors in output.log. Normally, the file should just contain a bunch of repeating lines along the lines of (1 rows affected).

8. Open Celestial Library Database.DbLib and use the following Connection string:

   Provider=SQLNCLI11.1;Integrated Security=SSPI;Persist Security Info=False;User ID="";Initial Catalog=altium_library;Data Source=localhost;Initial File Name="";Server SPN=""
   

9. Test the connection and follow through with the rest of the installation instructons

Now normally I would have made this a pull request but I'm not quite sure if the steps I have provided are optimal. Besides, I'm not quite keen on Github's fork mechanics that demand users create useless clones of projects that they never intended to host on their page, and that whole process generates needless amounts of fuss. Now, back to the point - if you could add the steps needed for the local installation, I believe that can save some trouble for new people. The whole idea of local cloning will also help in the long run, if (when) you forget to update the Azure subscription, and generally is better for maintainability.

Using the opportunity, I would also like to ask you about the contribution model for the library. Are you planning to continue the development of this library, given how popular snapEDA is? If so, I couldn't find an easy way of adding the components to the library from the AD itself, maybe only using things like SVNDBLib, which again I'm not very familiar with. Am I missing something or the "community" update process (like adding new components) is indeed somewhat complicated? And another question: Would you be fine with someone distributing the library using Torrents? Not that I know anyone or am planning to do this, but I believe the deployment process could be done much quicker in this fashion. Please feel free to ignore these questions, though - I can fully understand how plowing through tons of messages on a public account can become a burden.

similar to issue 10

I have attempted to sign up, but cannot see the send button in the window (its below bottom of the window and does not allow for scrolling) i just hit tab 2 times and then enter, which takes me to the activation code window.

No activation email sent so I hit resend. An error has occurred shows, without any email sent.

I checked spam.

Also is there a lost username/password? I want to reuse the same email I have been using but forgot my password and get the following error:

I’m sending you a pull request for some changes to the Celestial database. Its really rough. Not actually meant for you to pull, but more just to get the conversation started, so you can see what I changed.

Actually I haven’t had time to play with Celestial until now. My ISP changed my IP address and I wasn’t able to access it. I found another way to grab the DB using skyvia.com.

For various reasons I wanted to get this DB running locally, using a MySQL backend rather than Azure. Well, it seems to be working, and it’s pretty fast. Way faster than my company database hosted on some beefy MSSQL server. (But this stuff is for hobby not work.)

So, when you have time, have a look at the diff:

• I pulled your Celestial DB and exported it as CSV.
• Python script to convert this CSV, and your views, to MySQL syntax and import to a local DB.
• New DbLib file to use it.

As a side note, I noticed a gzipped version of the full DB is only 1.6MB. Might actually be feasible to check that in, I don’t know.

A few questions for you:

• I understand why the main Component.sql file was converted to git-lfs. But why were the Views/*.sql also converted? These are small files.
• I am unable to clone the repo when I have git lfs tracking the .sql files. It fails to download them, (presumably due to quota), and then the rest of the clone fails. Had to turn off lfs tracking to get it to succeed. So bottom line, I can’t see your latest Views/*.sql files.
• So I branched off of your July 2016 commit that still had the Views in sql in the repo. I don’t imagine they have changed much (if it all) since then.

Hi!!

I'm trying to install de database following the steps of "http://altiumlibrary.com/GetStarted/ConfigureAltium", but Altium gives me the next error:

I installed the Access engine from microsoft web, but i can't get a sucessfull connection.

Any idea to fix it??

Thanks!!

Not sure if this is an issue for this repo or for the windows app repo, but after the UDL file is written, Altium can't connect to anything using it. And since I'm on 64-bit Win7 I can't even open the UDL to see what's in there. The tricks for opening a 32-bit UDL on a 64-bit system don't seem to work either.

Can't I get the host/port and give my auth credentials manually and skip the UDL? For the time being I just downloaded the MDB and am using local database access, but that's suboptimal for what looks to be a promising replacement/augmentation of Altium's vault.

Hi,

After i installed the Celestial Library my Altium became extremely slow in some operations. Like, change a component footprint, update the PCB from the schematic.

After a lot of research i figure it out why.

When certain operations are performed, the library itself open a connection to the database and execute several query's (more the 10k).

The problem is that from my location the latency to the DB server (db.altiumlibrary.com) is huge (200 ms).

For me this could be solved, by making the database locally or with a closer mirror to my location. But i could not find the DB data in github, not connect to the database server to dump the tables.

Anyone else with the same problem?

Can someone provide me a database backup? So I can use a local server to confirm if this fix the issue or not.

Thanks

Some days when using the library Altium will become unusable. If I even try to move a component in the schematic Altium will lock up for about a minute. Even after restarting my pc the issue is intermittent. Sometimes it immediately returns after a fresh restart. When I close the library the issue disappears. Don't know what else too add that could help.

I have a 4790k, 32gb ram, gtx 980 ti and everything is on an ssd.

Hi! I've done all the setup through desktop tool as described here, cloned the repo, but Altium still wouldn't connect to the database (see screenshot attached). Can this be a server-side problem?

Hi, I couldn't find the supplier information except for digikey. Is there any help you guys can provide so I can add mouser entries in the database for the components I'm using?

There is no reference designator text on the assembly layer for these library parts.

I know this text isn't necessary if Draftsman is used to make the assembly drawing, but I can't get Draftsman to create an assembly drawing in the project that is using this library. Similarly, I have issues with using the project releaser with this library.

I am using altium 17 and was able to add the library successfully and no problem so far. However my disk is getting full and wanted to change the library folder so I removed the dblib file in the "Available Libraries" menu as below And then copy everything in the altium-library folder into different location and install the dblib file again. But after that, I am only getting these message saying "EOleException error executing: Select * From [Whatever parts] Cannot find supplier. May not installed properly" as below

It seems like Altium is still trying to find the old DB instead of new one. How can I solve this issue? Thanks,

I'm attempting to set a server login up so I can create a local copy of the database bet when I go to set the server login password it returns an error.

Error. An error occurred while processing your request.

Anyone else having this issue

Hi there, flash memory W25Q40CLSNIG has assigned a wrong variant of 8-Pin SOIC, which is 208-mil instead of 150-mil. W25Q40CLSNIG is 8-Pin SOIC8 150-mil W25Q40CLSSIG is 8-Pin SOIC8 208-mil Datasheet

Solder mask swell set to zero, because pin clearance == 0.2mm. No way to have mask bridges with class 3 PCBs (guided by JLCPCB specs for green mask only)