Gentoo Archives: gentoo-user

From: Andrew Lowe <agl@×××××××.au>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] SQL Server Advice for Small Business
Date: Wed, 31 Jul 2013 17:39:39
Message-Id: 51F94BCA.1090500@wht.com.au
In Reply to: Re: [gentoo-user] SQL Server Advice for Small Business by "J. Roeleveld"
1 > On Mon, July 29, 2013 22:22, Randy Westlund wrote:
2 > Hey guys,
3 >
4 > I'm planning to set up an SQL server for my dad's small canvas awning
5 > business, and I've never done this before. Most of my sysadmin-type
6 > skills are self-taught. I could use some advice.
7 [snip]
8
9 Randy,
10 I've read your original post and subsequently the answers. One question
11 that nobody raised about your original post was why are you writing
12 something for your fathers company in the first place? Why aren't you
13 looking at ERP packages such as Compiere, Adempiere, Tryton, OpenERP etc
14 etc? In other words, why are you reinventing the wheel? With these
15 systems, you will get all of the data entry stuff already set up and you
16 can then do your data analysis stuff, although these systems also do
17 heaps of this stuff already. You don't mention what you do for a crust,
18 but if you do a good implementation of one at your Dad's place, you
19 could sell your services to other companies.
20
21 Someone mentioned PostGIS - forget it. You want to generate heat maps
22 based upon where business is going. This does not need a GIS. If you are
23 generating "real", accurate maps, then a GIS would be what you want, but
24 in this case, you just need a rough "mudmap" of the areas in question.
25 This would just show that City A is north west, ie the top left side of
26 the page, from you, which is in the centre, company B is east, the right
27 hand side of the page etc and based upon this, generate your heat map.
28 Scale, true orientation and position are not important. Even just grab a
29 Google Earth screen grab of your area and then write something what will
30 add heat, colours, to it in the appropriate places.
31
32 You mentioned a "small database". Don't underestimate how big things
33 can get quickly. If, at the moment when someone is spec'ing a job, and
34 they take photo's, but subsequently those photo's are hard to access,
35 they won't take the photo's in the first place. If you set up an easy to
36 access repository for the photo's, people will start taking more
37 photo's. If there are CAD drawings, what are they? 2D/3D,
38 AutoCAD/MicroStation or full on Solidworks solid models? These get big
39 very quickly. Scanned notes etc just add more and more. I have a feeling
40 that your small db could get big quickly. Just plan for that.
41
42 In closing, these are just my five cents worth, we no longer have two
43 cent pieces in Australia, regarding the software. I have no idea on the
44 hardware except as someone mentioned back up, back up and back up. Oh,
45 also, the more RAM the merrier.
46
47 Good luck,
48 Andrew