I am trying to use SQl to simply the data I get from AutoCAD. I was wondering i was wondering whether there was a way to create one single folder for all the data from AutoCAD, including multiple projects, into just one database (or 4) instead of creating a new database for every project. I really do not want to have 4 new databases for every new project I create.
Is there an AutoCAD solution to this problem, or is it just something I will have to fix on the SQL side of things.
It depends on who the projects are for, and how you want to set them up. If they are for one client, and you know its going to be ongoing work, then maybe do one project for that client/site and just keep using that one until the work stops.
If they are separate clients/projects, then it would be easier to keep them as separate projects. Line Numbers, Valve Tags etc could get messy if you keep all your projects/clients/sites under the one database.
I agree with that concept.
But could there not be extra columns for project name, dwg, file, which could differentiate them in SQL while keeping them in one database.
I have also notice that some of my databases have different tables then other projects. It is kinda weird. It also makes life difficult when you are trying to make a system consistent with in one self.
The whole reason why I want to use just want Database is because I want things as simple and consistent as possible. The reason why I need them consistent and simple is that I use AutoCAD to do bids. I might bid on 5 projects in a month of varying sizes. I do want to vreate 20 new databases every month. The advantae of using AutoCAD to do bids is that it creates a standard methodology which can be repeated again and again. There is also so much data that can be glean from a 3D model that can get overlooked when looking at GAs. It also allows me to get a jumpstart on doing the cut sheets so our welders can weld the pipes sooner.
Im not sure why your saying you would need to create 20 databases per month. If your only bidding on 5 projects, then you would only be creating 5 dbase instances.
I would still tend to lean towards one P3D project per client, or per Project/Site.
If you have it all in one, and things like the database fields (to populate the text fields on borders/isos) would just get too out of hand. Unless you are the only person managing it, how do you plan to set it up so you know which database field is for which border, and which field it should be? And then for Ortho's, do you plan on having different borders for each? Iso styles isn't too much of an issue, they have different .dwt files for each.
Then things like valve tags, are you 100% sure they are all going to be the same for all the projects, line numbering tags, Joint Connection rules, P&ID settings etc.
How would you also manage the files within the project manager? When running Iso's, would line numbers clash between projects?
With these little projects, are they small brownfields kind of work? Eg, spool replacement, or equipment removal and replacement? If its on the one site, then thats easy. If they aren't, then TBH, its probably easier just to make another project for it.
I like to keep ISO settings the same, as well as connections setting (all the projects I do are similar). Valves tags are unimportant since I am not the designer of the plant. I also do not bother with orthos, since they are usually provided by the engineering firm. Currently I am the only one managing the AutoCAD files and the SQL files, ut I am hoping to expand it across my company as I work the issues out of the system.
I usually use the similar line numbers 001-01,001-02.... so those might clash unless there was an extra column in the database for dwg.
I added an attachment with some of the features I would like in one table (I had to use the join function to create it).
Any way I can deal with just lots of different databases.
Every project that gets created with SQL Express creates 4 databases ( ISO, Ortho, Piping and PnID). So 5 projects times 4 seperate databases per project creates 20 new databases in a month. Which over time might to cause a headache.
Not really, the 4 databases stay with each project. That would be better management than trying to do one massive project for each little sub-project you want in your all-in-one database.
Even with SQL Server, the databases are prefixed with your project name (or whatever you want).