16 posts
  • Bought between 1 and 9 items
  • Has been a member for 2-3 years
boberic says

So i need to write a program for work. I’m wondering what the best back end storage solution would be. The program is a session tracker for a call center. Each user will have a username and password, but on top of that other data needs to be stored on a daily basis and in fairly large quantities. Number of sessions taken, revenue, time spent in each session, session type, etc. And then they have to be able to see the individual sessions so i need to store the information input from each session as well. I’m wondering would a SQL server suffice? or is there something else i can use. Maybe a saving each users input to an XML file? but that would make it hell for the back end maintenance. Any ideas?

1633 posts fueledweb.com
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • Author had a Free File of the Month
  • Bought between 10 and 49 items
  • Exclusive Author
  • Has been a member for 7-8 years
+1 more
RimmonTrieu says

A database server is your best bet, any XML persistance is inefficient for large user base and definitely non-scaleable.

SQL server is a common approach but NoSQL like MongoDB is pretty trendy right now with low learning curve and high performance.

You should consider using Flex with builtin support for REST web service, manually crafting Http Request is tedious and time consuming in AS3.

16 posts
  • Bought between 1 and 9 items
  • Has been a member for 2-3 years
boberic says

Ah i think I’ll run with a SQL database since I’m already familiar with its inner workings and know how to interface with AS3 -> PHP -> SQL. My only concern is that we have to save large amounts of text. When we submit our session reports they contain about 3 fields that can have over 255 characters. I’m talking close to 3-5k characters depending on the service. So i’m wondering if I’ll run into any issues storing that data.

1633 posts fueledweb.com
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • Author had a Free File of the Month
  • Bought between 10 and 49 items
  • Exclusive Author
  • Has been a member for 7-8 years
+1 more
RimmonTrieu says

Database record can handle huge amount of character which should not be your concern.

16 posts
  • Bought between 1 and 9 items
  • Has been a member for 2-3 years
boberic says

Cool. Was only asking, because I’ve never stored egregious amounts of data on a SQL server before. Most I’ve stored is a 16 character limited username/password a 225 char. limited email address and an address(the longest thing I’ve ever had to store). So I guess you could say it was more uncertainty than concern.

by
by
by
by
by
by