title: Switching from SQL to Redis as standalone
body: <p><strong>Background info before question</strong></p>
  
  <p>I use state session a lot to store my complex objects, I am also using at max like 8 tables. On those 8 tables I am using like about 25 SP to join users based on user id and some key values that the user selects. All this is done on SQL Server database.</p>
  
  <ol>
  <li>zip codes spatial values</li>
  <li>male or female</li>
  <li>has pictures</li>
  <li>approved profile</li>
  <li>registered account(paying for services)</li>
  </ol>
  
  <p>I store Images in a file system on my application server. I store the path on my db table. </p>
  
  <p><strong>Use Case</strong></p>
  
  <p>Dating website, unique payloads most of the time such as searching based on a certain criteria, updating and fetching personal profile with photos. I am using asp.net MVC, and this is a website only. (separate web pages for responsive designs for other devices)</p>
  
  <p><strong>Question</strong></p>
  
  <p>Can I just use Redis as my primary data store, instead of using SQL server Database based on my use case?</p>
  
  <p><strong>Key Points</strong></p>
  
  <p>I don't on plan on having more than like 10-12 total tables in the future. The data input are mostly strings. When I want to persist a complex object like profile information and image paths I use a Session State. I love what I read about the speed of Redis, and I see it being counter productive to duplicating updates to both Redis and a DB if I stack them.  </p>