From: Andrew Lowe <agl@wht.com.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] SQL Server Advice for Small Business
Date: Thu, 01 Aug 2013 01:39:22 +0800 [thread overview]
Message-ID: <51F94BCA.1090500@wht.com.au> (raw)
In-Reply-To: <f582b4e1865ae1a78432d4e3ce490b1e.squirrel@www.antarean.org>
> On Mon, July 29, 2013 22:22, Randy Westlund wrote:
> Hey guys,
>
> I'm planning to set up an SQL server for my dad's small canvas awning
> business, and I've never done this before. Most of my sysadmin-type
> skills are self-taught. I could use some advice.
[snip]
Randy,
I've read your original post and subsequently the answers. One question
that nobody raised about your original post was why are you writing
something for your fathers company in the first place? Why aren't you
looking at ERP packages such as Compiere, Adempiere, Tryton, OpenERP etc
etc? In other words, why are you reinventing the wheel? With these
systems, you will get all of the data entry stuff already set up and you
can then do your data analysis stuff, although these systems also do
heaps of this stuff already. You don't mention what you do for a crust,
but if you do a good implementation of one at your Dad's place, you
could sell your services to other companies.
Someone mentioned PostGIS - forget it. You want to generate heat maps
based upon where business is going. This does not need a GIS. If you are
generating "real", accurate maps, then a GIS would be what you want, but
in this case, you just need a rough "mudmap" of the areas in question.
This would just show that City A is north west, ie the top left side of
the page, from you, which is in the centre, company B is east, the right
hand side of the page etc and based upon this, generate your heat map.
Scale, true orientation and position are not important. Even just grab a
Google Earth screen grab of your area and then write something what will
add heat, colours, to it in the appropriate places.
You mentioned a "small database". Don't underestimate how big things
can get quickly. If, at the moment when someone is spec'ing a job, and
they take photo's, but subsequently those photo's are hard to access,
they won't take the photo's in the first place. If you set up an easy to
access repository for the photo's, people will start taking more
photo's. If there are CAD drawings, what are they? 2D/3D,
AutoCAD/MicroStation or full on Solidworks solid models? These get big
very quickly. Scanned notes etc just add more and more. I have a feeling
that your small db could get big quickly. Just plan for that.
In closing, these are just my five cents worth, we no longer have two
cent pieces in Australia, regarding the software. I have no idea on the
hardware except as someone mentioned back up, back up and back up. Oh,
also, the more RAM the merrier.
Good luck,
Andrew
next prev parent reply other threads:[~2013-07-31 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 20:22 [gentoo-user] SQL Server Advice for Small Business Randy Westlund
2013-07-29 20:58 ` Mike Gilbert
2013-07-30 5:52 ` J. Roeleveld
2013-07-30 21:34 ` Randy Westlund
2013-07-31 6:00 ` J. Roeleveld
2013-07-31 8:48 ` Michael Hampicke
2013-07-31 17:39 ` Andrew Lowe [this message]
2013-07-30 10:31 ` microcai
2013-07-30 13:35 ` Mick
2013-07-30 17:50 ` Bruce Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F94BCA.1090500@wht.com.au \
--to=agl@wht.com.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox