I would like to know how people manage the databases. I have made about 5 different databases to cover thedifferent types of design that use different products. I keep them in the root database directory. Do other people do it this way? I can see that I might need to modify a database for a particular project, then put that database in that project directory. This is starting to get confusing, and when I need to add a new product, I need to add it to multiple databases. (Usually I use merge). I see where this can begin to be so complicated, I will need a spreadsheet to manage my databases.
Anybody do anything different?
Database Management
-
Mike Clough
- Posts: 2
- Joined: Sat May 23, 2009 12:11 pm
- Company: Engineering Support Intl
- City / Town: Naples
- Location: Naples Florida USA
- Contact:
-
Smccoon
- Posts: 5
- Joined: Tue Jun 09, 2009 7:04 am
- Company: Nelson Irrigation Corporation
- City / Town: Walla Walla, WA. USA
- Location: Walla Walla, WA. USA
Re: Database Management
Good Question Mike,
I like to keep the number of databases to a minimum, but seperate them by Ag and Turf.
Outside of a few materials, there is not that much crossover between these anyway.
The biggest thing to remember for me is to choose the Component Database I want to use out of "Settings - Irrigation Design Specific" before I add any hydraulic materials to the design.
So, while wanting to keep the number of databases to a minimum, the ability to have independent databases in IRRICAD is a great asset.
I like to keep the number of databases to a minimum, but seperate them by Ag and Turf.
Outside of a few materials, there is not that much crossover between these anyway.
The biggest thing to remember for me is to choose the Component Database I want to use out of "Settings - Irrigation Design Specific" before I add any hydraulic materials to the design.
So, while wanting to keep the number of databases to a minimum, the ability to have independent databases in IRRICAD is a great asset.