I'm running SQL Server 2014 on my laptop along with a ton of other installed applications, from Visual Studio to video games.
This is obviously not a production server, but for development and debugging only.
I've scripted out a fairly small and simple database, with a few dozen tables and views - and I've inserted less than 100 rows of dummy data for testing.
At one point I accidentally created a 100GB+ index, using some badly formed cross joins - the query creating this index was consuming 100% of the RAM in my laptop (16GB), which slowed everything to a crawl, so I aborted the query rather than waiting for it to finish, then promptly dropped and re-created the entire database with this index removed from the creation scripts.
However, SQL Server 2014 kept consuming all 16GB of my RAM from that point forward, even with the query aborted and the database dropped.
So I rebooted my laptop next, and the RAM usage for SQL Server dropped down to 7GB - where it has remained ever since, regardless whether or not I drop all of the 5MB of existing databases etc.
I'd like to get SQL Server back to a reasonable memory consumption level, but I don't know where to begin looking for possible causes.
I know this is a pretty open-ended question, but I'm willing to do the legwork with a little guidance.
I just don't know where to begin troubleshooting, since I'm not a DBA myself - and apparently Google doesn't know either. :)