Is my db too big for my server? Should I go nosql or stick with relational db management? I have a mysql database that is about 22GB in size and has multiple tables with hundreds of thousands of records, my biggest table has 1.8 million records. The Database was not professionally designed by a DB admin, it was designed by a php developer with not a lot of experience in dealing with that much data. I know its not the largest amount of data but it is giving is very slow performance, some of it is the code written.

My question is, does my system currently support the DB of that size? I have a dedicated managed server from go-daddy, 32GB of RAM, quad core processor, 1TB of storage. We have about 100 users actively using our application looking for a single record within a specific table.

I am thinking about restructuring the DB and also going into cloud instead of dedicated server and going with nosql db management rather than our current relational.

However I am not a DB admin, I am a developer. I would love to hear your thoughts.
I would like to echo @Thronk 's remarks about not having enough information to fully answer your question.

However, take a look at this article by a guy who sold his business to eBay and is still senior there.

This suggests to me that you would be far better off redesigning/refactoring your database according to proper relational principals rather than jumping on the NoSQL bandwagon which will involve more work and greater risk. As @Thronk points out, 22GB is not a large system. 

If you're using 5.6, try using the performance_schema (p_s) to pick the low-hanging fruit first, which may give you the breathing space you need to properly redesign. 

Don't be afraid to come back here with design questions and problem SQL - don't forget that the more detail you put into your question, the better your answers will be. It may be that some reindexing may help - again, don't hesitate to ask here. p.s. welcome to the forum!