gomer - 4:31 am on Sep 19, 2005 (gmt 0)

Webwork, I feel for you. The task at hand is large but I think you have the right approach, stay with it. Don't let a lot of unnecessary lingo make things more complex for you than they need to be.

In my opinion, you should not be discussing fail over, SAN or load balancing. If you are discussing those things, you have probably picked the wrong person to assist you. Yes, something like an interface where you can enter data and administer processes is good.

Sometimes people make things more complex than they need to be. Choosing such help is the worst decision you can make.

You have received some very good advice here on these first two pages of this thread. At this stage, knowing who to listen to is difficult but that is the most important decision you are going to make.

Here are some quotes from this thread of advice that I think are bang on in terms of what you need. It is worth repeating.

volatilegx:

* List of the data I wish to retrieve/store (name: first, last, middle initial; street address, etc.) * List of "types of searches" I wish to enable (search by price, State, etc.) * Security processes (password protection) * Data expiration and storage upon expiration (archive?) requirements * Payment processing info (if paid listings) The above is a good starting point to work with a programmer. Adding to that would be to mention a budget you would like to stay within and a time frame for completion. Above all, be prepared to be available to answer questions asked by them. Some of the things I would demand of a database programmer: * a useable interface for you to be able to enter new data, edit existing data, etc., which would also have * a reporting feature which would allow you to export data * an importing feature that would allow you to easily import large amounts of data * an automatic method of database backup, preferably by cron job. You would probably be responsible for downloading/archiving the backups, though. * a maintenance plan, so the programmer could go back in the future to correct any errors, etc.

aspdaddy:

One way I have worked in the past. The client gives me all the html pages of the site including what a search results page looks like, a single record page, before and after Paypal or WorldPay pages, and the step by step pages to create an account or make a listing. Everything ready for database integration. Usually I will tell them theres stuff missing like bad credit card page and error pages. They also let me know where the site will be hosted and I call the host if I dont know them already to check what db they support - Access, MySql or MS SQL. The only questions I need to ask is about requirements for security, volume of data, backup, response times and administrative functions and of course budget and timescales. All the normalisationa and designs I will decide based on the above. What are various data mining requirements? I would not ask stff like this at this point, client are usually focussing on getting a prototype working site to show sponsors etc. Questions like this increase the initial cost and are better handled with subsequent work, IMO.

surfin2u:

Find someone, who you can trust, and work with over the long term. I'm talking about a technical person, who will have a interest in the long-term success of your business. Develop a relationship with that person that probably involves part ownership or profit sharing, after you decide that you've found the right person.

Choose the right people and they will take care of most of your headaches. Keep things simple.